-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
okta_resource_set
always detects a change in resources with an ORN path
#1991
Comments
Hi @joshuacollins-deloitte, how is this issue blocking your flow? We are currently limiting investment in Classic Engine. Are you exploring an update to Identity Engine? This information will help us determine and prioritize the fix as necessary |
Hi @duytiennguyen-okta, I included the comment about classic engine for context, but after testing today, I can also reproduce the issue in Identity Engine. |
We are using Identity Engine and also experiencing this problem. We're using the ORN because some resources such as Workflows don't have a REST API. I guess for now we will just have to ignore changes but it would be great to have a fix here. |
We are also using OIE and experiencing this issue. We manage all Resource Sets in Terraform so having a fix here would make not look like we have drift everytime a plan/apply is run. |
OKTA internal reference https://oktainc.atlassian.net/browse/OKTA-735700 |
@duytiennguyen-okta |
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
I've redacted the organisation ID below, but it's reproduceable in every environment I've tried so far. All 3 are classic engine environments.
Expected Behavior
The resource set should be created once and then not appear in the terraform plan until the configuration changes (or drifts on the tenant)
Actual Behavior
Terraform persistently detects that a change is required and attempts to add the resource again on every plan and apply. Subsequent applies still succeed.
Steps to Reproduce
terraform plan
andterraform apply
to create the resource setterraform plan
again and see that the resource_set will be updated in the planImportant Factoids
References
The text was updated successfully, but these errors were encountered: