Open rajatjindal opened 1 year ago
I definitely see the value for sending some sort of signal to the user that the app readiness check failed. A non-zero exit code is one way, an error message another. The former would probably be the friendliest to automation.
We already have a message if the app doesn't come ready. Some nastiness with exit codes (from a previous look at an unrelated issue):
Err(...)
from main
which always prints "Error: ..." _even if it's really only a heads upstd::process::Termination
, and this could have knock-on impacts to other parts of the codebase (because we return the same type from all the commands), so might turn out to be more work than expectedThese are not a blocker to doing an exit code, but just for awareness.
it seems there is a bug right now on trying to update app on Fermyon Cloud. I am adding a test for it and it also seems like
spin cloud deploy
would exit with code0
even if readiness check timeouts.what do you think about adding a flag to
spin cloud deploy
, which will make the spin command exit with error code if readiness is not established. it will be useful in CI/CD scenarios as well.