-
Notifications
You must be signed in to change notification settings - Fork 2
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
chore: emit Docker and Shell logging to ProgressListener #221
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.
Please describe what this PR is addressing and how its solving it. If there are follow-up PRs, describe in a bit more detail how they will address it.
Please describe how you've verified the changes.
BTW, if it doesn't close the issue, e.g. because a second PR is needed, you cannot put that in like that. |
Signed-off-by: github-actions <[email protected]>
Related to #196
There is still a quiet flag however I will do that in another pr.
This change adds a new
GlobalOutputHandler
which as the name implies, is a global object which will send messages to the progress listener. If invoked from the CLI, the CLI first configures the progress as aConsoleProgress()
listener which prints to stderr by default. If invoked fromAssetPublishing
(the class which we programmatically interact with from the aws-cdk), then the globalOutputHandler will instead push the messages to the progress listener defined in that class.