-
Notifications
You must be signed in to change notification settings - Fork 2
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
Attachment RG scope causes terraform error #186
Comments
A variation of this problem also happens in the following scenario:
I get an error indicating that there is an issue in the provider itself when it tries to read/map the scope parameters and gets the new values from the RG exclusion entries:
|
It looks like any change to the attachment in SCC after deployment will cause the scope to get updated with Then the SCC DA cannot be undeployed or its inputs updated, the only way out is to clean up schematics workspace and delete the DA. |
@jor2 - the case that you submitted above is a different issue. The error you show in the output indicates that you did not supply a parameter that is required, but no default value is in the profile. This is not the same as the scope read error above. |
@in-1911 are you still able to reproduce this error? I wasn't able to. |
Tried to use an RG scope for an attachment.
I set the
resource_groups_scope
with one resource group name in the array. This was done after the SCC instance with a profile attachment for "AI Security Guardrails 2.0" has been deployed (originally using [] for the RG scope). When trying to update the deployment with the new RG scope, I got an error on apply (plan was successful):So I tried to change the RG scope back to
[]
but then somehow the schematics state got themodule.create_profile_attachment["AI Security Guardrails 2.0"].ibm_scc_profile_attachment.scc_profile_attachment
resource stuck with a non-empty value that it cannot refresh and I cannot even undeploy the config:Affected modules
Terraform CLI and Terraform provider versions
Terraform output
Debug output
Expected behavior
Actual behavior
Steps to reproduce (including links and screen captures)
terraform apply
Anything else
By submitting this issue, you agree to follow our Code of Conduct
The text was updated successfully, but these errors were encountered: