-
Notifications
You must be signed in to change notification settings - Fork 5
Feature flags: Support non-boolean values #71
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
Comments
Great idea. |
@alexsh-ca Thanks for the support! So they way I see it, is we add a new function and a new subsection for the complex engine in the json file and perhaps an updated schema (maybe add a new field for when_match field type etc.). |
@heitorlessa see aws-powertools/powertools-lambda-python#804 for a working POC |
Note that LaunchDarkly python library is completely un typed |
@michaelbrewer what do you mean? to my understanding, LaunchDarkly's API returns 'ANY' for an evaluated feature value. I was able to achieve this behavior in this PR. |
Just saying that powertools includes helpful type hinting. Where as LaunchDarkly just has none |
Hey @ran-isenberg thanks again for the initial implementation! This is available on 1.24 ;) |
Today, the utility feature flags support boolean flags.
The utility support only boolean values at the moment, hence the wording "flag".
The utility can support more complex rule match values. I'd like to be able to provide a session context and get back according to the rule engine a more complex object such as Dict, list etc.
The text was updated successfully, but these errors were encountered: