Exporting Should be Done in Deployment Pipeline to Allow for Multiple Environment Support

[bbrandt]

Example script that can be used in deployment pipeline to generate appsettings.json from multiple layers of configuration:

https://gist.github.com/bbrandt/60e7713b2826ce30e17b5752dfbeedd1

---

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

• ID: 48545e6e-02ea-1a4a-c74a-82af6513a7f7
• Version Independent ID: 916d7949-1a62-1d74-7cb5-1be816326ca7
• Content: Integrate Azure App Configuration using a continuous integration and delivery pipeline
• Content Source: articles/azure-app-configuration/integrate-ci-cd-pipeline.md
• Service: azure-app-configuration
• GitHub Login: @maud-lv
• Microsoft Alias: alkemper

[mike-urnun-msft]

Thank you for your feedback! We have assigned this issue to the author to review further and take the next course of action.

[zhenlan]

@bbrandt yes, you could run the same script at the deployment time to download and deploy the environment-specific configuration file with your application. The document shows an example of how to achieve it at the build time. Depending on what you build, it's not always feasible/easy to insert a configuration file into a build (for example, a container image) at the deployment time. Note that you can build environment-specific configurations at the build time, for example, from different git branches. Different teams may have different preferences.

[maud-lv]

Hi All, is there any further action needed to close this issue?