Krannich, Bernd <bernd.krannich@...>
toggle quoted messageShow quoted text
Hi Abby, Zach,
I don’t think we have looked into v3 commands in too much detail. Please forgive my ignorance in this topic, are the v3 commands already considered a stable API so that I could check if people can replace their existing
“--no-start” scenarios with it?
> this implies to me that these workflows are for new apps and not for updating existing ones.
IIRC, some of those workflows are done as part of blue-/green-updates. I am not sure that people would completely delete their currently inactive app completely, or if they would just keep updating the inactive app and
then switch over to it.
Thanks in advance,
From: <cf-dev@...> on behalf of Zach Robinson <zrobinson@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Thursday, 28. June 2018 at 01:58
To: "cf-dev@..." <cf-dev@...>
Subject: Re: [cf-dev] CF CLI: how do you use `no-start` with `cf push`
thanks to all that have replied.
i'd like to ask a clarifying question. it sounds like most of these use-cases are "set up some environment for the app". this implies to me that these workflows are for new apps and not for updating existing ones. does that sound right?
are their use-cases for "no-start" when updating an app?
On Wed, Jun 27, 2018 at 4:30 PM Abby Chau <achau@...
Hey Bernd and Julian,
Many thanks for your responses.
Wondering if you folks have tried using the `v3-create-app`
command as Mike has pointed out (and Zach elsewhere). The command is basically the equivalent of `cf push test --no-start` in that it creates an app, leaves it in a `stopped` state, and users can then apply configurations, bind services, set-groups, enable
ssh, etc. This command appears to be a workaround for your use cases, but please let us know if that's incorrect.
On Wed, Jun 27, 2018 at 3:04 PM, Hjortshoj, Julian <Julian.Hjortshoj@...> wrote:
+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.
Thank you very much for reaching out. Indeed, we are frequent users of the `no-start`
flag. A couple of use cases:
After a `cf ssh-enable APP_NAME`, you’ll need to restart your app to be able to SSH in. To prevent starting the app twice in that process, people do a `cf push --no-start` and then
an explicit `cf start APP_NAME` afterwards.
The same applies for changes of security groups which also require an app restart.
Lastly, and maybe most importantly, people use `no-start` for pushing an app to which they want to bind services. They push the app with “no-start”, “cf create-service” their services,
“cf bind-service” them to the app, and only then start the app.
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
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.
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@...>
Reply-To: "cf-dev@..." <cf-dev@...>
Date: Wednesday, 27. June 2018 at 18:18
To: "Discussions about Cloud Foundry projects and the system overall." <cf-dev@...>
Subject: [cf-dev] CF CLI: how do you use `no-start` with `cf push`
The CF CLI is soliciting feedback on how you use the `no-start` flag:
what are your specific use cases?
if the flag was no longer available, how might that affect you? (Would you strongly object to such a change, and why?) would you have a sensible workaround?
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.