Merge existing configuration Azure Container Apps

We are using Azure Bicep to deploy and manage our Azure Containers. We do have two teams working on the Azure Containers, Cloud Infra technician and Developers. We have created a Bicep module so developers have only to enter there desired configuration. After the creation of the Azure Container Apps our developers rely on a subset of Azure DevOps pipelines to build and deploy there solution. Within those steps they are setting up some environment variables. But the only thing they need to do manually is to create an Azure Key Vault Secret and link this KeyVault secret to the secrets within the Azure Container Apps.

If we are running our Bicep template again the Configuration is gone, also with the Incremental feature. It would be great is it's possible to leave the existing configuration and deploy our Bicep template without touching this configuration. I saw some similar function within the Azure Function, this will provide you the opertunity to merge even existing configuration with some predefined Bicep Environment Variables or KeyVault Secrets.

Start by reproducing the Azure Bicep deployment of an Azure Container App, including an existing environment variable and linked Azure Key Vault secret. Review how incremental deployments handle Container Apps configuration and compare the behavior with the Azure Functions approach mentioned in the issue. Done means a Bicep deployment applies declared settings while preserving existing configuration that is not declared.

Written by the indexing model from the issue text.