Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Trimming and Feature Flags #625

Open
rossgrambo opened this issue Feb 21, 2025 · 1 comment
Open

Trimming and Feature Flags #625

rossgrambo opened this issue Feb 21, 2025 · 1 comment

Comments

@rossgrambo
Copy link
Member

Feature flags are transformed by our adapter into keys looking like:

{[FeatureManagement:Alpha, False]}

The TrimKeyPrefix happens after this transformation. Meaning trimming any of the following would cause the feature flag to be unreadable (no longer in the expected "FeatureManagement" section):

.TrimKeyPrefix("f");
.TrimKeyPrefix("fe");
.TrimKeyPrefix("fea");
.TrimKeyPrefix("feat");
// etc

Trimming usually has some sort of divider which helps mitigate this- but I think trimming in it's current state and feature flags simply don't make sense to interact.

I propose we do not trim the key value if we know it is a feature flag. This is not a breaking change- as any trimming of a feature flag today would break it from being a feature flag. (You could trim a FF into acting like a normal KV by removing the full "FeatureManagement"- but I suspect little to no one has a dependency shaped like that)

@jimmyca15 @zhiyuanliang-ms @samsadsam

@samsadsam
Copy link
Contributor

Agree with the proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

2 participants