Request: A mode for import/export that ignores whether the value of an existing key or feature flag is different, aka, create-only or net-new mode

[rrussell0]

I'm attempting to create a process in which my pipeline automatically adds new feature flags and configurations that are introduced to the repo's appsettings.json before a deployment occurs, but I do not want to have it overwrite/flip feature flags or configuration values if they differ from what is in code. I understand that this process is not pure configuration-as-code, but it's a scenario I am sure many would like to achieve as a sort of hybrid method.

In addition, it would be nice if the Compare panel would allow you to transfer configuration settings from one App Configuration resource to another.

Without these tools, I'm left basically manually examining the appsettings.json and adding the keys by hand - something I was hoping I could automate with App Configuration. I am sure I could achieve what I want with a long enough Powershell script, but it'd just be nice to have as a built-in option.

[jimmyca15]

@rrussell0 Thanks for filing a feature request for Azure App Configuration. I have not heard of usage like this before. I have a couple of questions:

• Is the scenario that your appsettings.json provide some sort of environmental defaults, that you may later override? I'm wondering if you can use label for this and override settings via a different label
• How does removing a flag/setting work without a source of truth? Or is that not a need?

[zhenlan]

Maybe another Import Mode that ignores key-values with matching key and label will do the trick. Basically, the appsettings.json is only used to add new key-values and feature flags. Other than that, what's in the App Configuration store is the source of the truth.

[zhenlan]

Not exactly the same, but similar ask in this old issue: #620