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
feat(pipes-targets): add step function target #29987
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
1db8840
to
d35ec0c
Compare
✅ Updated pull request passes all PRLinter validations. Dismissing previous PRLinter review.
@@ -1 +1,2 @@ | |||
export * from './sqs'; | |||
export * from './step-function'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please make sure these are named consistently
export * from './step-function'; | |
export * from './stepfunctions'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking a look already :)
Currently its consistent using step-function
everywhere (as far as I can tell). Should I change it to the plural version of it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you mean "everywhere"? I was referring to the module name which is aws-stepfunctions
.
(You might totally be right about this by the way)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How do you mean "everywhere"?
I meant all the filenames inside this PR.
I was referring to the module name which is aws-stepfunctions.
Ah I think I know now what you meant. The package name/cdk module name is aws-stepfunctions
and I should keep that name consistent also in this pipes-targets module, changed it to stepfunctions :)
I kept the name StepFunctionTarget
if you think I should change that as well let me know.
@@ -63,3 +68,42 @@ const pipe = new pipes.Pipe(this, 'Pipe', { | |||
target: pipeTarget | |||
}); | |||
``` | |||
|
|||
### AWS Step Function |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
### AWS Step Function | |
### AWS Step Functions |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch! Changed it
d35ec0c
to
141dbf5
Compare
Co-authored-by: RaphaelManke <RaphaelManke@users.noreply.github.com>
141dbf5
to
08d94b7
Compare
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@mrgrain just wanted to ask if there is something else I should change or does an additional person needs to review my PR (or I just need to wait a bit more)? |
Someone else should get around to this eventually. I'm not actually working on the CDK anymore 🙈 |
Thanks, appreciate it! Lets hope its not necessary :D |
Issue #29665
Closes #29665
Reason for this change
Step Function target is not supported yet by pipes-targets.
Description of changes
invocationType
a required parameter, since this made the code clearer and make users aware of how they want the step function to be invoked.The AWS::Pipes::Pipe PipeTargetStateMachineParameters has this as an optional parameter (defaulting to Request-Response), which can lead the user unknowingly in a broken pipe, because cdk's StateMachines default to Standard Workflow, which is not compatible with Request-Response Invocation Type.
Description of how you validated changes
Checklist
I've talked with @RaphaelManke and he was fine for me opening up a PR (put him as a co-author nevertheless) :)
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license