Open pro4tlzz opened 1 year ago
Thanks @pro4tlzz . It seems like the when the user is created the resource is not then setting the custom attributes to ignore. This is a bug, we'll look into it. Okta internal reference: https://oktainc.atlassian.net/browse/OKTA-611104
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 5 days
Not stale
Not stale and still an open issue. I would assume that the property is setup on first apply (not subsequent) and any changes would be ignored
Community Note
Terraform Version
1.2.2
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
The okta_user.user resource is created and the
custom_attribute_to_set
has the correct value set when the resource is created.Can this be done in the Admin UI?
Yes
Can this be done in the actual API call?
Yes
Actual Behavior
The okta_user.user resource is created but the
custom_attribute_to_set
is not set. If a Terraform plan is run afterwards then an update to the okta_user.user resource for thecustom_attribute_to_set
property is described in the plan.Steps to Reproduce
terraform apply
terraform plan
terraform apply