`rbt cloud logs --follow` disconnects when a new revision is `rbt cloud up`ped

[rjhuijsman]

What is the limitation?

A developer running...

rbt cloud logs --follow

... while (in a different terminal) somebody runs rbt cloud up to deploy a new revision of the application, will see the following error:

... connection interrupted, please try again

They will need to re-run rbt cloud logs --follow to continue following the logs.

This is a bug in the Reboot Cloud, which will need to get fixed.

How do I know if I've hit this limitation?

If you see the following error on your terminal...

... connection interrupted, please try again

... while you or a colleague were updating the application, you've hit this issue.

What do I do if I've hit this limitation?

1. Send feedback!

Please comment below, and share your use-case! We prioritize work based on user feedback, so letting us know that this limitation is affecting you, and why, helps us get the most important issues dealt with first!

2. Consider solutions or workarounds

Re-run rbt cloud logs --follow

Re-running rbt cloud logs --follow will continue following the logs. Note that to avoid missing log lines, you may want to consider passing the following flags:

• --revisions=">=$revision_you_were_watching" to get logs for both the new revision and the one being watched before.
• --last=$number_of_lines_you_may_have_missed to make sure the logs stream is picked up where it left off.