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
When working with the new @aws-cdk/toolkit-lib and implementing a custom ioHost I'd like to have all the logs emitted by CDK included in the notifiy callback.
Right now this is not the case, and some logs like the one emitted by the esbuild bundling process are not included.
Use Case
When using the new toolkit customers can control all the notifications and apply complex filtering/workflows on them. Right now the logs emitted by the bundling are excluded from these notifications and end up directly to stdout.
Proposed Solution
No response
Other Information
No response
Acknowledgements
I may be able to implement this feature request
This feature might incur a breaking change
CDK version used
2.1000.2
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered:
Describe the feature
When working with the new @aws-cdk/toolkit-lib and implementing a custom
ioHost
I'd like to have all the logs emitted by CDK included in thenotifiy
callback.Right now this is not the case, and some logs like the one emitted by the
esbuild
bundling process are not included.Use Case
When using the new toolkit customers can control all the notifications and apply complex filtering/workflows on them. Right now the logs emitted by the bundling are excluded from these notifications and end up directly to stdout.
Proposed Solution
No response
Other Information
No response
Acknowledgements
CDK version used
2.1000.2
Environment details (OS name and version, etc.)
N/A
The text was updated successfully, but these errors were encountered: