Re: CF CLI: how do you use `no-start` with `cf push`

Zach Robinson

Hi Lee,

Have you seen the new variable substitution feature for manifests?  It might really help your use-case.


On Wed, Jun 27, 2018 at 10:09 AM Mike Youngstrom <youngm@...> wrote:
We mostly use it to do things to an application before starting it that cannot be done in a manifest.  For example, setting computed environment variables, or binding services that need service-parameters.  I think "--no-start" can be removed and we could use v3-create-app instead.


On Wed, Jun 27, 2018 at 10:18 AM Abby Chau <achau@...> wrote:
Hi everyone,

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.


Abby Chau
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.

Join { to automatically receive all group messages.