fix(stepfunctions): maxConcurrency does not support JsonPath #29319
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.
Issue # (if applicable)
Relates to #20835
Reason for this change
MaxConcurrency
does not supportJsonPath
. This change addsMaxConcurrencyPath
so that CDK users can specify aJsonPath
for theirMaxConcurrency
Note : This does not invalidate JsonPaths for
MaxConcurrency
, as I'm unsure how to do so without reverting #20279 . Open to suggestionsDescription of changes
Added a new
maxConcurrencyPath
field that accepts aJsonPath
value. Decided to go with another explicit field as it is similar to what is done forErrorPath
andCausePath
, in addition to most other Path fieldsDescription of how you validated changes
Added unit tests
Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license