Posted On: Jan 12, 2023
Today, AWS AppConfig announces new options for customers to track and clean up stale feature flags. Previously, customers needed to build their own schedules for managing stale feature flags. Now, customers can do this through AWS AppConfig. Feature flagging is a powerful technique that allows engineering teams to change application behavior on production without pushing out new code. By using feature flags, engineers can develop new capabilities, but hide them behind a feature flag configuration. Once ready to launch, AWS AppConfig allows you to roll flags out slowly. However, a common pain point with feature flags is the management of stale or unused flags. After a feature is launched, the flag may no longer be needed and becomes stale. Stale flags add clutter to your application code and configuration, and can make debugging your application challenging. Cleaning up unused flags improves application hygiene.
AWS AppConfig already allowed customers to designate a flag as ‘short-term.’ By indicating which flags are short-term, customers can find which flags are candidates for deprecation and removal. Now, engineers can also set an optional target deprecation date for each flag, and can sort and filter flags. Furthermore, flags that have passed their deprecation dates are labelled as overdue. The AWS AppConfig console now has has been updated with improved search and filtering capabilities as part of this release. These tools allow customers to better manage their flags and keep their application code and configuration easier to maintain.
This new capability for any workload using AWS AppConfig Feature Flags, including AWS AppConfig’s Feature Flags for AWS Lambda and Feature Flags for Amazon ECS and Amazon EKS.
AWS AppConfig’s feature flag deprecation and clean up tools are available in all AWS Regions, including the AWS GovCloud (US) Regions. To get started, use the AWS AppConfig Getting Started Guide.