1. cf-dev@lists.cloudfoundry.org
  2. Messages
   Date   
Re: Office Hours: CF on K8s Networking

Dieu Cao
 

Awesome! Very excited that there'll be this new forum where folks can get engaged.

-Dieu

From: cf-dev@... <cf-dev@...> on behalf of Shannon Coen via lists.cloudfoundry.org <scoen=vmware.com@...>
Sent: Tuesday, July 14, 2020 12:37 PM
To: cf-dev@... <cf-dev@...>
Subject: [cf-dev] Office Hours: CF on K8s Networking
 
Hello CFF friends,

The CF on K8s Networking team will be hosting OSS office hours bi-weekly beginning next Wednesday, July 22. We've added the event to the CFF community calendar: https://www.cloudfoundry.org/community-calendar/.

We're working toward delivering all the same outcomes within the problem domains of traffic management and security achieved in CF for VMs, for all data paths (ingress, egress, and app-to-app), plus those that have been long requested and not yet realized. We welcome your questions, comments, collaboration, and contribution!

Best,

Shannon Coen (He/Him)
Manager, Product Management
scoen@...
875 Howard Street 5th Floor, San Francisco CA 94103
Mobile: +1.415.640.0272


Office Hours: CF on K8s Networking

Shannon Coen
 

Hello CFF friends,

The CF on K8s Networking team will be hosting OSS office hours bi-weekly beginning next Wednesday, July 22. We've added the event to the CFF community calendar: https://www.cloudfoundry.org/community-calendar/.

We're working toward delivering all the same outcomes within the problem domains of traffic management and security achieved in CF for VMs, for all data paths (ingress, egress, and app-to-app), plus those that have been long requested and not yet realized. We welcome your questions, comments, collaboration, and contribution!

Best,

Shannon Coen (He/Him)
Manager, Product Management
scoen@...
875 Howard Street 5th Floor, San Francisco CA 94103
Mobile: +1.415.640.0272


Re: CATS Migration to support CF CLI V7

Eric Promislow
 

Hello,

The PR is at https://github.com/cloudfoundry/cf-acceptance-tests/pull/423

If anyone has any concerns (or comments) on the PR, we'd appreciate if you could add them by EOD Thursday July 16.
We hope to merge it and get a new V7-based release cut by the end of the week.

Cheers,
Eric Promislow and Dave Walter, Release Integration Team
Topics? CAB call: Wednesday, July 15th @ 8AM PT / 11AM ET / 4PM CET

Troy Topnik
 

Tomorrow's meeting currently has just the regular community updates from the PMC leads and community Q&A, so it might be a bit short.

If you have something you would like to present or know of something interesting we should get on the agenda, please get in touch with me via email or Slack and we'll try to make it happen. :)

Here's the agenda document:

https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit#

And the chat room: slack.cloudfoundry.org - join the #cab channel

Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/757994996 

Or iPhone one-tap :
    US: +16468769923,,757994996# or +16699006833,,757994996#
Or Telephone: Dial(for higher quality, dial a number based on your current location):
    US: +1 646 876 9923 or +1 669 900 6833 or +1 408 638 0968

Meeting ID: 757 994 996

International numbers available: https://zoom.us/zoomconference?m=BbM_MZowkH08pdKycQk10at13V5cLneM


TT

--
Troy Topnik
Senior Product Manager, 
SUSE Cloud Application Platform 
troy.topnik@...
 
CATS Migration to support CF CLI V7

Saikiran Yerram
 

Hello community friends,

With the recent CF CLI v7 release, we are migrating CATS to CF CLI v7 and also dropping support for CLI V6 in CATS. 

For contributing teams - You will have to update your pipelines to use a soon-to-be-released version of cf-deployment-concourse-task to run CATS with CLI v7. We will notify you when we ship CATS and cf-deployment-concourse-task releases. (If you're running CATS master, then your pipelines will break until you switch to the new concourse task. We recommend you pin to the last CATS version to avoid the disruption).

For Operators: Unless you're running CATS, it should not impact your workflows. We are updating smoke tests to be compatible with CLI v6 and v7. We will publish that release soon.

If you have any questions, please feel free to reach out to us in #cf-deployment or #cf-for-k8s slack channel.
IMPORTANT NOTICE: [staticfile-buildpack] End of Support for NGINX versions 1.17.x after 2020-08-07

Kashyap Vedurmudi <kvedurmudi@...>
 

The first release of the Staticfile buildpack after 2020-08-07 will no longer include NGINX versions 1.17.x. These NGINX versions will no longer be supported upstream[1]. Please migrate your static content apps to supported versions of NGINX before that time.


Note: As 1.17.x is the current default version of NGINX in the buildpack, the default NGINX version will be updated to 1.19.x as a part of this removal. If you’d like to use a different NGINX version, please configure your application to select that version[2].


As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[3].


[1] - https://nginx.org/en/download.html

[2] - https://docs.cloudfoundry.org/buildpacks/nginx/index.html

[3] - https://cloudfoundry.slack.com/archives/C02HWMDUQ


Thanks,

Kashyap Vedurmudi, Buildpacks PM
IMPORTANT NOTICE: [nginx-buildpack] End of Support for NGINX versions 1.17.x after 2020-08-07

Kashyap Vedurmudi <kvedurmudi@...>
 

The first release of the NGINX buildpack after 2020-08-07 will no longer include NGINX versions 1.17.x. These NGINX versions will no longer be supported upstream[1]. Please migrate your NGINX apps to supported versions of NGINX before that time.


Note: As 1.17.x is the current default version of NGINX in the buildpack, the default NGINX version will be updated to 1.19.x as a part of this removal. If you’d like to use a different NGINX version, please configure your application to select that version[2].


As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[3].


[1] - https://nginx.org/en/download.html

[2] - https://docs.cloudfoundry.org/buildpacks/nginx/index.html

[3] - https://cloudfoundry.slack.com/archives/C02HWMDUQ


Thanks,

Kashyap Vedurmudi, Buildpacks PM
IMPORTANT NOTICE: [php-buildpack] End of Support for NGINX versions 1.17.x after 2020-08-07

Kashyap Vedurmudi <kvedurmudi@...>
 

The first release of the PHP buildpack after 2020-08-07 will no longer include NGINX versions 1.17.x. These NGINX versions will no longer be supported upstream[1]. Please migrate your PHP apps to supported versions of NGINX before that time.


Note: As 1.17.x is the current default version of NGINX in the buildpack, the default NGINX version will be updated to 1.19.x as a part of this removal. If you’d like to use a different NGINX version, please configure your application to select that version[2].


As always, the buildpacks team is happy to answer questions you may have about this deprecation in the #buildpacks Slack channel[3].


[1] - https://nginx.org/en/download.html

[2] - https://docs.cloudfoundry.org/buildpacks/nginx/index.html

[3] - https://cloudfoundry.slack.com/archives/C02HWMDUQ


Thanks,

Kashyap Vedurmudi, Buildpacks PM
Routing release 0.202.0

Josh Russett
 

Hi cf-dev!

 

Routing release 0.202.0 is now available.

 

Release Highlights

  • Platform operators observe the following:
    • `X-Cf-RouterError` Response headers in application access logs
    • Gorouter logs messages when the gorouter fails to find any endpoints
    • Gorouter's log messages for retry attempts are consistent in form
  • Clarify `backend-endpoint-failed` errors in Gorouter logs by logging cause `x509: certificate has expired or is not yet valid`
  • Clarify, in the gorouter job spec,
    • that `extra_headers_to_log` property (the "HTTP headers to log") only applies to Request headers
    • how `request_timeout_in_seconds` applies to connections between the router and backend

 

 

Regards,

CloudFoundry Networking Program

 
CF-Networking and Silk release 2.31.0

Josh Russett
 

Hi cf-dev!

 

New CF-Networking and Silk releases were cut.

 

CF-Networking release highlights:

  • C2C DNS Lookups are not case-sensitive (See Issue #76)
  • Service Discovery Controller's open_files ulimit increased to 65535 (See PR #80)
  • Introduce a delay between on retries between the bosh-dns-adapter and the Service Discovery Controller (See PR #81)
  • Built with go1.14.4
  • Tested with silk-release v2.31.0

 

Silk release highlights:

  • None!
  • Tested with cf-networking-release v2.31.0

 

Regards,

CloudFoundry Networking Program
While creating user ,emails set primary is set to true while sending request but after creating in the response the primary is set with false #uaa #cf

shilpa kulkarni
 

Hi All,

I tried to create user and I passed the value true for emails primary but as response it is set primary value as false. Why the primary value does not set with true? can any one please tell about this?
Why UAA is considering username field instead of email field from uaa users table for sending reset password link ? #cf #uaa

shilpa kulkarni
 

Hi All,

while creating user I have not given email address as username  but the user is having email address in email field. when i try to check the forgot password(reset password) functionality it is not sending password reset link to that email address. So again I tried by changing the username to the proper email address  and given that email address (which is username) for sending reset password link  then the password reset link has been sent to the email address which is saved as username filed. Why UAA is considering username field instead of email field from uaa users table? Can anyone please answer to this?
While creating user ,emails set primary is set to true while sending request but after creating in the response the primary is set with false

shilpa kulkarni
 

Hi All,

I tried to create user and I passed the value true for emails primary but as response it is set primary value as false. Why the primary value does not set with true? can any one please tell about this?
cf-for-k8s Secret proposal

Saikiran Yerram
 

Hello CF community, here is the proposal from the release-integration and the credhub team about the generation and consumption of Secret passwords in cf-for-k8s. 

The proposal recommends,
  1. How contributing projects should consume sensitive information like passwords using a standardized way 
  2. The contract between the cf-for-k8s project and components 
  3. Use of QuarksSecret to generate passwords. 

You can review and comment on this doc. https://docs.google.com/document/d/1VKMVaBcIUjro_y38KwMskvqoqSXljqVcLA_CVPTHbXU/edit?usp=sharing 


Thank you!!
Re: Proposal to Rename the Primary Branch on all Cloud Foundry repos

Dieu Cao
 

Hey all,

I really appreciate the support on this thread for moving away from `master` as the default branch.
It seems `main` is a popular choice as an alternative default and some projects are moving to adopt that.
It sounds like each PMC can take that as a suggestion, in addition to the other alternatives suggested on this thread, and figure out what they would like to standardize on within each PMC.
I'd like to recommend, as a way to move this forward, that each of the PMCs work towards guidance on defaults within their PMCs and each PMC work towards achieving those changes.

Thanks all,
-Dieu

From: cf-dev@... <cf-dev@...> on behalf of Amelia Downs via lists.cloudfoundry.org <adowns=vmware.com@...>
Sent: Tuesday, June 30, 2020 8:44 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Hi all, 

I created an issue for routing-release for my team to do this work. 


Please feel free to use this as a template to make stories for your own teams/repos/components.

Best, 
Amelia
From: cf-dev@... <cf-dev@...> on behalf of Jesse Alford via lists.cloudfoundry.org <jalford=vmware.com@...>
Sent: Friday, June 26, 2020 10:16 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Changing branches breaks a lot of tooling, docs, and expectations.

If you're going to do it - which to be clear I think we should in this case -
it is better to move to what you'd prefer,
rather than make multiple such breaks.

I agree that `main` is a fine default and matches what Github will be migrating to.
If "default branch, plus whatever expectations you might bring with you about such a branch"
is what you want to communicate with your branch name, switch to `main`.

If "the place that active development should be pushed/merged to" and,
optionally,
"the place that deliberately released code should be pulled from"
is what you want to communicate, maybe use that pattern.

If you want to say something else with your branch names,
this is an opportunity to communicate.

Anyway. I support changes away from `master`,
but think we don't need to coordinate further on the matter.
From: cf-dev@... <cf-dev@...> on behalf of Josh Collins <collinsjo@...>
Sent: Friday, June 26, 2020 9:58 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
I support this change.

Josh Collins - CF CLI PM
From: cf-dev@... <cf-dev@...> on behalf of Lee Porte via lists.cloudfoundry.org <lee.porte=digital.cabinet-office.gov.uk@...>
Sent: Wednesday, June 24, 2020 12:22 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Hi all,

I am also in support of this change after enquiring on slack.

Cheers

L

On Tue, 23 Jun 2020 at 23:06, Dieu Cao <dieuc@...> wrote:
Hey all,
I would like to propose that the cloud foundry projects rename the primary branch on all https://github.com/cloudfoundry and https://github.com/cloudfoundry-incubator repos to “main” as part of Cloud Foundry’s commitment to an inclusive and welcoming community.
I believe some project teams independently have plans to invest in making this change.
Thoughts? Feedback?
-Dieu



--
Lee Porte
Reliability Engineer 
GOV.UK PaaS Team
‪020 3920 6036‬
07785 449292
Re: Proposal to Rename the Primary Branch on all Cloud Foundry repos

Amelia Downs
 

Hi all, 

I created an issue for routing-release for my team to do this work. 


Please feel free to use this as a template to make stories for your own teams/repos/components.

Best, 
Amelia

From: cf-dev@... <cf-dev@...> on behalf of Jesse Alford via lists.cloudfoundry.org <jalford=vmware.com@...>
Sent: Friday, June 26, 2020 10:16 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Changing branches breaks a lot of tooling, docs, and expectations.

If you're going to do it - which to be clear I think we should in this case -
it is better to move to what you'd prefer,
rather than make multiple such breaks.

I agree that `main` is a fine default and matches what Github will be migrating to.
If "default branch, plus whatever expectations you might bring with you about such a branch"
is what you want to communicate with your branch name, switch to `main`.

If "the place that active development should be pushed/merged to" and,
optionally,
"the place that deliberately released code should be pulled from"
is what you want to communicate, maybe use that pattern.

If you want to say something else with your branch names,
this is an opportunity to communicate.

Anyway. I support changes away from `master`,
but think we don't need to coordinate further on the matter.
From: cf-dev@... <cf-dev@...> on behalf of Josh Collins <collinsjo@...>
Sent: Friday, June 26, 2020 9:58 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
I support this change.

Josh Collins - CF CLI PM
From: cf-dev@... <cf-dev@...> on behalf of Lee Porte via lists.cloudfoundry.org <lee.porte=digital.cabinet-office.gov.uk@...>
Sent: Wednesday, June 24, 2020 12:22 AM
To: Discussions about Cloud Foundry projects and the system overall. <cf-dev@...>
Subject: Re: [cf-dev] Proposal to Rename the Primary Branch on all Cloud Foundry repos
 
Hi all,

I am also in support of this change after enquiring on slack.

Cheers

L

On Tue, 23 Jun 2020 at 23:06, Dieu Cao <dieuc@...> wrote:
Hey all,
I would like to propose that the cloud foundry projects rename the primary branch on all https://github.com/cloudfoundry and https://github.com/cloudfoundry-incubator repos to “main” as part of Cloud Foundry’s commitment to an inclusive and welcoming community.
I believe some project teams independently have plans to invest in making this change.
Thoughts? Feedback?
-Dieu



--
Lee Porte
Reliability Engineer 
GOV.UK PaaS Team
‪020 3920 6036‬
07785 449292
Re: The V7 CF CLI is now GA!

Chip Childers <cchilders@...>
 

Late to pile on here, but congratulations to everyone that was involved in the v7 CPI and the CAPI v3 APIs... both recently with this big push AND historically. This has been a long time coming, and it's exciting to see the CLI hit this milestone!

-chip

Chip Childers
Executive Director
Cloud Foundry Foundation



On Mon, Jun 29, 2020 3:49 PM, Eric Malm emalm@... wrote:

Congratulations, Josh! Super excited to see the v7 CLI get its first GA release!

Best,
Eric
From: cf-dev@... <cf-dev@...> on behalf of Saikiran Yerram via lists.cloudfoundry.org <syerram=vmware.com@...>
Sent: Friday, June 26, 2020 6:14 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats Josh and the CLI team. It’s a huge milestone for CF.

— Sai
Product Manager - CloudFoundry and PAS Release
From: cf-dev@... <cf-dev@...> on behalf of Dieu Cao <dieuc@...>
Sent: Friday, June 26, 2020 5:10:48 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats! Huge milestone and awesome effort from everyone involved!

-Dieu
From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams via lists.cloudfoundry.org <drnicwilliams=gmail.com@...>
Sent: Friday, June 26, 2020 3:43 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats to the team past and present!

Nic

On Sat, 27 Jun 2020 at 8:42 am, Josh Collins <collinsjo@...> wrote:
Good morning, good afternoon, good evening & happy Friday to you all,

The cf CLI team GA'd the v7 CF CLI yesterday in the late afternoon. 
We're simultaneously excited, relieved, and exhausted by our efforts over the last couple months and we invite you to join us as we take (v)7 deep breaths to rightly mark this occasion.

Please see the release notes for details.

And as always, we really would love to hear from you so please feel free to respond to this email or find us in the Cloud Foundry Slack #cli channel any time.

Because this is kind of a big deal, some acknowledgements are in order...


We wouldn't be here without dedicated users and contributors; all your feedback, your issues, your pull requests and your valuable time taken to help us gain insight into what matters most. 

Your engagement has been invaluable. And we look forward to our continued work and collaboration in the future. Thank you!

And it took a great deal of work from people on the cf CLI, V3 Acceleration and Services API teams (as well as many others) to deliver the new CLI. 

Based on a review of Git commits, we've put together a list of folks we'd like to acknowledge (if a name is missing, please know we appreciate you in spirit).

Thank you all very much: Piyali Banerjee, Alexander Berezovsky, Alex Blease, George Blue, Seth Boyles, Connor Braa, Florian Braun, Winna Bridgewater, Andrew Brown, André Browne, Marcela Campo, Abby Chau, Renee Chu, Greg Cobb, Josh Collins, Emina Cosic, Andrew Crump, Brian Cunnie, Tim Downey, Derik Evangelista, Daniel Fein, Oleksii Fedorov, Weyman Fung, Anand Gaitonde, Jenna Goldstrich, Nick Guerette, Leah Hanson, Spencer Hawley, Michelle He, Chris Hendrix, Sannidhi Jalukar, Rob Jones, Mike Kenyon, Aarti Kriplani, Merric de Launey, Joao Lebre, Diego Lemos, Belinda Liu, Georgi Lozev, Will Martin, Felisia Martini, Niki Maslarski, Nikolay Maslarski, Andres Medina, Reid Mitchell, Mona Mohebbi, Magesh Murali Kumar, Will Murphy, Harsha Nandiwada, Supraja Narasimhan, Joseph Palermo, James Palmer, Will Pragnell, Eric Promislow, Zach Robinson, Luan Santos, Simon Seif, Chris Selzo, Alex Shan, Brendan Smith, Henry Stanley, Teal Stannard, Steve Taylor, Aditya Tripathi, Sebastian Vidrio, Thomas Viehman, Nicholas Webb, Sarah Weinstein, Eli Wrenn


Have a great weekend!
CF CLI and V3 Acceleration teams


--
Dr Nic Williams
Stark & Wayne LLC
+61 437 276 076
twitter @drnic
Re: The V7 CF CLI is now GA!

Eric Malm
 

Congratulations, Josh! Super excited to see the v7 CLI get its first GA release!

Best,
Eric

From: cf-dev@... <cf-dev@...> on behalf of Saikiran Yerram via lists.cloudfoundry.org <syerram=vmware.com@...>
Sent: Friday, June 26, 2020 6:14 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats Josh and the CLI team. It’s a huge milestone for CF.

— Sai
Product Manager - CloudFoundry and PAS Release
From: cf-dev@... <cf-dev@...> on behalf of Dieu Cao <dieuc@...>
Sent: Friday, June 26, 2020 5:10:48 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats! Huge milestone and awesome effort from everyone involved!

-Dieu
From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams via lists.cloudfoundry.org <drnicwilliams=gmail.com@...>
Sent: Friday, June 26, 2020 3:43 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats to the team past and present!

Nic

On Sat, 27 Jun 2020 at 8:42 am, Josh Collins <collinsjo@...> wrote:
Good morning, good afternoon, good evening & happy Friday to you all,

The cf CLI team GA'd the v7 CF CLI yesterday in the late afternoon. 
We're simultaneously excited, relieved, and exhausted by our efforts over the last couple months and we invite you to join us as we take (v)7 deep breaths to rightly mark this occasion.

Please see the release notes for details.

And as always, we really would love to hear from you so please feel free to respond to this email or find us in the Cloud Foundry Slack #cli channel any time.

Because this is kind of a big deal, some acknowledgements are in order...


We wouldn't be here without dedicated users and contributors; all your feedback, your issues, your pull requests and your valuable time taken to help us gain insight into what matters most. 

Your engagement has been invaluable. And we look forward to our continued work and collaboration in the future. Thank you!

And it took a great deal of work from people on the cf CLI, V3 Acceleration and Services API teams (as well as many others) to deliver the new CLI. 

Based on a review of Git commits, we've put together a list of folks we'd like to acknowledge (if a name is missing, please know we appreciate you in spirit).

Thank you all very much: Piyali Banerjee, Alexander Berezovsky, Alex Blease, George Blue, Seth Boyles, Connor Braa, Florian Braun, Winna Bridgewater, Andrew Brown, André Browne, Marcela Campo, Abby Chau, Renee Chu, Greg Cobb, Josh Collins, Emina Cosic, Andrew Crump, Brian Cunnie, Tim Downey, Derik Evangelista, Daniel Fein, Oleksii Fedorov, Weyman Fung, Anand Gaitonde, Jenna Goldstrich, Nick Guerette, Leah Hanson, Spencer Hawley, Michelle He, Chris Hendrix, Sannidhi Jalukar, Rob Jones, Mike Kenyon, Aarti Kriplani, Merric de Launey, Joao Lebre, Diego Lemos, Belinda Liu, Georgi Lozev, Will Martin, Felisia Martini, Niki Maslarski, Nikolay Maslarski, Andres Medina, Reid Mitchell, Mona Mohebbi, Magesh Murali Kumar, Will Murphy, Harsha Nandiwada, Supraja Narasimhan, Joseph Palermo, James Palmer, Will Pragnell, Eric Promislow, Zach Robinson, Luan Santos, Simon Seif, Chris Selzo, Alex Shan, Brendan Smith, Henry Stanley, Teal Stannard, Steve Taylor, Aditya Tripathi, Sebastian Vidrio, Thomas Viehman, Nicholas Webb, Sarah Weinstein, Eli Wrenn


Have a great weekend!
CF CLI and V3 Acceleration teams


--
Dr Nic Williams
Stark & Wayne LLC
+61 437 276 076
twitter @drnic
Re: The V7 CF CLI is now GA!

Saikiran Yerram <syerram@...>
 

Congrats Josh and the CLI team. It’s a huge milestone for CF.

— Sai
Product Manager - CloudFoundry and PAS Release

From: cf-dev@... <cf-dev@...> on behalf of Dieu Cao <dieuc@...>
Sent: Friday, June 26, 2020 5:10:48 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats! Huge milestone and awesome effort from everyone involved!

-Dieu
From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams via lists.cloudfoundry.org <drnicwilliams=gmail.com@...>
Sent: Friday, June 26, 2020 3:43 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats to the team past and present!

Nic

On Sat, 27 Jun 2020 at 8:42 am, Josh Collins <collinsjo@...> wrote:
Good morning, good afternoon, good evening & happy Friday to you all,

The cf CLI team GA'd the v7 CF CLI yesterday in the late afternoon. 
We're simultaneously excited, relieved, and exhausted by our efforts over the last couple months and we invite you to join us as we take (v)7 deep breaths to rightly mark this occasion.

Please see the release notes for details.

And as always, we really would love to hear from you so please feel free to respond to this email or find us in the Cloud Foundry Slack #cli channel any time.

Because this is kind of a big deal, some acknowledgements are in order...


We wouldn't be here without dedicated users and contributors; all your feedback, your issues, your pull requests and your valuable time taken to help us gain insight into what matters most. 

Your engagement has been invaluable. And we look forward to our continued work and collaboration in the future. Thank you!

And it took a great deal of work from people on the cf CLI, V3 Acceleration and Services API teams (as well as many others) to deliver the new CLI. 

Based on a review of Git commits, we've put together a list of folks we'd like to acknowledge (if a name is missing, please know we appreciate you in spirit).

Thank you all very much: Piyali Banerjee, Alexander Berezovsky, Alex Blease, George Blue, Seth Boyles, Connor Braa, Florian Braun, Winna Bridgewater, Andrew Brown, André Browne, Marcela Campo, Abby Chau, Renee Chu, Greg Cobb, Josh Collins, Emina Cosic, Andrew Crump, Brian Cunnie, Tim Downey, Derik Evangelista, Daniel Fein, Oleksii Fedorov, Weyman Fung, Anand Gaitonde, Jenna Goldstrich, Nick Guerette, Leah Hanson, Spencer Hawley, Michelle He, Chris Hendrix, Sannidhi Jalukar, Rob Jones, Mike Kenyon, Aarti Kriplani, Merric de Launey, Joao Lebre, Diego Lemos, Belinda Liu, Georgi Lozev, Will Martin, Felisia Martini, Niki Maslarski, Nikolay Maslarski, Andres Medina, Reid Mitchell, Mona Mohebbi, Magesh Murali Kumar, Will Murphy, Harsha Nandiwada, Supraja Narasimhan, Joseph Palermo, James Palmer, Will Pragnell, Eric Promislow, Zach Robinson, Luan Santos, Simon Seif, Chris Selzo, Alex Shan, Brendan Smith, Henry Stanley, Teal Stannard, Steve Taylor, Aditya Tripathi, Sebastian Vidrio, Thomas Viehman, Nicholas Webb, Sarah Weinstein, Eli Wrenn


Have a great weekend!
CF CLI and V3 Acceleration teams


--
Dr Nic Williams
Stark & Wayne LLC
+61 437 276 076
twitter @drnic
Re: The V7 CF CLI is now GA!

Shannon Coen <scoen@...>
 

It's been a long road. Congratulations on getting to GA!

Shannon Coen (He/Him)
Manager, Product Management
scoen@...
875 Howard Street 5th Floor, San Francisco CA 94103
Mobile: +1.415.640.0272


From: cf-dev@... <cf-dev@...> on behalf of Dr Nic Williams <drnicwilliams@...>
Sent: Friday, June 26, 2020 3:43 PM
To: cf-dev@... <cf-dev@...>
Subject: Re: [cf-dev] The V7 CF CLI is now GA!
 
Congrats to the team past and present!

Nic

On Sat, 27 Jun 2020 at 8:42 am, Josh Collins <collinsjo@...> wrote:
Good morning, good afternoon, good evening & happy Friday to you all,

The cf CLI team GA'd the v7 CF CLI yesterday in the late afternoon. 
We're simultaneously excited, relieved, and exhausted by our efforts over the last couple months and we invite you to join us as we take (v)7 deep breaths to rightly mark this occasion.

Please see the release notes for details.

And as always, we really would love to hear from you so please feel free to respond to this email or find us in the Cloud Foundry Slack #cli channel any time.

Because this is kind of a big deal, some acknowledgements are in order...


We wouldn't be here without dedicated users and contributors; all your feedback, your issues, your pull requests and your valuable time taken to help us gain insight into what matters most. 

Your engagement has been invaluable. And we look forward to our continued work and collaboration in the future. Thank you!

And it took a great deal of work from people on the cf CLI, V3 Acceleration and Services API teams (as well as many others) to deliver the new CLI. 

Based on a review of Git commits, we've put together a list of folks we'd like to acknowledge (if a name is missing, please know we appreciate you in spirit).

Thank you all very much: Piyali Banerjee, Alexander Berezovsky, Alex Blease, George Blue, Seth Boyles, Connor Braa, Florian Braun, Winna Bridgewater, Andrew Brown, André Browne, Marcela Campo, Abby Chau, Renee Chu, Greg Cobb, Josh Collins, Emina Cosic, Andrew Crump, Brian Cunnie, Tim Downey, Derik Evangelista, Daniel Fein, Oleksii Fedorov, Weyman Fung, Anand Gaitonde, Jenna Goldstrich, Nick Guerette, Leah Hanson, Spencer Hawley, Michelle He, Chris Hendrix, Sannidhi Jalukar, Rob Jones, Mike Kenyon, Aarti Kriplani, Merric de Launey, Joao Lebre, Diego Lemos, Belinda Liu, Georgi Lozev, Will Martin, Felisia Martini, Niki Maslarski, Nikolay Maslarski, Andres Medina, Reid Mitchell, Mona Mohebbi, Magesh Murali Kumar, Will Murphy, Harsha Nandiwada, Supraja Narasimhan, Joseph Palermo, James Palmer, Will Pragnell, Eric Promislow, Zach Robinson, Luan Santos, Simon Seif, Chris Selzo, Alex Shan, Brendan Smith, Henry Stanley, Teal Stannard, Steve Taylor, Aditya Tripathi, Sebastian Vidrio, Thomas Viehman, Nicholas Webb, Sarah Weinstein, Eli Wrenn


Have a great weekend!
CF CLI and V3 Acceleration teams


--
Dr Nic Williams
Stark & Wayne LLC
+61 437 276 076
twitter @drnic
341 - 360 of 9431