Cap resolve_value permutations to prevent exponential blowup#4394
Merged
kddejong merged 1 commit intoaws-cloudformation:mainfrom Mar 23, 2026
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4394 +/- ##
==========================================
- Coverage 93.54% 93.44% -0.10%
==========================================
Files 418 422 +4
Lines 14145 14319 +174
Branches 2817 2858 +41
==========================================
+ Hits 13232 13381 +149
- Misses 567 581 +14
- Partials 346 357 +11
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
When deeply nested functions (Fn::If, Fn::Select, etc.) are resolved against schemas with value constraints, the number of condition permutations can grow exponentially. Cap at 512 yields per resolve_value call as a safety valve — best effort validation beyond that point.
5afc88d to
76c7330
Compare
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
1 participant
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.
When deeply nested functions (Fn::If, Fn::Select, etc.) are resolved against schemas with value constraints, the number of condition permutations can grow exponentially. Cap at 512 yields per resolve_value call as a safety valve — best effort validation beyond that point.
Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.