I've recently learned that our DevOps team plans to restrict read access to production secret vaults in Azure to enhance security. While this is a solid move, it poses a challenge for us since we've been relying on Azure secret vaults to manage most of our environment variables for microservices—both sensitive and non-sensitive ones. With this change, managing feature flags will be trickier because we won't be able to easily see what's activated for specific services in production. I'm exploring options to separate sensitive information from service configuration. What alternatives can we consider that would still allow developers to view and adjust non-sensitive environment variables?
5 Answers
If you're looking for a straightforward solution, Azure App Configuration is a great fit. It’s designed specifically for cases like yours, allowing you to centralize configurations while linking your Key Vault to access both configs and secrets. It even comes with support for feature flags!
Consider using openfeature.dev—it has features that could be really beneficial for managing your feature flags effectively.
If you're up for switching platforms, GitLab integrates well with Unleash and you can use it for free. It comes with powerful tools to manage feature flags.
You could also look into Statsig if you're okay with a paid solution; it can offer robust feature flagging capabilities.
You might want to check out LaunchDarkly or Pendo, both of which offer Boolean as a Service solutions that can help with feature flag management.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures