Skip to content
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.

Sign up for GitHub

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

Jump to bottom

docs(triggers): add consideration about invocationType for the behavior of trigger failures #26450

Merged
merged 3 commits into from
Jul 20, 2023
Merged

docs(triggers): add consideration about invocationType for the behavior of trigger failures #26450

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
6fe7219
docs(trigger): Add consideration about invocationType for the behavio…
tam0ri Jul 20, 2023
653a2ce
Update packages/aws-cdk-lib/triggers/README.md
kaizencc Jul 20, 2023
e334c32
Merge branch 'main' into docs/trigger-failures
mergify[bot] Jul 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions packages/aws-cdk-lib/triggers/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,9 @@ deployment will fail, as if a resource failed to provision. This makes it easy
to implement "self tests" via triggers by simply making a set of assertions on
some provisioned infrastructure.

Note that this behavior is only applied when invocationType is `REQUEST_RESPONSE`. When invocationType is `EVENT`, Lambda function is invoked asynchronously.
In that case, if Lambda function is invoked successfully, the trigger will success regardless of the result for the function execution.

## Order of Execution

By default, a trigger will be executed by CloudFormation after the associated
Expand Down