|
cf CLI 6.47.2 released today
Abby Chau
Hi everyone, The cf CLI team released v6.47.2 today which includes a bump to Golang 1.12.12 to address Golang-related security concerns. Please reach out if you have any questions. Thanks. Best, Abby and the cf CLI team
|
||||||||||||
|
|
||||||||||||
|
Remove support for TLS 1.0 and 1.1 in the CF CLI
Steve Taylor
Hi CF CLI community, The minimum version of TLS supported by the current CF CLI is TLS 1.0. Does anyone object to us bumping the minimum version of TLS to 1.2 in a near-future minor release of the CLI? Regards, The CF CLI Team
|
||||||||||||
|
|
||||||||||||
|
CF CLI: Dropping Support for Legacy Operating Systems related to GoLang 1.13
#cf
Eric Promislow
Greetings CF CLI community, The current binary releases of the CF CLI are built using Go 1.12. We plan to start using Go 1.13 soon. The GoLang 1.12 release included the following warning: Go 1.12 is the last release that will run on macOS 10.10 Yosemite. Go 1.13 will require macOS 10.11 El Capitan or later. And the GoLang 1.13 release included the following warning: The Windows version specified by internally-linked Windows binaries is now Windows 7 rather than NT 4.0. As a result of these two announcements, we plan the following binary support matrix for an upcoming release of the CF CLI binaries built with Go 1.13:
Please reach out if you have any questions or concerns. Regards, The CF CLI team
|
||||||||||||
|
|
||||||||||||
|
Re: CF Application Runtime PMC: Loggregator Project Lead Call for Nominations
Eric Malm <emalm@...>
Hi, everyone, Pivotal is nominating Jesse Weaver for the Loggregator Project Lead in the Application Runtime PMC. Jesse is a product manager at Pivotal working on the Loggregator team, and previously was an engineer working on Cloud Foundry in Denver. His previous work includes full-stack engineering and design for web applications, and engineering and product design for open-source projects. Please send any other nominations directly to me or in reply to this message no later than 11:59 PM PDT on Monday, Nov 11, 2019. Thanks, Eric Malm
On Tue, Oct 29, 2019 at 11:05 AM Eric Malm <emalm@...> wrote:
|
||||||||||||
|
|
||||||||||||
|
CF Application Runtime PMC: Loggregator Project Lead Call for Nominations
Eric Malm <emalm@...>
Hi, everyone, Allen Duet, the lead for the Loggregator project within the Application Runtime PMC, is stepping down from the project, as he has recently left Pivotal. We thank him for his service. The Loggregator team, located in Denver, now has an opening for its project lead. Project leads must be nominated by a Cloud Foundry Foundation member. Please send nominations directly to me or in reply to this message no later than 11:59 PM PDT on Monday, Nov 11, 2019. Also, if you have any questions about the role or the nomination process, as described in the CFF governance documents (https://www.cloudfoundry.org/governance/cff_development_operations_policy/), please let me know. Thanks, Eric Malm, CF Application Runtime PMC Lead
|
||||||||||||
|
|
||||||||||||
|
Automating minor stemcell releases
Saikiran Yerram
TLDR We will now automatically release minor versions of CF Deployment for every new minor stemcell version bump. Why we are doing this CF users want to upgrade their foundation as soon as bosh stemcell versions are available in CF-deployment. However, the bosh stemcell bumps are packaged with unrelated changes and scheduled as part of regular release cycles. If there are any new stemcell updates (including CVE fixes), users will have to wait for the next release even if it might include other component updates. If any change results in a build failure at any stage in the pipeline, a stemcell update might be blocked until unrelated changes are fixed. Furthermore, a minor stemcell bump can be packaged with a major version cf-deployment release with component related breaking changes. This forces cf users to either perform a major upgrade just to get the latest stemcell version or run the risk of falling behind. Solution The Release Integration team will release a cf-deployment minor release with just one single change - minor stemcell bump - as soon as a new stemcell is available, so cf users can stay up to date with the latest stemcell (and not worry about other unrelated changes). Version 12.3.0 is one such example. 
|
||||||||||||
|
|
||||||||||||
|
Re: cf CLI 6.47.0 regression and Windows not released
Abby Chau
Hi everyone, cf CLI 6.47.1 now has support for Windows. In summary, cf CLI 6.47.1 supports all previous supported operating systems, and it fixes a regression for cf login. Thanks everyone for your patience, and let us know if you have any feedback. Best, Abby and the CLI and VAT
On Tue, Oct 22, 2019 at 12:22 PM Abby Chau <achau@...> wrote:
|
||||||||||||
|
|
||||||||||||
|
Re: What happened to Maven Central releases
#uaa
Dan Beneke
Hi Mike - The project's primary intent is to publish new releases on Github within cloudfoundry/uaa. I recognize that there was a time that they were being published to Maven, and that publish has been interrupted. Historically, the Maven artifacts were hosted by the Spring/Pivotal organization, meaning publish access was restricted to members of that org. There is UAA community intent to move the hosting location to a CFF (or other shared) site, so that contributing project members outside of Spring/Pivotal could be provided publish access to the new location. All of this is to say that Maven artifact publish may continue, but not until a new hosting location is identified. Dan
On Tue, Oct 22, 2019 at 5:47 AM Mike Roda <m2roda@...> wrote: Thanks but I need the jars, specifically the cloudfoundry-identity-server and cloudfoundry-identity-model projects.
|
||||||||||||
|
|
||||||||||||
|
Re: cf CLI 6.47.0 regression and Windows not released
Abby Chau
Hi everyone, A quick update: we are still working on Windows Support. In the meantime, the cf CLI eng team applied a temporary fix for the Windows issue: links for the latest Windows version temporarily redirects to use cf CLI 6.46.1 which is the last known working version. The Linux and OSX installers/binaries are still pointing at cf CLI 6.47.1, which fixes the aforementioned regression for login. Once we have the new Windows cert working, we will release Windows support which will be on par with cf CLI 6.47.1. Please reach out if you have any questions or concerns, thanks. Abby
On Mon, Oct 21, 2019 at 5:25 PM Abby Chau <achau@...> wrote:
|
||||||||||||
|
|
||||||||||||
|
Re: What happened to Maven Central releases
#uaa
Mike Roda
Thanks but I need the jars, specifically the cloudfoundry-identity-server and cloudfoundry-identity-model projects.
|
||||||||||||
|
|
||||||||||||
|
Re: cf CLI 6.47.0 regression and Windows not released
Abby Chau
Hi everyone, We released a patch today for this regression on OSX and Linux. We are currently still working on adding Windows support and hope to release again (this week - fingers-crossed) with Windows support. Please do not hesitate to get in touch if you have any questions. Thanks, Abby
On Thu, Oct 17, 2019 at 12:18 PM Abby Chau <achau@...> wrote:
|
||||||||||||
|
|
||||||||||||
|
Re: What happened to Maven Central releases
#uaa
Dr Nic Williams <drnicwilliams@...>
Before I learned that UAA wars went to Maven, I created a CI pipeline to create the .war files and store on github release. If it’s useful to you, they are at -- Nic
|
||||||||||||
|
|
||||||||||||
|
What happened to Maven Central releases
#uaa
Mike Roda
Hi,
Does anyone know why there are no new UAA releases being published to Maven Central after 4.30.0 ? Mike
|
||||||||||||
|
|
||||||||||||
|
New slack channel - services feedback for v3 / v7
Aditya Tripathi
Hello cf-dev! I represent the team that is building out services things for the v3 API and v7 CLI. We're trying an experiment to get fast feedback via slack for services related topics. If this sounds interesting, please consider joining the #services-feedback channel on the cloud foundry slack. Thank you! Kind regards, Aditya Tripathi
|
||||||||||||
|
|
||||||||||||
|
IMPORTANT NOTICE: [python-buildpack] End of support for Python versions 3.4.x after 2019-11-18
Elliott Shanks
The first release of the Python buildpack after November 18, 2019 will no longer include Python versions 3.4.x These Python versions will no longer be supported upstream.[1] Please migrate your Python apps to supported versions of Python before that time. Note: Unless you are manually specifying a version of Python for the buildpack to use, or you have customized your Python buildpack, no action is required. [1] https://www.python.org/downloads/release/python-343/ Thanks, Elliott Shanks, CF Buildpacks PM
|
||||||||||||
|
|
||||||||||||
|
cf CLI 6.47.0 regression and Windows not released
Abby Chau
Hi all, cf CLI 6.47.0 released but a regression found This is to let folks know that we've released cf CLI 6.47.0 which includes a multi-month refactor of `cf login`. See release notes for more information. However we've received reports that for some users, they've experienced issues using `cf login` on some platforms. We believe we've found the underlying cause now and will be releasing a patch soon. cf CLI `6.47.0` has now been marked as a pre-release. Windows support not released in cf CLI 6.47.0 This point might be moot given the above but we wanted to give you a heads up that due to cert renewal for Windows taking longer than expected, 6.47.0 does not include Windows support. We've recently received news that the cert has been renewed and so we are optimistic that we will be able to include Windows support in a release soon. We'd like to hear from you if this has an impact on your operations. Please do not hesitate to reach out should you have any questions or concerns via this email or through Cloud Foundry Slack #cli. Thanks everyone for your patience. Best, Abby Chau cf CLI, Product Manager
|
||||||||||||
|
|
||||||||||||
|
Issue for some users logging into CF using cf CLI 6.47
Abby Chau
Hi everyone, This is to inform everyone that we've had reports some users on cf CLI release 6.47.0 are experiencing issues with `cf login`. We are reviewing this issue and will provide updates as soon as we can. Thanks, Abby
|
||||||||||||
|
|
||||||||||||
|
Re: New CLA tool for Cloud Foundry
Chris Clark
CLA migration is complete, as of several minutes ago.
EasyCLA is now set up on all public repositories in the cloudfoundry, cloudfoundry-incubator, and openservicebrokerapi orgs. Dreddbot is disabled, and is scheduled for retirement in coming weeks. Please let me know have any questions or run into any issues with pull requests (chrisclark on CF Slack, christopherclark on GH)! Less urgently, if you have any thoughts on the new CLA workflow goes, or if there's anything that could be more intuitive, I'd love to hear about that as well.
|
||||||||||||
|
|
||||||||||||
|
cf7 CLI beta.26, roadmap, and deprecation of custom client workflows
Abby Chau
Hi everyone, We've released cf7 CLI beta.26! Here are some highlights:
See release notes here for more information including a large refactoring effort for cf login, and many new commands now backed by the v3 API. Important note: This release does not include the Windows installer because we are working on renewing the cert. We are currently working to include the Windows installer in the next release. This release adds a deprecation notice to login and auth for "custom client workflows". In an early version of the cf CLI, support was added to allow users to extend their refresh token using the config.json. If users require a longer-lived token, see the UAAC docs on how to do so. Instead of this workflow, use the cf auth command instead for pipeline-related use cases. More details can be found in the release notes above. New Roadmap Details in GitHub Projects We've added our roadmap information to GitHub so that you folks are able to review our current priorities for the next few months. We've also added a section where we are hoping to get feedback from you for items under consideration. We plan on releasing cf CLI v6.47 soon, which will include the login work. cf CLI v6.47 will also not include the Windows Installer but we hope to it include soon. In the meantime, do not hesitate to get in touch if you have any questions or feedback. We hang out in Cloud Foundry Slack #cli. Have a good weekend. Best, Abby, the v3 Acceleration and cf CLI teams
|
||||||||||||
|
|
||||||||||||
|
Re: [Proposal] Deprecation of the firehose endpoint
Mitch Seaman
Hi Steffen, confirmed. Dopplers are part of the v2 firehose, so the gRPC endpoint will still be available when v1 is deprecated. Regards, Mitch
On Thu, Oct 10, 2019 at 2:29 AM Steffen Uhlig <steffen.uhlig@...> wrote: Hi Jesse and Loggregator team, --
Mitchel Seaman Associate Director, Product Management @mitchelseaman
|
||||||||||||
|
|
