Repository navigation
Tech debt: Feature Flags validates the full schema on every evaluate(), including cache hits #8426
Description
Why is this needed?
FeatureFlags.get_configuration() constructs a new SchemaValidator and walks the whole document on every call. evaluate() and get_enabled_features() each call it, so a handler that evaluates five flags validates the entire document five times per invocation, even when AppConfigStore served the document from the Parameters cache without a network call. For documents with many flags and rules this is wasted CPU on every request.
Which area does this relate to?
Feature Flags
Suggestion
Validate once per fetched document. Options: memoise on id() of the returned dict (the Parameters cache returns the same object until expiry), or have StoreProvider expose a version/etag and cache the validation result against it. Either keeps the "always validate fresh configuration" guarantee while skipping repeat work on cache hits.
Acknowledgment
- This request meets Powertools for AWS Lambda (Python) Tenets
- Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET
Activity
powertools-for-aws-oss-automation commentedon Sep 14, 2026
Warning
This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
perf(feature_flags): validate schema once per fetched document (aws-p…
github-actions commentedon Sep 15, 2026
This is now released under 3.35.0 version!