Skip to content
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

[SCC DA] Add support to create EN destination, topic, and subscription #85

Closed
ocofaigh opened this issue May 15, 2024 · 1 comment
Closed
Assignees

Comments

@ocofaigh
Copy link
Member

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

@in-1911
Copy link

in-1911 commented Aug 7, 2024

@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.

^^ Moved that comment to #162

@ocofaigh ocofaigh closed this as completed Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants