Source name in event notification instance defaults to 'compliance' when using "ibm_scc_instance_settings" resource

[iamar7]

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

Terraform v1.5.7

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/tree/main/examples/complete

Expected Behavior

The source shouldn't be set as "compliance" by default or there should be an option to set the source name.

Actual Behavior

It sets the source in the event notification instance with the name "compliance". As a result, if two SCC instances are provisioned using this module, the second instance attempting to use the EN will fail with an error stating that a source with the same name already exists.

Steps to Reproduce

Clone the repository and then follow the following steps:-

1. Go to the complete example directory
2. export TF_VAR_ibmcloud_api_key="xxxxxxXxxxxxxXxxxxxxXXxxxxxxxxXXXX"
3. terraform init
4. terraform plan
5. terraform apply

Important Factoids

References

• #0000

[tyao117]

allowing this capability would be difficult to incorporate because the endpoint used to READ the settings doesn't return back the source_name

[iamar7]

@tyao117 what is happening due to the above issue is that when the scc-da is used to create a new SCC instance with referencing an existing Event Notifications service, any additional project/configuration using SCC module fails because of the existing source name. Also, it is not optimal to create a separate EN instance for SCC instance.