AZD_INITIAL_ENVIRONMENT_CONFIG, github workflow and multiple environments

[Lindsay-Mathieson]

Currently have a modified azd pipeline generated github workflow for deploying to our Azure test env, works the best.

Want to update it for deployment to production as well - can create a new prod env easily, and set the AZURE_ENV_NAME in the workflow, but what about AZD_INITIAL_ENVIRONMENT_CONFIG?

If I update it for production with azd pipeline config won't it overwrite the test env parameters? or can azd handle multiple env in AZD_INITIAL_ENVIRONMENT_CONFIG?

[davidfowl]

This is an azd question, not really an aspire one. Though I will say the team is refining this because it's broken right now.

This is the first change: Azure/azure-dev#5143

The second is about being able to set different configuration values somehow. I don't know what azd supports nor what pipeline you are using, or where your state is stored, but those are great questions for: https://github.com/Azure/azure-dev

[Lindsay-Mathieson]

Thanks! most interesting.

I guess for now I can manually specify a different env var to azd provision, e.g secrets.AZD_INITIAL_ENVIRONMENT_CONFIG_PROD

The var just contains the config.json from the azd envi doesn't it?