- MINOR SCALE PATCH
- MINOR SCALE UPGRADE
- MINOR SCALE CODE
Patch versions are typically used when one or more of the following is true: Updates to policies which impact Policy Assignments (resulting in potential loss of compliance history).
MINOR SCALE CODE
Minor updates will be needed for customer code before being able to successfully run terraform plan, such as simple edits to one or more input variables.Existing resources will be recreated without direct customer impact (such as redeployment of Azure Policy resources, or Roles).Addition of new input variables with a default value.A new feature is being enabled which is configured through new input variables.New resources will be added to the customer environment, but only if a new (optional) setting is explicitly enabled.New resources will be automatically added to the customer environment without impacting existing resources managed by the module (such as addition of the new Log Analytics solutions in release v2.1.0).Minor versions are typically used when one or more of the following is true:
MINOR SCALE UPGRADE
NOTE: When publishing major releases we will always provide a detailed upgrade guide to help with the upgrade experience.
Addition of new input variables without a default value. Changes to default values which would result in unexpected changes to deployed resources. Existing resources will be recreated with direct customer impact (such as redeployment of networking resources). A significant change is needed to the customer code which requires careful consideration before being able to successfully run terraform plan. Adding significant functionality to the module (such as the addition of the Virtual WAN capability in release v2.0.0). Major versions are typically used when one or more of the following is true: Whilst we try to follow the published Semantic Versioning 2.0.0 guidelines, module releases are typically versioned according to the following: Major releases In most cases, we will include the following information: Releases are tagged based on Semantic Versioning 2.0.0 and release notes will always outline the changes being introduced. This also allows customers to implement recommended practices for consuming modules using versioning, mitigating the risk of unexpected or unwanted changes. This approach allows us to release updates in a controlled manner, helping customers to manage change effectively. The Azure landing zones Terraform module is designed to be published and consumed through the Terraform Registry. Deploy using multiple module declarations with remote state. Deploy using multiple module declarations with orchestration. Create custom policies, initiatives and assignments. Deploy management resources with custom settings. Deploy identity resources with custom settings. Deploy connectivity resources with custom settings (Virtual WAN). Deploy connectivity resources with custom settings (Hub and Spoke). Set parameter values for Policy Assignments. Deploy connectivity resources (Virtual WAN). Deploy connectivity resources (Hub and Spoke).
0 kommentar(er)
