Open andreineculau opened 6 years ago
Marking as feature request. Seems reasonable to me. I think this could apply to all wait
commands.
This would be a great feature to have! It seems necessary when running ci/cd systems.
It would even be better if the CloudFormation events would be printed to stdout. I would then see the progress of the stack in my CI/CD logs.
@hoegertn true that, but the list of events can be really long (I'm saying that with Travis in mind, where you have a limit of how much logging you can do, which is 4MB if memory holds).
What we have done is print only relevant FAILED/ROLLBACK events if the stack provisioning fails https://github.com/tobiipro/support-firecloud/blob/master/bin/aws-cloudformation-cu-stack#L209-L216
I think a parameter like --tail
would be great.
I also wanted wanted something like a log tail for cfn deployments in pipeline and made a small bash wrapper to do this: https://tech.aapjeisbaas.nl/display-aws-cloudformation-logs-in-pipelines.html
A --tail or --follow would be awesome, if there is enough interest I would love help out by creating this in a fork.
Several CI/CD environment e.g. Travis check for hanged executions based on stdout output, or the lack of it actually. Travis in particular has a way to extend the timeout, but that is a workaround, not a solution.
Deploying an API Gateway or a CloudFront instance can take a really long time, and
aws cloudformation wait
does not output anything at all.Please consider changing the current behaviour, or add a flag e.g. to reach status CREATE_COMPLETE..." on a new line. Something.
--progress
that would print something to stdout every 30s=poll. A dot. A "Waiting for change-set