In a scenario where there is a "central" deployment of the stack components (security / watson SaaS shared instances) and a number of dependent stack deployments with only watson sub-resources and separate ALM / application config instances I need to be able to refer to an existing resource group instead of provisioning a new one in the Account Infrastructure Base.
Essentially, the Account Infrastructure Base DA becomes just a reference point where I can provide an existing resource group so that other members of the stack can keep pointing to the output of the Account Infrastructure Base DA.
The resource groups for the subsequent / additional stack deployments may be managed by the central team along with the IAM permissions scoped to those resource groups. Therefore it may not be feasible for the additional stack deployments to be allowed to create their own resource group and/or modify the account settings.
This will probably require the Account Infrastructure Base DA to have options to suppress creation of resource groups and changes of account settings as well as the stack to have a parameter to indicate the usage of an existing resource group.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct
Description
In a scenario where there is a "central" deployment of the stack components (security / watson SaaS shared instances) and a number of dependent stack deployments with only watson sub-resources and separate ALM / application config instances I need to be able to refer to an existing resource group instead of provisioning a new one in the Account Infrastructure Base. Essentially, the Account Infrastructure Base DA becomes just a reference point where I can provide an existing resource group so that other members of the stack can keep pointing to the output of the Account Infrastructure Base DA.
The resource groups for the subsequent / additional stack deployments may be managed by the central team along with the IAM permissions scoped to those resource groups. Therefore it may not be feasible for the additional stack deployments to be allowed to create their own resource group and/or modify the account settings.
This will probably require the Account Infrastructure Base DA to have options to suppress creation of resource groups and changes of account settings as well as the stack to have a parameter to indicate the usage of an existing resource group.
New or affected modules
By submitting this issue, you agree to follow our Code of Conduct