Every day, we talk to teams that use feature flags to drive their modern software development process—simplifying deployments or providing much-needed flexibility to roll changes to groups of users and targets to implement progressive delivery. After the software release is complete and the user experience verified, the flag has served its purpose, and it’s time to delete it - first from the code, then from Harness. Once in a while, though, someone deletes a flag before removing it from the code.
Deleting a feature flag can result in the wrong values being served to your end customers, as Harness Feature Flags will fall back to the in-code default rule if it can’t find a flag configuration to serve. Having this happen in a production environment can enable or disable specific features that a product manager didn’t intend for the user base, creating an urgent issue needing resolution. Until now, when this happened, you’d have to create a new feature flag with a matching identifier to the deleted flag and recreate the flag-specific configuration. With the introduction of flag archiving into our feature flag management lifecycle, a user can just click restore flag.
Harness makes archiving a flag through the normal flag management process easy.
Developers can restore this flag within 30 days, otherwise, the archived flag will be deleted.
Developers change, update, and create code every day. At Harness, we are addressing developer toil across the entire software delivery lifecycle to decouple the code deployment from feature releases. Removing the burden of complex lifecycle flag management is a straightforward improvement this new feature provides.
Create a free Harness Feature Flag account and leverage our Harness Developer Hub documentation on archiving and restoring flags.
Enjoyed reading this blog post or have questions or feedback?
Share your thoughts by creating a new topic in the Harness community forum.