Currently, after a Project Set is deployed, any changes require manual modification of each respective main.tf file. For example, if a change is made to the azure-lz-vending template file, these changes are not applied to the existing Project Sets, and only affect net-new Project Sets.
We need to investigate, research, and discuss the best at-scale/long-term approach for applying and unifying changes across existing Project Sets. Additionally, this work could include investigation on how to still allowing for customizations to a Project Set.
Given the current manual modification of each main.tf file after deployment
When changes are made to a template file, such as azure-lz-vending
Then the issue should be resolved by implementing an at-scale/long-term approach for applying and unifying changes across existing Project Sets while still allowing customizations.
Currently, after a Project Set is deployed, any changes require manual modification of each respective
main.tffile. For example, if a change is made to theazure-lz-vendingtemplate file, these changes are not applied to the existing Project Sets, and only affect net-new Project Sets.We need to investigate, research, and discuss the best at-scale/long-term approach for applying and unifying changes across existing Project Sets. Additionally, this work could include investigation on how to still allowing for customizations to a Project Set.
Acceptance Criteria
main.tffile after deploymentazure-lz-vending