ibm_scc_instance_settings incorrect plan to change

[kierramarie]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform IBM Provider Version

Affected Resource(s)

• ibm_scc_instance_settings

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

https://github.com/terraform-ibm-modules/terraform-ibm-scc/blob/main/examples/basic/main.tf
Then add

en_instance_crn                   = # Event Notifications Instance CRN
en_source_name                    = # Same Event Notifications Instance Name

to security_and_compliance_center module.

Debug Output

https://gist.github.com/kierramarie/a8e72887cb8e411adcadf751b44313bb

Panic Output

Expected Behavior

A terraform apply should be run and no changes needed.

Actual Behavior

Plan: 0 to add, 1 to change, 0 to destroy. scc_instance_settings is planned to change when nothing in the terraform has changed.

Steps to Reproduce

1. Deploy resources - terraform apply
2. Run terraform apply again

Important Factoids

References

• #0000