Re: CF CLI: how do you use `no-start` with `cf push`
Hjortshoj, Julian <Julian.Hjortshoj@...>
+1 to that last use case. In particular, if a service requires bind configuration, then it's not possible to put the binding in an app manifest (because manifests don't support service binding configuration) so it is very helpful to keep your app from starting until the service is bound.
Adding the ability to specify bind configuration in an application manifest might be a reasonable mitigation if --no-start were to disappear.
From: cf-dev@... [cf-dev@...] on behalf of Krannich, Bernd [bernd.krannich@...]
Sent: Wednesday, June 27, 2018 9:55 AM
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`
Thank you very much for reaching out. Indeed, we are frequent users of the `no-start` flag. A couple of use cases:
So, I guess in summary, for all operations changing the app environment, doing those changes with the app not yet started is a common use case for us.
SAP Cloud Platform
Dietmar-Hopp-Allee 16, 69190 Walldorf, Germany
Pflichtangaben/Mandatory Disclosure Statement: www.sap.com/impressum
Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank.
This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
<cf-dev@...> on behalf of Abby Chau <achau@...>
The CF CLI is soliciting feedback on how you use the `no-start` flag:
Please contact us on the #cli channel on Cloud Foundry Slack. Alternatively, respond directly to this email.
CF Product Manager, CF CLI
Note: The CF CLI team is currently working on updating the `cf v3-push` command to use the server side manifest work we've completed (with the Capi team), and to update the command such that it has as much feature parity with the current `cf-push` as possible. The eventual goal is to make the `cf push` command default to the enhanced v3-push command for users (on cc api 3.27 or higher). Since there is more granular control options in v3, `no-start` is a more nebulous flag.