-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
aws-stepfunctions-tasks: Support for new HTTPS Endpoint integration #28278
aws-stepfunctions-tasks: Support for new HTTPS Endpoint integration #28278
Comments
Thanks @MathieuGilbert for submitting this request and volunteering for the PR contribution. |
@MathieuGilbert hey there, do you already use this with a workaround? would also love to contribute somehow as I desperately need this construct :D |
Hi @boringContributor, we aren't using this yet, but have plenty of Lambdas doing this manually which we'd love to replace. I have an initial implementation of this, I just need to find the time to test & polish it, hopefully this coming week. |
@boringContributor Just wanted to update you as I've made some progress and have a WIP draft PR here. I tested it out by copying the construct to an existing project and it works if the Connection is set up right. It can be used that way if you don't want to wait for it to make it into the library. The only internal import can be hard-coded as |
This adds an `HttpInvoke` Step Functions task construct, which allows calling public APIs as described [here](https://docs.aws.amazon.com/step-functions/latest/dg/connect-third-party-apis.html). - Accepts an Event Bridge API Destination `IConnection`, setting required permissions to use its credentials. - Grants permission to invoke the root path for the endpoint (`apiRoot` prop). This allows passing the relative endpoint path at execution time (`apiEndpoint` prop). - Defines an enum for the allowed options for the URL encoding style of arrays, used when encoding the request body. Closes #28278 ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
|
Describe the feature
Support for the newly released HTTPS Endpoints Step Functions integration:
Use Case
CDK should support the HttpInvoke Step Functions integration, so it can be managed via IaC.
Proposed Solution
Task should allow specifying all standard, optional, and required parameters (endpoint, HTTP method, EventBridge Connection ARN, headers, body, query string, etc.).
Other Information
No response
Acknowledgements
CDK version used
latest
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered: