This pre-deploy error appears when attempting to deploy an Okta element which contains a user email or user id, which doesn't exist in the target application connection.
What triggers this error?
When deploying to Okta, you may get the "Element references users which don’t exist in target environment" error, and an element won't be deployed because of this error.
This message shows up when Tulip is trying to deploy Okta elements which contain a reference to one or more users, but some of these users do not exist in the target application connection. This means that Tulip can't automatically deploy the element as-is, and you'll have to solve the problem in order to deploy it.
How can I solve this?
To solve this issue, you have 3 options:
Manually add this user to your target Okta application connection. After doing that, try deploying again for Tulip to identify the newly added user.
Manually edit the element's NACL file, and change the missing user to one which exists in the target application connection. You can edit the NACL during a deployment, in the pre-deployment overview stage.
To edit a NACL during a deployment, open the element and then click the "edit" option shown on the right side of the element header
Add the omitMissingUsers option to your target Tulip application connection's configuration file. When this option is on, Tulip will omit the missing user from the element in types that allow it. When using deployments, your application connection configuration can be accessed from the application connection settings page:
Here's a sample configuration file which includes this option:okta {
fetch = {
include = [
{
type = ".*"
},
]
}
deploy = {
omitMissingUsers = true
}
}