Re: Propose removing --no-start from cf push in CLI v7


Norm Abramovitz
 

Hi

It seems to me that you are making the developer experience more painful with your new interface   I wondering why you did not consider using parameters to cf push instead.   The first parameter would be a stop after parameter to stop after a phase.   

--stop-after build|droplet|staging|start

If you want to start at a particular phase versus starting with a build, then have a parameter starting at a phase.

--start-at build|droplet|staging|start

Most developers would still use cf push as it is now and only those people that need the new features will use them.  Also, you maintain the readability of the cli interface.

Now the no-start parameter can be maintained for backward compatibility.



On Thu, Oct 4, 2018 at 1:29 PM Zach Robinson <zrobinson@...> wrote:
Hey all,

We asked for some feedback regarding the use of the --no-start flag some time ago. As a result, we're proposing a change to push in the upcoming CLI v7.  In the linked doc we've described what the change is and why we want to make it.  We'd love to hear any feedback in comments on the doc.

https://docs.google.com/document/d/1OPJSUYXMQMtzZmVdnvwI4NiXE0xp4tuLxO3fhhXtGwI/edit?usp=sharing
Thanks,
Zach Robinson CAPI Project Lead and Abby Chau CLI Project Lead



--
Norman Abramovitz
Technical Director
Stark & Wayne, LLC



Join cf-dev@lists.cloudfoundry.org to automatically receive all group messages.