When setting up any azure pipeline with terraform, I am constantly faced with the management of the standard secrets needed for the terraform to run, we use Azure Pipelines and leverage libraries backed by an Azure Key Vault, the problem has been that azure key vault does not support _ (underscores).
I have found a post on the Azure Key Vault “user voice” (Community) which is 4 years old and still not implemented.
I thought I would ask if there is an option to do anything from the hashicorp / terraform side.
Setting it so that terraform could handle environmental values in the form of ARM_TENANT_ID and ARM-TENANT-ID (and the others), would then allow the process to automatic set those values.
below is a mapping example in the pipeline that is needed in order to push the key vault secret into the environmental equivalent for terraform to pick up.
env: ARM_TENANT_ID: $(ARM-TENANT-ID) ARM_CLIENT_ID: $(ARM-CLIENT-ID) ARM_CLIENT_SECRET: $(ARM-CLIENT-SECRET) ARM_SUBSCRIPTION_ID: $(ARM-SUBSCRIPTION-ID) ARM_ACCESS_KEY: $(ARM-ACCESS-KEY)