Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
Is your feature request related to a problem?
Not really
Describe the solution you'd like
I have customers confused about how to start from scratch, mostly about secrets and TF state. In some Microsoft docs we seem to recommend using Azure Storage and Azure Keyvault (such as in the CAF TF module), but in the ALZ docs we don't have any guidance about it. IMHO we should have some brief paragraph. Even if we want to be agnostic to where customers keep their state and secrets, it would be worth describing the different options, like:
Having it in Azure: manually create a subscription in the same tenant with just a storage account and an AKV
Use the equivalent services of other public clouds
Use Hashicorp native services, such as Hashicorp Cloud and Hashicorp Vault
Additional context
Here you can find the "launchpad" concept in the CAF TF module, which doesn't have any equivalence in the ALZ TF module.
Community Note
Description
Is your feature request related to a problem?
Not really
Describe the solution you'd like
I have customers confused about how to start from scratch, mostly about secrets and TF state. In some Microsoft docs we seem to recommend using Azure Storage and Azure Keyvault (such as in the CAF TF module), but in the ALZ docs we don't have any guidance about it. IMHO we should have some brief paragraph. Even if we want to be agnostic to where customers keep their state and secrets, it would be worth describing the different options, like:
Additional context
Here you can find the "launchpad" concept in the CAF TF module, which doesn't have any equivalence in the ALZ TF module.