Original Summary

I watched several teams struggle with feature flags. Clients sat down to test a feature and found it switched off in their environment. A flag would be on in staging and off in production with nobody sure why, and Azure's revision history doesn't record who changed it. No one owned the flags, so they never got removed after a rollout. So I built Flagsweep. It runs next to Azure App Configuration and: shows every flag as one row, with its state in each environment records who changed which flag, in which environment and when, with the old and new values marks flags that were changed outside Flagsweep, in the portal, the CLI or a pipeline gives every flag an owner and a retire-by date, 90 days out by default The flags stay in Azure and apps keep reading them with the SDKs they already use. It's a .NET 10 API with a React front end and SQLite, shipped as one Docker image under Apache-2.0. There's a sandbox mode with demo flags if you want to try it without an Azure account. This first release handles boolean flags on Azure only. AWS AppConfig is next. I'd like to know two things: does the site make it clear what this does, and what would stop you from trying it? Site and docs: https://flagsweep.com Code: https://github.com/flagsweep-hq/flagsweep   submitted by   /u/Neat-Ad-7906 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/9/28 15:26:24