When deploying apps and services using the toolchain, there is no way to target a specific resource group. For example, the logistics-wizard-erp-db service creation will create a Cloudant-XX instance in the default resource group. The default group is used even though the user may elect to add the toolchain to another resource group, which leads to confusion over where resources actually reside.
Fixing this would require:
Defining a resource group textbox in the deploy.json similar to this example.
Passing the intended resource group into the pipeline yamls
Within each app deployed by the toolchain, the respective DEPLOYment script needs to be updated to include a target -g <resource group> command similar to this example,
When deploying apps and services using the toolchain, there is no way to target a specific resource group. For example, the
logistics-wizard-erp-dbservice creation will create aCloudant-XXinstance in thedefaultresource group. Thedefaultgroup is used even though the user may elect to add the toolchain to another resource group, which leads to confusion over where resources actually reside.Fixing this would require:
target -g <resource group>command similar to this example,