This repo provides examples of using two auto-tagging frameworks for deploying resources into Azure; terratag and yor. The frameworks automatically add git metadata tags to the resources being deployed - without commit those changes to the git repo - to facilitate traceability of those resources in the Azure Portal. Essentially, they provide answers to the questions, "What, where, when deployed these resources?".
The repo deploys an Azure Storage Account in three different ways:
- using a resource block
- using a module block, where the source is defined in a local "modules" folder
- using a module block, where the source is from the Terraform registry
This will provide proof that the frameworks can handle the three different approaches to deploying a resource.
| Name | Version |
|---|---|
| terraform | >= 1.7.0 |
| azurerm | >= 3.0 |
| Name | Version |
|---|---|
| azurerm | 3.105.0 |
| Name | Source | Version |
|---|---|---|
| local_storage_account | ./modules/test | n/a |
| naming | Azure/naming/azurerm | >= 0.4.1 |
| remote_storage_account | Azure/avm-res-storage-storageaccount/azurerm | >= 0.1.1 |
| Name | Type |
|---|---|
| azurerm_resource_group.this | resource |
| azurerm_storage_account.this | resource |
| Name | Description | Type | Default | Required |
|---|---|---|---|---|
| default_subscription_id | ID of default subscription to which this deployment should be made. | string |
n/a | yes |
| environment | The environment in which the resources will be created. | string |
n/a | yes |
| location | The location/region where the resources will be created. | string |
n/a | yes |