github cloudfoundry/cli v6.39.0

latest releases: v8.7.9, v7.7.9, v8.7.8...
5 years ago

Package Manager Installation

Installers

Binaries

Change Log

Buildpacks association with Stacks

In order to help with the transition to cflinuxsf3 in April 2019, stack association with buildpack is introduced in this release.

  • Buildpacks can now have the same name, as long as they are associated with a unique stack. update-buildpack, rename-buildpack, and delete-buildpack now support a -s stack flag to disambiguate buildpacks with the same name epic
  • In order to update-buildpack, rename-buildpack, or delete-buildpack a buildpack with a duplicate name, you must disambiguate the buildpack by providing a stack association with the -s option
  • In order to update-buildpack, rename-buildpack, or delete-buildpack a buildpack that has a unique stack, you do not need provide a -s option
  • In order to update-buildpack, rename-buildpack, or delete-buildpack a buildpack that has no stack association, you do not need to provide a -s option
  • cf buildpacks table display is updated with a new stack field

Review this documentation for more information about this feature, including usage examples.

Refactored commands (rewrites)

In order to prepare for the buildpack - stack association feature, the CLI embarked on a rewrite (refactor) of a subset of buildpacks-related command. User-facing changes include promoting consistency, improving error messages, and enhancing the UX to provide additional information. See below for more information.

We also refactored the create-org command to prepare for work on fixing an existing issue with creating orgs whilst logged with client credentials.

Create Buildpack epic

  • in order to move toward establishing a more consistent CLI experience, create-buildpack now shows more verbose output:
    • user role is outputted when creating a buildpack
    • a upload progress bar is displayed in the output information
  • Fixes a bug whereby previously when you have manifest.yml in your path, that file is ignored when the directory is zipped up story
  • now when you attempt to create a buildpack and you provide a path to an empty directory, the CLI prevents you from creating the buildpack story
  • we no longer validate whether the buildpack zip file contains a bin/compile, which has been deprecated for some time. As a result, the CLI no longer modifies the contents of user provided zip files; previously we defined a buildpack as at the root of bin/compile story
  • the --enable is found to be unnecessary since creating a buildpack will enable the buildpack by default when you use the create-buildpack command story

Rename Buildpack epic

  • error message for when attempting to rename a non-existent buildpack updated

Update Buildpack epic

  • now when you attempt to update a buildpack and you provide a path to an empty directory, the CLI prevents you from creating the buildpack story
  • we no longer validate whether the buildpack zip file contains a bin/compile, which has been deprecated for some time. As a result, the CLI no longer modifies the contents of user provided zip files; previously we defined a buildpack at the root of bin/compile story

Create-org Refactor epic

  • correction to color text output as prescribed by our style guide

Support for Async Operations for Service Bindings epic

  • cf bind-service and cf unbind-service now supports asynchronous operations. The output of both commands have changed accordingly with additional information how to view operation status details.
  • cf service service-instance has been updated such that the service instance information section is separated from the bound apps information. status and message has been added added to the bound apps information.

cf auth supports the --origin option to log in to different identity providers epic

The cf auth command is updated to include an optional --origin flag, so that users can more seamlessly log in to different identity providers. If not provided, cf auth continues to default to the UAA internal data store. See the UAA api documentation for more information.

Service instance sharing is no longer experimental

In CLI release v6.35.0 we introduced service instance sharing, which enables you to share service instances between spaces in the same or in a different organization. The share service CLI commands are no longer experimental.

Enhancements

  • for users on cc api 3.27, cf start is enhanced to display the new cf app v3 output. For users on cc api 3.27 or lower, users will see the same v2 output. Note that if you use v3 commands to create and start your app, if you subsequently use cf stop and cf start, the routes property in cf app will not populate even though the route exists story
  • for users on cc api 3.27, cf restart is enhanced to display the new cf app v3 output. For users on cc api 3.27 or lower, users will see the same v2 output. story
  • for users on cc api 3.27, cf restage is enhanced to display the new cf app v3 output. For users on cc api 3.27 or lower, users will see the same v2 output. story
  • improved help text for -d domains for cf push to include examples of usage story
  • cf v3-scale displays additional app information story
  • if you've created an internal domain, and it is the first domain in cc, the CLI will now ignore the internal domain and instead choose the next non-internal domain when you push an app story

Bug Fixes

  • Fix for users on macOS attempting to brew install cf-cli the CF CLI using the unreleased master branch of Homebrew story
  • Fixes an issue whereby, due to a recent cc api change, when you execute cf push and watch the cf app command, the app display returned a 400 error story
  • Fixes a bug whereby if you logged in using client credentials, cf auth user pass --client credentials you were unable to create an org; now create-org will assign the role to the user id specified in your manifest story
  • fixes an issue introduced when we refactored cf start and as part of that work, we stopped blocking on the initial connection with the logging backend; now the CLI blocks until the NOAA connection is made, or the default dial timeout of five seconds is reached story

Plugins Updates

  • Updated CF Dev plugin #247
  • Updated Log Cache CLI plugin #248
  • Updated Blue Green plugin #248

Contributors: An Yu, Sebastian Vidrio, Anande Gaitonde, Thomas Viehman, Alex Zhao, Abby Chau, Spencer Hawley, Renee Chu, Nick Guerette, Ryan Tang, William Murphy

Special Guests: Buildpacks team (for help with the buildpack-stack association feature), SAPI London team (for pull requests and the async operation work), SAP and UAA Team (for help with the cf auth --origin work)

Don't miss a new cli release

NewReleases is sending notifications on new releases.