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
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:
Silk release highlights:
Regards, CloudFoundry Networking Program
|
|
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?
|
|
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,
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:
|
|
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:
|
|
Re: The V7 CF CLI is now GA!
Chip Childers <cchilders@...>
On Mon, Jun 29, 2020 3:49 PM, Eric Malm emalm@... wrote:
|
|
Re: The V7 CF CLI is now GA!
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:
|
|
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:
|
|
Re: The V7 CF CLI is now GA!
Shannon Coen <scoen@...>
It's been a long road. Congratulations on getting to GA!
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:
|
|
Re: The V7 CF CLI is now GA!
Krannich, Bernd
Congrats to everybody involved!
Regards, Bernd
From: <cf-dev@...> on behalf of Dieu Cao <dieuc@...>
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:
--
|
|
Re: The V7 CF CLI is now GA!
Dieu Cao
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:
|
|
Re: The V7 CF CLI is now GA!
Dr Nic Williams <drnicwilliams@...>
Congrats to the team past and present! Nic
On Sat, 27 Jun 2020 at 8:42 am, Josh Collins <collinsjo@...> wrote:
--
|
|
The V7 CF CLI is now GA!
Josh Collins
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
|
|