I use no-start because ‘cf push’ doesn’t have flags to set env vars/service bindings. If the response to that is “use manifest.yml” then perhaps get rid off all the push flags and force ppl

Hi, To walk down memory lane a bit, the varz endpoints were replaced with the firehose more than two years ago. The relevant threads are - https://lists.cloudfoundry.org/g/cf-dev/topic/6333080#3843 -

We have not tried the v3 api, but yes, that sounds correct to me, and v3-create-app seems like a reasonable substitute. From: cf-dev@... [cf-dev@...] on behalf of Zach Robinson [zrobinson@...] Sent:

Hey Bernd, Zach can speak more to this but, I believe, the CC v3 API has been stable for some time, with v3.27. The v3 prefixed CF CLI commands are relatively lesser known so apologies if it's been

Hi, +1 on chips idea. ;-) v3-foo was fun but we should get rid of that syntax. Greetings Christian -- E-Mail: cbrinker@... evoila GmbH Weberstraße 21 55130 Mainz Germany Geschäftsführer: Johannes

My 2 cents here, FWIW... the v3-foo$ syntax feels like it should be only temporary and should eventually be merged back into the more standard commands / feature flag combos.-- Chip Childers CTO,

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

We have multiple foundries in our org and occasionally we would want to push an app in the stopped state to a pool for DR purposes (active/active across foundries is always desirable but simply not

Hi Team, We would need clarification regarding custom roles on Cloud foundry. Our use case is as follows: Relevant permissions: deploy applications (re)start/stop applications access application

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

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

+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

Hi Abby, 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

Hi Lee, Have you seen the new variable substitution feature for manifests? It might really help your use-case. https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html#multi-manifests -Zach

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

Hi, We use it when setting env vars that we don't want to commit. Or when committing then would harm the reuse of our code by others. E.g. https://docs.cloud.service.gov.uk/#metrics Thanks Lee

Hi cf-dev, i am trying to bootstrap UAA 4.6.1 with an admin user password from the environment. i tried providing the entire scim.users array item and just the password in the pipe-delimited string

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

Hello all, Pivotal is nominating Josh Collins for the Release Integration Project Lead in the Application Runtime PMC. He is currently serving as Interim Project Lead for the Release Integration

Hi, Dieu, David, and teams, Let me personally (and on behalf of IBM’s CF team) thank David Sabeti for an outstanding job transitioning us all to cf-deployment. In the process, also making CF