I'm using an azure devops pipeline to push a json config file to azure app config. According to the documentation there's a setting that can be enabled:
Delete all other Key-Values in store with the specified prefix and label: Default value is Unchecked. Checked: Removes all key-values in the App Configuration store that match both the specified prefix and label before pushing new key-values from the configuration file. Unchecked: Pushes all key-values from the configuration file into the App Configuration store and leaves everything else in the App Configuration store intact.
When the setting is enabled, it sounds as if the operation performs two steps: a delete and then an update. I don't want that the application checks for config to find it missing.
Is it possible to update all the config at once atomically, like a http put?
From the App Configuration service perspective, each key-value is always updated (and deleted or created) individually via separate requests, so there is no atomic operation when changes of multiple key-values are involved. Applications should be designed to be tolerable of the transitioning states. Alternatively, you can consider using other mechanisms to notify applications what is good timing to pick up/refresh configuration.