[SERVER-69212] Allow multiple feature-flag checks within a single operation Created: 26/Aug/22 Updated: 14/Jun/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
When developing new features using the feature flag system, the code that needs to be guarded behind the feature flag may be spread out over different components making it difficult to re-use a single feature flag call. In practice to work around this, you would create a decoration on the OperationContext to be able to re-use the one allowed feature-flag check. We would simplify the usage of feature flags if multiple feature-flags checks would be allowed and consistent. This can be implemented for example by automatically storing a copy of the feature flag state in the OperationContext. |
| Comments |
| Comment by Samyukta Lanka [ 29/Aug/22 ] |
|
This is a problem for checking different feature flags as well over the course of one operation. The solution should try to take that into account as well. |