Full log of copilot activity

[jerometremblay]

When we run copilot, the interface is very dynamic and pretty to look at.
Is there a way to also generate a complete text-mode log instead of the dynamic view?

[Lou1415926]

@jerometremblay Thank you for the nice words!

Unfortunately not today : ( Are you looking to store the logs for future references?

[jerometremblay]

Yes, and also to more easily let a task run in the background and see what happened step by step. Otherwise, when I come back I just see "everthing rolled back" and i don't know exactly what worked and what did not.

[Lou1415926]

Gotcha. Thanks for sharing 👍🏼 !

Copilot should not have attempted to erase the stack events that the deployment ended with, which should contain information of what failed and why. Did you see something like ⬇️, or did you see only the last line "deploy service: stack xxx did not complete successfully", or was the deployment progress tracker you were left with too scrambled that it became unreadably?

To clarify, I still agree that having a text based output to certain log files can be a helpful addition. I am trying to identify whether or not it was because of a bug that you weren't able to see the failure reasons.

[jerometremblay]

Searched but couldn't find the exact example I had in mind for this. I did remember that it was as you showed in your screenshot. A bunch of resources were all in a rolled back state. It's just that since the execution order is not fixed in this view, i wasn't sure which one exactly failed and triggered the rollback.

Since then I fould the --no-rollback option that helps a lot for this particular case.

[jerometremblay]

Example of lost information

But after everything is done, i have this

So I don't know that the problem is caused by something in Route 53. (An extra CNAME in the zone so it cannot be deleted)

[Lou1415926]

Got it..! I think you are right - for delete commands, the progress are indeed erased after they are done:

copilot-cli/internal/pkg/deploy/cloudformation/cloudformation.go

Line 800 in 90b23b0

_, err = progress.EraseAndRender(w, progress.LineRenderer(log.Ssuccess(in.description), 0), nl)

. It's a good idea to preserve them for troubleshooting purposes 👍🏼