You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow specifying arbitrary handlers which execute as part of the deployment process and hook them into various events such as before/after a resource or before/after stack deployments.
See #75 for a discussion
Then, use these for e.g. integration test assertions (#31)
Progress
Tracking Issue Created
RFC PR Created
Core Team Member Assigned
Initial Approval / Final Comment Period
Ready For Implementation
implementation issue 1
Resolved
The text was updated successfully, but these errors were encountered:
I've been digging through the source and the docs for a while now and it appears there are no events output by the app, a stack, or constructs. This makes it difficult or impossible to use the CDK to orchestrate environments that require non-cfn related tasks.
Ex:
I have a stack that generates a bucket
When the bucket is created I want to upload a file
Once that file is uploaded I want to trigger another stack
I can orchestrate this with a pipeline - which is what I'll do. But I'd like to be able to manage this locally as part of a package where a single cli command can kick this off. I'm sure there other use cases for events as well.
What I'd like to see:
Events added to a stack that are emmitted on state change:
var Stack = new CustomStack(app, 'CustomStack');
Stack.on('change', evt => {
if (evt.State == States.CREATE_COMPLETE) {
// do my thing;
}
})
I also think individual resources could use these events.
Description
Allow specifying arbitrary handlers which execute as part of the deployment process and hook them into various events such as before/after a resource or before/after stack deployments.
See #75 for a discussion
Then, use these for e.g. integration test assertions (#31)
Progress
The text was updated successfully, but these errors were encountered: