Bring your data in Azure App Configuration down to your Kubernetes cluster, available as ConfigMap and Secrets and ready to be consumed by any workload.
MIT License
5
stars
3
forks
source link
Unable to refresh keys automatically without using sentinel #40
I have problem with receiving updates made in a Configuration Explorer. I don't want to use sentinel keys, I would like my provider to consume updates to all configuration values but the Config Map is not refreshed upon adding and updating configuration settings.
I tried specifying something like this but the error is: spec.configuration.refresh.monitoring: Required value
The documentation says that you can use a key-value to signal the completion of your update. This key-value is known as the sentinel key. Seems that it's something that you must use in order to consume the updates of all keys, not something you can use. Am I correct?
I expected the functionality to download updates to all configuration keys and their updates as the fundamental functionality of the provider but maybe I'm doing something wrong.
Sentinel key is required for refreshing now, the feature of refreshing by watching all keys is in our roadmap. Although we don't have an ETA of having this feature, it won't take very long I think.
I have problem with receiving updates made in a Configuration Explorer. I don't want to use sentinel keys, I would like my provider to consume updates to all configuration values but the Config Map is not refreshed upon adding and updating configuration settings. I tried specifying something like this but the error is:
spec.configuration.refresh.monitoring: Required value
The documentation says that
you can use a key-value to signal the completion of your update. This key-value is known as the sentinel key.
Seems that it's something that you must use in order to consume the updates of all keys, not something you can use. Am I correct?I expected the functionality to download updates to all configuration keys and their updates as the fundamental functionality of the provider but maybe I'm doing something wrong.