Skip to content

Latest commit

 

History

History
75 lines (51 loc) · 5.2 KB

AzureSpringCloudAppConfigurationConfig.md

File metadata and controls

75 lines (51 loc) · 5.2 KB

azure-spring-cloud-appconfiguration-config

Source code | Package (Maven) | README | Product documentation | Samples

azure-spring-cloud-appconfiguration-config-web

Source code web | Package (Maven) web | Product documentation

Active development has moved to group com.azure.spring and artifacts spring-cloud-azure-appconfiguration-config and spring-cloud-azure-appconfiguration-config-web. See SpringCloudAzureAppConfigurationConfig for more information.

2.5.0 - March 29, 2022

  • Add a refresh interval spring.cloud.azure.appconfiguration.refresh-interval that can be used to periodically reload all the key-value pairs in a configuration store. This can also be used to force update Key Vault References.
  • Added support for parsing and using sync-token from push notifications received from Event Grid. Using sync-token ensures that users get the latest key-values from App Configuration on any subsequent request.

2.4.0 - March 02, 2022

  • Dependency updates

2.3.0 - January 05, 2022

  • Fixed a bug where spring.cloud.application was still used in a location. This caused a refresh bug where a null value was used on refresh. spring.cloud.application has now been replaced by key-filter.

2.2.0 - November 25, 2021

  • Fixed a bug where content-type json configurations that used numbers literals inside of tables/lists wouldn't resolve.

2.1.1 - September 29, 2021

  • Fixed a bug where a watch key may not work as expected. If you use a key with no label as the watch key and delete the key in App Configuration, if the key has values with other labels, the key with another label could be used as the watch key.
  • Fixed a bug where adding or deleting a feature flag in App Configuration wouldn't cause the feature flag to be added or deleted in users' applications. #24049

2.1.0 - September 06, 2021

  • Added Health Monitor support with Spring Actuator. #21982

  • Added new API which allows users to configure the behavior when a Key Vault reference which cannot be resolved. KeyVaultSecretProvider can be used to resolve the references using its getSecret method, which provides a URI to the requested secret.

    @Bean
public KeyVaultSecretProvider keyVaultSecretProvider() {
    return new KeyVaultSecretProvider() {
        
        @Override
        public String getSecret(String uri) {

            ...

            return mySecret;
        }
    };
}

2.0.0 - July 22, 2021

  • Enables loading from multiple App Configuration stores.
  • Each store can load configurations by using key/label selects. Many selects can be used, default is key = /applicaiton/* with label = ${spring.profiles.active} or if null \0. See README for full configuration.
  • Authentication via Connection String, Managed Identity, or any method supported by Azure Identity SDK, see Token Credential Provider in README.
  • App Configuration stores can be monitored for changes. This is done by a specified configuration know as a trigger being checked in the App Configuration store on a set interval. Each individual App Configuration store can be enabled/disabled for monitoring and have a different interval in which they are checked. Monitoring can be done through either a Push or Pull model.
    • Pull Monitoring checks the config store for changes strictly based on how long it has been since the last check and activity in the application.
    • Push Monitoring has the App Configuration store notify the Application that configurations have changed through a web-hook.
  • Feature Flag loading can be enabled per config store spring.cloud.azure.appconfiguration.stores[0].feature-flags.enable
    • A single label can be used to load feature flags, default \0 i.e. (No Label).
    • A cache expiration can be set for feature flags.
  • Configurations can be set using: Key-Value, Key Vault Reference, Placeholder Values i.e. ${my.config}, Json