github cloudfoundry/cli v7.0.0-beta.27
on GitHub

latest releases: v8.7.10, v7.7.10, v8.7.9...
pre-release4 years ago

Installation

Note: V7 beta binaries will be called cf7 to allow for coexistence with V6 cf binaries.

Package Manager Installation

Installers

Binaries

Compatibility

Tested against CC API Release Candidate 1.89.0-rc.4*.

Change Log for 7.0.0-beta.27

v3 CC API Resources and backing v7 beta cf CLI commands

  • events is now backed by the v3 API
  • set-org-role is now backed by the v3 API story
  • set-space-role is now backed by the v3 API story
  • rename-service-broker is backed by the v3 API story

Enhancements:

  • update to cf start to support multiple workflows story:
    • Use Case: using --no-start to configure your app before starting it: now cf push app --no-start --> configure app ---> cf start works as expected
    • Use Case: Rolling back your app now if you've rolled back your application (using set-droplet, for example) and you use cf start, start will use the droplet you've explicitly set
    • Notes: If we detect that there is a new package, we will always stage the new package
  • support for tagging resources: now you can use set-label, unset-label, and labels to set metadata for the domain resource
  • now if you are running tasks and your app is not a long running process story:
    • cf push supports a new --task flag. Configure your manifest with a task process type and then run run-task. Other changes for tasks:
    • run-task: now takes a --process flag. If you have configured your manifest as specified above, this flag is not required, and your task will run as expected using the start command for the process type provided in your manifest.
    • run-task: start command (previously a required arg) is not an optional flag

Built with Golang 1.12.12

Golang 1.12.12 addresses security vulnerabilities and other bugs. See the Golang release summaries for details.

Gotchas

  • "v6" plugins do not work on a v7 cf CLI because we are developing a new plugin interface which calls the v3 API. install-plugin will allow you to install a v6 plugin but when you attempt to run the plugin, it fails. In the next v7 cf CLI release, we will disallow installation of v6 plugins on a v7 cf CLI, and vice versa.
  • cf7 create-org does not assign the current user roles in the org after creating, since we are waiting on development of v3 users/roles. Roles can still be assigned afterwards with cf7 set-org-role.
  • cf7 create-space does not assign the current user roles in the space after creating, since we are waiting on development of v3 users/roles. Roles can still be assigned afterwards with cf7 set-space-role.
  • When you use a v6 CLI to create-service-broker and subsequently run cf7 service-brokers, the newly created service broker will appear as unknown. You must use cf update-service-broker to update the service broker. A TIP was added to service-brokers to advise users about this. The Services Enablement Team will revert this change for the next release. story

Documentation

Feedback

Do you have feedback or a bug report for the cf CLI v7 beta? Please file a GitHub issue, or reach out on Cloud Foundry Slack #v3-acceleration-team.

V3 Acceleration Team Core Contributors to v7 CLI beta: Eli Wrenn, Reid Mitchell, Piyali Banerjee, Greg Cobb, Supraja Narasimhan, Abby Chau, Mona Mohebbi, Brian Cunnie, Teal Stannard, Merric de Launey, Belinda Liu, special thanks to Connor Braa for the start xtp work

CF CLI - v7 Feature Development Contributors: Brendan Smith, Andrew Crump, Abby Chau, Eric Promislow, Alexander Berezovsky, Steve Taylor, Jenna Goldstrich, Joseph Palermo, special thanks to Zach Robinson for the tasks pull request

Services API/CLI Contributors: Oleksii Fedorov, Aditya Tripathi, George Blue, Felisia Martini, Winna Bridgewater

Check out latest releases or
releases around cloudfoundry/cli v7.0.0-beta.27

Don't miss a new cli release

NewReleases is sending notifications on new releases.

Get notifications