You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@ocofaigh - there is a problem with using existing Event Notification instance with SCC.
It turns out that when the ibm_scc_instance_settings resource is used, it creates a source in the EN instance with the same name "compliance", so if two SCC instances are provisioned with this module, the second one trying to use EN will fails with the error about "source with the same name already exists.
It probably has to be fixed at the provider level as there is no name parameter in SCC instance settings resource, but when the integration is created in SCC UI, the source name is set to SCC instance name.
The effect of this is that when the DA is used to create a new SCC instance with referencing an Event Notifications service, any deployment after the first one fails because of the existing source name.
If a value is passed for
existing_en_crn
then the DA should also create EN destination, topic, and subscription.More info on how to do this with provider at: https://cloud.ibm.com/docs/event-notifications?topic=event-notifications-en-tera-workwith
The text was updated successfully, but these errors were encountered: