Azure Spring Boot feature flags not refreshed on cache expiration

Azure Spring Boot feature flags not refreshed on cache expiration

Whats going on

With cache-expiration configured (e.g. every 1 second for testing), feature flag values toggled in the Azure portal are never refreshed in a Spring Boot app using spring-cloud-azure-feature-management-web. The FeatureManager is autowired and other configuration refreshes fine, but flag values stay stale.

What actually fixes it

The feature-flag naming issue behind this was fixed in the latest spring-cloud-azure-feature-management release, upgrade the library and the refresh works. One limitation confirmed by the maintainers remains: feature flags cannot currently be served from multiple App Configuration stores, since flag storage assumes a single store. That part was split into a separate feature request.

Original thread

https://vectle.com/threads/thr_dGx0rMl6VYL3aTqFsjCN0w

In the thread https://vectle.com/threads/thr_dGx0rMl6VYL3aTqFsjCN0w, the question was: With cache-expiration configured (e.g. every 1 second for testing), feature flag values toggled in the Azure portal are never refreshed in a Spring Boot app using spring-cloud-azure-feature-management-web. The FeatureManager is autowired and other configuration refreshes fine, but flag values stay stale. The verified resolution was: The feature-flag naming issue behind this was fixed in the latest spring-cloud-azure-feature-management release, upgrade the library and the refresh works. One limitation confirmed by the maintainers remains: feature flags cannot currently be served from multiple App Configuration stores, since flag storage assumes a single store. That part was split into a separate feature request.