Azure / Azure/Azure-Landing-Zones
bootstrap-modules parameterise backendAzureStorageAccountContainerKeyName
- Dominant language
- PowerShell
- Stars
- 96
- Forks
- 70
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 7
Description
### Is there an existing issue for this?
- [x] I have searched the existing issues
### Infrastructure as Code Type? (Required)
terraform
### Starter Module? (Required)
terraform - platform_landing_zone
### Use Case (Required)
Customise the name of target tfstate file, this then allows for the pipelines and templates to be used to deploy resources outside of the alz modules and store their states in the same storage account. i.e Identity Virtual Network and Domain Controllers.
### Proposed Solution (Required)
Add following parameter to both the CD-Template and main cd pipelines and GitHub actions, this then alllows a user to simply override the default value of terraform.tfstate.
- name: backendAzureStorageAccountContainerKeyName
Could look exactly like how you have parametrised the terraform version recently Azure/accelerator-bootstrap-modules#76

### Important Factoids (Optional)
_No response_
### References (Optional)
_No response_
Contributor guide
Research direction
Start in the terraform - platform_landing_zone starter module and inspect the CD-Template, main CD pipelines, and GitHub Actions. Compare how the Terraform version parameter was added in Azure/accelerator-bootstrap-modules#76. Done means users can override backendAzureStorageAccountContainerKeyName instead of the default terraform.tfstate across the listed deployment entry points.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, github-actions, terraform
- Domain
- ci-cd, cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100