Background
In T388036, we were surprised to learn that the behavior of base in our feature management system is different than common understanding. As a result, there is at least one known case of us rolling out a feature with the configuration base: true and loggedin: false, which is inadvertently targeting logged in users
We want to check our production configurations and document all the cases where base is true, but the configuration suggests it was not intended to target everyone
Additionally, we want to document all cases where base is true regardless, as these would potentially be impacted by a change implemented as part of T388202
User story
As a member of the web team, I want to be confident that my features are configured properly and rolled out to the correct audiences
Requirements
[ x] production configurations are audited for cases where base is true
[x ] state of the world is documented in this ticket, with a team discussion accompanying any similar cases where our rollout is presumed incorrect (base is true and other modes are false)
[ x] additionally, an overall view of the usage of base is provided in the ticket, which will inform and unblock work on T388202
[x ] followup tickets are created if necessary
Acceptance criteria
- We are confident that the full impact of this bug is understood
- We have a plan and path forward for anything that comes up as part of this investigation
- T388202 is able to be scoped and estimated, with the understanding of what the impact of changing the existing definition of base would have
Rollback plan
No code is being written for this task, so it's not something that can be rolled back, per se