tquinn86/advent-of-code-2022

Working through Advent of Code 2022

advent-of-code-2022's Issues

[FF]

What is the name of your feature flag?

What is its purpose?

Feature Flag Rollout Checklist

See feature flag documentation here.

• Create a feature flag that is fully disabled for everyone and use it to control access to your new feature.
• Develop and test your changes locally. You can enable the feature flag in local developer environments for test purposes.
• Make sure that you test your code with the feature flag enabled and disabled to make sure both sides of the flag operate as expected with your changes.
• Deploy your software to all environments with the feature flag fully disabled.
• Enable your feature flag for a limited testing audience to build confidence. Examples are staff shipping using the preview_features group or directly assigning access to a small subset of users/repos/businesses.
• Slowly rollout your flag across environments by slowly incrementing access to wider audiences. This can be done with percentage of users or percentage of calls increases (e.g. 2%, 10%, 30%, 50%, etc.). If you detect any problems you can immediately reduce your rollout percentage or fully disable the feature flag. Various rollout strategies are possible using the different capabiities of the feature flag control gates (percentages, actors, custom groups, targeting specific environments like dotcom/proxima stamps).
• At each stage of rollout monitor your changes for impacts to defects, error rates, performance and resource demands.
• Once you have confidence in your feature and no reported or observed issues fully enable your feature flag for all environments.
• For a period of time monitor the feature flag for stability and schedule removal of the feature flag. First remove the conditional code that uses the feature flag and once all of it is deployed and showing no impacts, remove the feature flag itself.