Ability to incrementally create/update AppSettings & ConnectionStrings
Today if we don't provide all of the existing AppSettings or ConnectionStrings, the ones we omit are removed.
A little bit like the ARM deployment mode, add the ability to specify an Incremental & Complete mode when pushing settings. To ensure compatibility, Complete would be the default, keeping the behavior we have today. If we set the mode to Incremental, only the provided settings would be created/updated, leaving existing settings untouched.
This would be very useful in cases where we want to sync AppSettings or ConnectionStrings for resources directly in our ARM templates for only a subset of settings and/or connectionStrings from a ARM template without deleting the existing settings that are not provided.
Thanks for the suggestion, we are looking into the feature request
Azure App Service Team
+1 Any news???
David Smith (US) commented
Any way we can get clarification on what "We are looking into the feature request." means? Three years later and we've still got absolutely nothing...
Adrien Uwin commented
+ 1 . we would appreciate having this feature in ourcompany.
Vasyl Kutsyk commented
How is it going with this one?
Brandon Hurlburt commented
Any update on this, Ahmed?
Klotz, Anthony commented
We need this fixed. I can't maintain my Azure functions with an ARM template because it is replacing existing settings that are not referenced in the deployment template or parameter template. I complained about this in a stackoverflow post.
My initial testing with Azure CLI gave me the impression that appsettings would be merged, but the Azure API is different than how powershell cmdlet works
Henrik Sommer commented
An ide could be to follow the same standard as Microsoft.KeyVault/vaults/accessPolicies
where you set name: add, replace, remove
Klotz, Anthony commented
Need some traction on this. I want to use template functions to generate dynamic appSettings in the primary template using existing resources. Then I follow up with another site/config "appsetting" to input more application settings, but I lose the initial values.
Please do this...
Brett Parton commented
Joe Ristine commented
I also think this would be helpful. We'd like an option to be able to incrementally add/update application settings and connection strings. If there's an override we need to set for a certain app service, it currently gets overwritten with each ARM deployment.
Jonas Schmied commented
Are there any news on this? It really would be helpful and enable incremental deployments with ARM templates. As we often work with linked templates, we need to pass many out-of-context-parameters.