-
Notifications
You must be signed in to change notification settings - Fork 412
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
Feature request: Allow non-JSON schemas in Feature flags #1170
Comments
@whardier - shouldn't this about be resolved for feature flags? |
Referring to #804? No this issue relates to the payload coming from appconfig rather than subobjects. |
Update: Now that feature flags is stable (one incoming change for Time-based feature), I'd love to see a RFC on this for a Loader interface so to allow any input (YAML, TOML, canonical, etc.). |
Hi @whardier! Hope things are going well over there. It's been a long time since we've had updates on this issue, and we'd like to know if you can work on an RFC to implement this in Powertools. As @heitorlessa mentioned, the Thank you. |
We're closing feature requests older than a year that haven't received enough customers +1 or that we were unable to prioritize. For newer customers interested in, please feel free to comment and we can reopen it. |
|
Is your feature request related to a problem? Please describe.
Allow for callable transforms to be used (as well as the str "shortcuts").
Describe the solution you'd like
Pass something like yaml.loads or load_my_really_cool_serialized_data callable as transform argument toward parameter store fetches.
Describe alternatives you've considered
Due to how feature flags works.. we are unable to use yaml or any other loader before processing happens and this needs patched. Other approaches for parameters is to not pass a transform and then transform after the fact.
Additional context
PR already written up.
The text was updated successfully, but these errors were encountered: