In a scenario where the stack is deployed while re-using most of the resources (security services, Watson SaaS), I would like to be able to configure the stack variables to skip provisioning a new SCC instance. At some point I might still want to be able to create some attachments, but currently the SCC DA does not have much fine-grained control over that.
At the moment, I would have to just not deploy the SCC DA if I do not want to create a new SCC instance. Another option is to just delete that member DA from the stack instance in the project. Neither option would work if we will be creating SCC attachments through the stack while re-using the instance.
This feature would probably require a change in the SCC DA as well (to enable using an existing instance) or a change in stack framework that allows to override the stack member with pre-defined output values - to keep any wiring within the stack intact.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct
Description
In a scenario where the stack is deployed while re-using most of the resources (security services, Watson SaaS), I would like to be able to configure the stack variables to skip provisioning a new SCC instance. At some point I might still want to be able to create some attachments, but currently the SCC DA does not have much fine-grained control over that.
At the moment, I would have to just not deploy the SCC DA if I do not want to create a new SCC instance. Another option is to just delete that member DA from the stack instance in the project. Neither option would work if we will be creating SCC attachments through the stack while re-using the instance.
This feature would probably require a change in the SCC DA as well (to enable using an existing instance) or a change in stack framework that allows to override the stack member with pre-defined output values - to keep any wiring within the stack intact.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct