[PM-34500] Fix Feature Flag pm-34500-strict-cipher-decryption name casing#7460
Merged
Conversation
jengstrom-bw
approved these changes
Apr 13, 2026
|
Contributor
|
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #7460 +/- ##
=======================================
Coverage 58.49% 58.49%
=======================================
Files 2066 2066
Lines 91140 91140
Branches 8111 8111
=======================================
+ Hits 53308 53309 +1
+ Misses 35924 35923 -1
Partials 1908 1908 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-34500
📔 Objective
The feature flag name was copied from Launch Darkly, but it turns out the actual key used is all lower-case. This fixes the feature flag key name so it comes back in the
/configresponse.