fix(stepfunctions-tasks): allow passing apiEndpoint as intrinsic function #31643
+43
−20
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 #29925
Closes #29925, #30749.
Reason for this change
The
apiEndpoint
prop currently only works when it's a string (ie.TaskInput.fromText('some/text')
), with the task failing when passed as a reference (ie.TaskInput.fromText(JsonPath.format('some/text/{}', '123')
). This is needed to allow for dynamic parts in the path.Description of changes
ApiEndpoint
task parameter to use theJsonPath.format
intrinsic function to combine theapiRoot
andapiEndpoint
props, instead of basic string concatenation.Description of how you validated changes
GET /testing
with basic auth Connection and was successfully invoked with task and payload{ "endpointName: "testing" }
:Checklist
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license