-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
feat(flags-hackathon): Encrypted payloads on remote config feature flags #27414
base: master
Are you sure you want to change the base?
Conversation
…ypted-config-flags
…o encrypted-config-flags
…ypted-config-flags
…o config-flags
…o encrypted-config-flags
📸 UI snapshots have been updated2 snapshot changes in total. 0 added, 2 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
📸 UI snapshots have been updated1 snapshot changes in total. 0 added, 1 modified, 0 deleted:
Triggered by this commit. |
…ypted-config-flags
…ypted-config-flags
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
I'll provide a concise summary of the key changes in this PR for adding encrypted payloads to remote config feature flags:
Added support for encrypting sensitive payload data in remote configuration feature flags, with a focus on secure access through personal API keys.
- Added new
has_encrypted_payloads
field to feature flag model with corresponding UI controls and database migration - Added encryption/decryption helpers in
encrypted_flag_payloads.py
for secure payload handling - Added new
/remote_config
endpoint for fetching decrypted values when authenticated with personal API key - Limited encrypted payload support to API SDK initially (with plans to add Node.js, Python, Go, Ruby later)
- Added "Remote config" filter option in feature flags table for better discoverability
The changes are well-structured across frontend and backend with proper validation and access control in place.
18 file(s) reviewed, 11 comment(s)
Edit PR Review Bot Settings | Greptile
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few additional questions on top of greptile yapping (tbh I think the greptile yaps were mostly pretty good; what a neat tool)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few additional questions on top of greptile yapping (tbh I think the greptile yaps were mostly pretty good; what a neat tool)
…ypted-config-flags
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
…ypted-config-flags
…ypted-config-flags
…osthog into encrypted-config-flags
📸 UI snapshots have been updated7 snapshot changes in total. 0 added, 7 modified, 0 deleted:
Triggered by this commit. |
…osthog into encrypted-config-flags
…ypted-config-flags
Problem
Follow-up to #27376 - adds support for encrypted payloads
Changes
Demo:
https://drive.google.com/file/d/1punn1c1yV2CXhsJ4ajelh89Mndqvz64n/view
retrieve
andlist
callsGET .../feature_flags/:flagId/remote_config
for fetching decrypted payload values when authenticated with personal API keyDoes this work well for both Cloud and self-hosted?
No differences
How did you test this code?
Added visual regression tests, will add/update API tests as well