project new subcommand waits for environment to be ready

[brokad]

Currently, running cargo shuttle project new returns immediately with a prompt stating the project is creating.

However, the environment is not ready to be deployed to until cargo shuttle project status returns ready. Most times this is not a big deal, but under high load, environment creation can take a minute or so, which can be unexpectedly long and create a bad experience as users don't know when their environment is finally ready.

Maybe it'd be better to hold exiting from project new until the project is ready, continuously updating the prompt with the latest state, and including a spinner to show there is work in progress. This also requires covering the entire state machine of environments.

If users exit early from the prompt, they should be able to go back into the "blocking, continuously updating state" through project status --wait, which should be equivalent.

[chesedo]

Thanks for this @brokad. The prefered solution for this should use websockets rather than a polling model (if possible).

I'm wondering if project status --follow won't be more idiomatic?

[brokad]

I'm wondering if project status --follow won't be more idiomatic?

Sure, I'm fine either way. Let's go with --follow.

[guerinoni]

I will try to implement it :)