Description
Description
As an engineer, I would like to track what infrastructure is deployed to an environment from a shared/remote backend, so that the deployment changes can be determined from any machine.
Acceptance Criteria
scenario 1: deployment with no existing resources
given a deployment is defined to deploy the following resources
- resource group 'core-use-rg-dev-cblt'
- vnet 'core-use-rg-dev-cblt' in resource group 'core-use-rg-dev-cblt'
- key vault 'core-use-kv-dev-cblt' in resource group 'core-use-rg-dev-cblt'
and none of the above resources exist
when the deployment is executed
then the following resources are created
- resource group 'core-use-rg-dev-cblt'
- vnet 'core-use-rg-dev-cblt' in resource group 'core-use-rg-dev-cblt'
- key vault 'core-use-kv-dev-cblt' in resource group 'core-use-rg-dev-cblt'
scenario 2: deployment with some existing resources
given a deployment is defined to deploy the following resources
- resource group 'core-use-rg-dev-cblt'
- vnet 'core-use-rg-dev-cblt' in resource group 'core-use-rg-dev-cblt'
- key vault 'core-use-kv-dev-cblt' in resource group 'core-use-rg-dev-cblt'
and the following resources exist and were deployed from machine a
- resource group 'core-use-rg-dev-cblt'
- vnet 'core-use-rg-dev-cblt' in resource group 'core-use-rg-dev-cblt'
when the deployment is executed machine b
then the following resources are created
- key vault 'core-use-kv-dev-cblt' in resource group 'core-use-rg-dev-cblt'
scenario 3: deployment with all resources existing
given a deployment is defined to deploy the following resources
- resource group 'core-use-rg-dev-cblt'
- vnet 'core-use-rg-dev-cblt' in resource group 'core-use-rg-dev-cblt'
- key vault 'core-use-kv-dev-cblt' in resource group 'core-use-rg-dev-cblt'
and the following resources exist and were deployed from machine a
when the deployment is executed from machine b
then no new resources are created
Notes
Use multiple directories (clone) to simulate executing the templates from different machines.
Out of scope
Automating the creation of the storage account (remote backend)