I didn't say the idea is entirely without merit, but I do think that this should be evaluated on a per case basis, rather than the silver bullet being sold in the description.
Your example is also questionable:
> deploy-stack --wait-for-relations
Please show this being useful in a non-error-prone way. The relation being established for Ensemble doesn't say much about it being ready for the underlying service, and the next action you attempt would have to wait on the _actual_ service to be ready.
So, again, I'm understand the conceptual problem, and I'm happy to work with you guys to improve the situation, but let's try to provide tools that will enable the user to do things reliably.
I didn't say the idea is entirely without merit, but I do think that this should be evaluated on a per case basis, rather than the silver bullet being sold in the description.
Your example is also questionable:
> deploy-stack --wait- for-relations
Please show this being useful in a non-error-prone way. The relation being established for Ensemble doesn't say much about it being ready for the underlying service, and the next action you attempt would have to wait on the _actual_ service to be ready.
So, again, I'm understand the conceptual problem, and I'm happy to work with you guys to improve the situation, but let's try to provide tools that will enable the user to do things reliably.