Hi, all, Please welcome Bo Yang (on cc:) of IBM as PM for CF App AutoScaler Extensions project [0]. You can keep up with the project’s monthly drumbeat as well as other CF Extensions updates here

Dear Jesse, did anything come out of this proposal? Did you end up picking up this track of work? Warm regards Marco From: <cf-dev@...> on behalf of Marco Voelz <marco.voelz@...> Reply-To:

Hi Josh, This is great news, thanks for sharing! So essentially, cf-deployment at some point in time will run containerized processes, even on “plain VMs”, excellent. This coincides

Hey Y'all, Cf-deployment 3.0 is around the corner. We're going to go 3.0 in 2-3 weeks. We released cf-deployment 2.0 on June 18th and included 'breaking' changes. Breaking changes in the context of

Hey Y'all, You may know this already, but I wanted to send out a broad communication to make sure you're in the know and to build a shared understanding about the process for migrating to BPM going

Hi all, We would like to propose the CF Containerization effort for incubation in the BOSH PMC. The full proposal can be found

Hi all, Thank you to everyone who gave us feedback on changing the `cf app` display summary information. We really appreciate your input. We've taken your feedback into consideration and have

Hello All, Usha Ramachandran, the Project Lead for the CF Networking team within the Application Runtime PMC, is rotating into a role internal to Pivotal. We thank her for her time serving as the CF

All you CF contributors and community folks out there, please take a quick 2 minutes and compete this survey, if you would! This will help us get a sense of the makeup of the Cloud Foundry Community,

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