Releases: cloudfoundry/cli
v6.46.1
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Deprecation of --hostname, --no-hostname, -d, --route-path on cf push
The cf CLI team reached out to the Community back in December 2017 to gather feedback about domains and hostnames app manifest properties. Based on feedback, in cf CLI release v6.34.0, the team moved forward with deprecating domains and hostnames properties in the app manifest in favor of the routes attribute.
At the time, the flag options to override the manifest properties were not deprecated. This release deprecates the flag options on cf push:
--hostname--no-hostname-dfor domain--route-path
When any of the above flag options are passed to cf push, a deprecation warning appears in output text. story
We are seeking feedback on this for the cf7 beta CLI. Please add feedback and comments if you have any concerns.
Update-One Is Generally Available
The SAPI and Services Enablement Team are GA'ing the Update-One Feature in this release. story
- Adds a
--forceflag toupdate-serviceto support automation workflows story - Adds a helpful message if an upgrade is not available story
Bugs
- Fixes an issue where
update-user-provided-servicecan unset existing
credentials associated with a service even when the-pflags is not specified story
Plugin Updates
- Adds cf-security-entitlement plugin story
- Updates top plugin to v0.9.4 story
- Updates cf-puppeteer to 1.1.1 story
- Updates html5-plugin to 1.3.0 story
- Updates open plugin to v1.2.2 story
Contributors: Brendan Smith, Abby Chau, Andrew Crump, Alexander Berezovsky, Steve Taylor, Eric Promislow, Supraja Narasimhan, and the SAPI and Services Enablement team (Winna Bridgewater, George Blue, Aditya Tripathi, Oleksii Fedorov) for all the services-related work.
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0 (3.35). See our minimum supported version policy for more information.
v7.0.0-beta.24
Introducing the v7 beta cf CLI
Installation
Note: V7 beta binaries will be called cf7 to allow for coexistence with V6 cf binaries.
Package Manager Installation
Installers
Important note: Due to a bug with both the Mac and Windows Installer, we are removing the links to the v7 beta for these two Operating Systems. We hope to release 7.0.0-beta.25 with the fix soon.
Binaries
Compatibility
Tested against CC API Release Candidate 1.86.0-rc.21.
Background
The CC API team have been working on developing the v3 API, which introduced new features including running tasks, defining app processes via a Procfile, advanced deployment strategies, sidecars, and granular control of an application lifecycle.
To expose the v3 API to end users, the CLI team implemented v3 prefixed commands in CLI release v6.32.0; and in CLI release v6.38.0, we updated the cf7 app to use the v3 endpoint.
Whilst working toward this v3 effort, both the CC API and CLI teams came to the rea 8000 lization that development work for the v3 API, and the CLI's adoption of it, is best done as a dual effort.
To this end, both teams contributed engineers to form the V3 Acceleration Team, a team tasked with completing the v3 API, and developing a v7 cf CLI to support it - both of which are under active development.
Goals for v7 beta cf CLI
Release and make generally available cf CLI v7 which is completely backed by the v3 CC API so that we can unlock feature development which was not possible on the v2 CC API. As such, we've purposely kept changes between the v6 cf CLI and the v7 cf CLI to a minimum. Where there are differences, we have documented potentially breaking changes here.
Important Notes about v7 beta CLI
- Since both the v7 beta cf CLI and the backing CC API v3 are both in active development, it is important to note that the v7 beta cf CLI is subject to change as we move toward completing development. Therefore, using the v7 beta cf CLI in scripts is not recommended.
- Not all cf CLI v7 commands are backed by the CC API v3. As a result, commands still fall back to the v2 API. As we release the v7 beta cf CLI, more v3 resources will be developed along with the v7 beta cf CLI support for it.
- In order to complete the v7 beta cf CLI in a timely matter, we develop and test against the latest CAPI release candidate. When v7 cf CLI is generally available, we will start supporting official CC API releases again.
v3 CC API Resources and backing v7 beta cf CLI commands
As of 7.0.0-beta.24, the cf7 CLI beta commands backed by the v3 CC API include:
- push (Not a resource but the bulk of our work has been geared toward building
cf7 pushthat is completely backed by the v3 API) epic - domains epic
- routes epic
- feature-flags epic
- stacks epic
- buildpacks epic
- spaces epic
- organizations epic
- some v3 Services API support:
create-service-broker
Highlights
Rolling Deployments
cf7 pushis completely backed by the v3 API. New features including rolling deployments have been added tocf7 push app --strategy rolling. See New Workflows for more information. epic epic
Labels - metadata support
- labels metadata support (new commands:
set-label,unset-label,labels) for the following resources:apps,spaces,orgs. Additional support forbuildpacksandstacksand adding annotations and filtering labels coming soon. epic
Commands backed by the v3 API
- Resources mentioned above all completely backed by the v3 API on v7 beta cf CLI. Expect changes to flag options and arguments, removal of commands (kept to a minimum), a change to exit codes for one command (
create-buildpackanddeletecommands where the resource does not exist story), and new error output which comes directly from the v3 API. Errors and warnings print tostderrinstead ofstdout. For full details regarding changes to commands, please see v6 versus v7 command differences. - Pre-fixed
v3commands have been removed and are now the default command on v7. story
Please read the official CF documentation for additional information, and changes you might expect for 7.0.0-beta.24.
Gotchas
cf7 restarthas not been updated to use rolling deployments, we hope to start that work sooncf7 startdoes not restage on v7. We hope to update thecf7 restartcommand and thecf7 startcommand soon.cf7 routesis missing theservicescolumn, we are waiting on development of v3 servicescf7 orgis missing thequotascolumn, we are waiting on development of the quotas resourcecf7 create-orgdoes 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 withcf7 set-org-role.cf7 create-spacedoes 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 withcf7 set-space-role.
Documentation Resources
- Official Cloud Foundry documentation notes for v7 beta - includes information about breaking changes and feature development work available on v7
- Additional cf CLI v7 beta release notes for previous releases
Feedback
Do you have feedback or a bug report for the cf CLI v7 beta? Please file a GitHub issue here, or reach out on Slack #v3-acceleration-team.
Change Log for 7.0.0-beta.24
Below are the release notes for 7.0.0-beta.24. To review previous release notes for older version of the cf CLI v7 beta, go here.
CF Push
- experimental command output removed from
cf7 pushstory - support for
--random-routeis added tocf7 pushstory CF_STARTUP_TIMEOUTandCF_STAGING_TIMEOUTenvironment variables added tocf7 pushhelp text storycf7 pushis completely backed by the v3 API story story story--no-routewill now unmap routes including the default route story- bug fix for when bit service is enabled,
cf7 pushworks as expected story - bug fix for pushing an app when the directory contains empty files story
- additional
cf7 pushdocker and buildpack-related bug fixes story and story story story
Rolling Deployments
- explorations into updating an app when it is in the
Deployingstate; we advised users to usecancel-deploymentfor now and the CC API team will review in the future story
###...
v6.46.0
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Service Instance Upgrade feature
Service authors that have built services using the On-Demand Broker want to allow Service Instances to be upgraded individually after a new version of their Service Broker has been deployed.
Now cf services will inform users that an upgrade is available; running cf service <name> provides additional details. To upgrade a service instance, run cf update-service <name> --upgrade. This flag is in experimental stage and may change without notice.
Users must be on CC API v2.135 to use this feature.
For questions, regarding this feature please reach out to #SAPI on Slack Cloud Foundry. Thank you, SAPI team (Aarti Kriplani, Alex Blease, George Blue, Georgi Lozev, Henry Stanley, Nikolay Maslarski, Will Martin) who all worked on this feature.
Bugs
- Fixes
cf pushremove spin lock in PollStart(). This reduces the CPU time when waiting for apps to start. Also affectscf start,cf restartandcf restagestory - Fixes a documentation url in output story
- Fixes an issue whereby if you are logged in as a client, the user name was not printed in the output story
- Targeting a space for
cf copy-sourceis no longer case sensitive story - Retry plugin uninstall attempt for windows story
Plugin Updates
Release Contributors: Brendan Smith, Abby Chau, Andrew Crump, Alexander Berezovsky, Steve Taylor, Simon Seif, SAPI team (Aarti Kriplani, Alex Blease, George Blue, Georgi Lozev, Henry Stanley, Nikolay Maslarski, Will Martin)
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0 (3.35). See our minimum supported version policy for more information.
v6.45.0
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Known Issue with the log-cache-cli plugin
Recently changes (v6.44.0) were made to the CF CLI to no longer refresh authentication tokens in cases where we have an existing authentication token that has not yet expired.
In some circumstances users using the log-cache-cli plugin may see a temporary error when attempting to view logs for an application that has just been pushed. Log Cache maintains a one-minute cache on the server of the current applications associated with a token, and will reject requests for logs associated with an application it is not yet aware of.
As a workaround you can re-authenticate to obtain a new token or wait 60 seconds for the cache entry to be invalidated.
Using client credentials with cf oauth-token
This release adds support for using client credentials with the cf oauth-token command. This functionality was removed in cf CLI release 6.44.0; this release supports the workflow again but with changes in behavior:
- it is no longer possible to re-authenticate and return a new token when using client credentials with
cf oauth-token. See this issue for more information. - if your token is valid, running
cf oauth-tokenreturns the current token - if your token has expired, running
cf oauth-tokenerrors with a message to say that your access token has expired
For more information, please review this github issue and this tracker story.
Known issues with using client credentials
To prepare for this release, the cf CLI team did an exhaustive review of the client credential workflow:
- we ran all our integration tests using client credentials story story
- we checked for all the places in our codebase where we refresh the auth token story
We discovered the following issues with using client credentials:
ssh-codedoes not currently work with client credentials story- unrefactored commands will not print the client id in output text story
If you have any feedback about client credentials, please reach out to the UAA team (Cloud Foundry Slack #uaa), or the cf CLI team via a GitHub issue or on Cloud Foundry Slack #cli.
Bug Fixes
- Fixes a regression for
v3-pushwhilst viewing logs when authenticated as a client. Now you are able to see logs if you are logged in as a client and you attempt to view logs (cf logs for example).
Plugin Additions/Updates
Contributors:
Will Murphy, Brendan Smith, Abby Chau, Andrew Crump, and Alexander Berezovsky
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0 (3.35). See our minimum supported version policy for more information.
v6.44.1
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Fixes a regression with client credentials
Fixes a regression for viewing logs when authenticated as a client. Now you are able to see logs if you are logged in as a client and you attempt to view logs (cf logs for example).
Note: We have not fixed this regression on experimental v3-push, if you are authenticated as a client, and you are using v3-push you will not be able to view logs. Please reach out with any feedback.
v6.44.0
UPDATE: A regression has been detected for this release. The bug affect users using client credentials - logs will not appear for commands such as cf push or cf logs.
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Client credentials update to address security concerns
Changes to the client credential workflow
In CF CLI v6.35.0, we added support for client-credentials. During the implementation of the feature, the client secret was written config.json file to allow for token refresh in a pipeline workflow. In this release, we have reimplemented this feature to not write the client secret to the config.json.
Changes our users should expect from this change: if you are using cf auth --client-credentials and you upgrade to the CLI v6.44.0, you will be logged out of your session after 12 hours and be prompted to log back in.
We've decided to change this implementation because:
- Writing secrets to disk is a a security vulnerability we do not want to persist
- The default refresh token expiration is 12 hours. We believe a 12 hour refresh token should be sufficient for most pipeline-related activity and if users require a longer lived token, they can generate one using the
uaac- see documentation here
Note: cf oauth-token does not work with client credentials. Please reach out if there's a use case for this workflow.
Deprecation Notice for CF CLI Commands story
The following commands were deprecated because the V1 Broker API was deprecated as of January 2015. The CF CLI currently supports CC API 3.35.0/ Service Broker API Version 2.13.
create-service-auth-tokendelete-service-auth-tokenupdate-service-auth-tokenservice-auth-tokensmigrate-service-instancescf files
Using client credential for setting org and space roles
This release supports setting roles for a client. Updates include:
- a new optional
--clientflag forcf set-org-rolestory - a new optional
--clientflag forcf set-space-rolestory cf org-usersnow display the client name storycf space-usersnow display the client name story
Note:
- More information about the client credentials feature: API docs, UAA docs here and here
- If you are on an older version of cf-deployment (7.9.0 or lower) the CLI does not check to see if the client exists when we set orgs and spaces. Starting with cf-deployment 7.9.0, we added specific scopes to cf deployment to allow us to validate that a provided client exists when attempting to set an org or space role for a client. story
Minimum Version Warning
Our minimum version policy changed in January 2019 to support CC API 2.100/3.35. In this release, we will start outputting a warning when users are on a unsupported version of the CC API. cf api, cf auth and all rewritten code will display this warning.
Built with Golang 1.12.1
Updated to Golang 1.12.1 See the Golang release summaries for details on the bug fixes. story
New Translations
New translations are included in this release - thanks to IBM who contributed updated translations of CLI output and help text. As usual, the update came in mid-release and a number of message strings may have changed since, but will be included in the next release. story
Enhancements
- A new flag
--no-plansadded tocf marketplaceto view the table without theplanscolumn story
Minor Enhancements
cf helpnow displays a more prominentTIPso that users can discovercf help -a- Roles for the
set-org-roleandset-space-rolecommands are case insensitive story - Piping a multi-line file to
cf loginnow works as expected story - Updated the help text for
cf delete-orphaned-routesto clarify that the command is spaced-scoped story
Bug Fixes
- Fixes a bug for
cf update-buildpackfor assigning stacks story - Fixes an issue with
cf-bind-route-servicewhereby if a user does not have aorgorspacetargeted, instead of returning a useful error, the CLI would attempt toGETtheprivate_domainsendpoint story v3-apply-manifestnow works for defining environment variables in a multi-app manifest story- Now the CLI checks the expiration time of an access token and refreshes it automatically before making a call the CF API story
Plugin Additions/Updates
- Updated html5-plugin to
1.2.0story - Updated CF Dev to
0.0.15story - Updated cf-puppeteer to
0.0.13story - Updated Create-Service-Push to
1.3.1story - Updated conduit to
0.0.7story - Adds push-with-vault story
- Adds set-weights story
- Adds multi-apps plugin story
Contributors:
Thomas Viehman, Will Murphy, Brendan Smith, Abby Chau, Andrew Crump, Alexander Berezovsky, SAPI team (Aarti Kriplani, Alex Blease, George Blue, Georgi Lozev, Henry Stanley, Nikolay Maslarski, Will Martin) for all the services-related work, Simon Seif (thanks for the pull request!), V3 Acceleration Team, IBM (for Translations work)
Thank you to all our Community contributors, we appreciate the pull requests!
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0 (3.35). See our minimum supported version policy for more information.
v6.43.0
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Multi-Service Registration epic
CF now allows multiple service brokers to offer services with the same name and or to have the same catalogs. (However, brokers themselves must still be given a unique name.)
Note: Multi-service registration is only supported on CC API version 2.125.0 or greater.
Users can specify which broker to use with a new -b flag, which is available on the following commands:
cf create-servicecf enable-service-accesscf disable-service-accesscf purge-service-offeringcf service- now display broker namescf marketplacenow display broker names
Important Note: If you have two services with the same name, the commands above will now require the -b flag to disambiguate which service and broker you want to operate on.
For more information: For more information regarding this feature and other services-related work in this release, reach out to cf-services-api@pivotal.io or #sapi on Cloud Foundry Slack.
Enhancements
cf curlsupports a new--failflag (primarily for scripting purposes) which returns exit code22for server errors story- Improves
cf delete-orphaned-routessuch that it uses a different endpoint, reducing the chance of a race condition when two users are simultaneously deleting orphaned routes and associating routes with applications story - we've improved the speed of cf services - it now hits a single endpoint instead of making individual API calls
Minimum Version Cleanup
Our minimum version policy changed in January 2019 to support CC API 2.100/3.35. This release removes code which support CC API below those versions. story
Bug Fixes
Security
- Fixes issue with running
cf loginin verbose mode whereby passwords which contains regex were not completely redacted - Fixes issue whilst running commands in verbose mode refresh tokens were not completely redacted
32-bit systems
- Fixes a bug for users on 32-bit syst
8000
ems where the CLI would fail to unmarshall responses from the server because the response contained integer values that, when unmarshalled, would overflow 32-bit integers. For example, now users on 32-bit systems, can now set their memory usage larger than 2GB for
cf push. See the list of commands below which we've applied the fix for. story story
| CC Version | Resource | Field | Affected Commands | |
|---|---|---|---|---|
| v2 | App | HealthCheckTimeout | push |
|
| v2 | App Instance Status | Disk | create-app-manifest |
|
| v2 | App Instance Status | DiskQuota | create-app-manifest |
|
| v2 | App Instance Status | Memory | create-app-manifest |
|
| v2 | App Instance Status | Memory | create-app-manifest |
|
| v3 | Process | Health Check Invocation Timeout | v3-set-health-check, v3-get-health-check |
|
| v3 | Process | Index | ||
| v3 | Process Instance | Uptime | push, restage, restart, start, app |
|
| v3 | Task | Sequence ID | tasks, run-task |
|
| v3 | Job | Code | v3-delete, v3-apply-manifest |
Other Bug Fixes
- Updates help text for
cf curlstory - Now refresh tokens work properly whilst using
cf curlwith V3 CC API endpoints story - Fixes performance degradation for
cf servicesstory cf delete-servicerequires that you are targeting a space storycf enable-service accessfor a service in an org will succeed if you have already enabled access for that service in that org storyrename-serviceupdated to no longer fail if a plan has been removed from the catalog story
Plugin Additions/Updates
-
Added anchor links to the plugin page story
-
updates autoscaler-cli story
-
updates log-cache-cli to
v2.1.0story -
updates report-memory-usage story
-
adds log-stream plugin story
-
adds HTML5 Plugin v1.1.0 story
Contributors:
Thomas Viehman, Jennifer Spinney, Will Murphy, Magesh Kumar Murali, Alex Shan, Brendan Smith, Abby Chau, Aarti Kriplani, Alex Blease, Georgi Lozev, Henry Stanley, Laurel Gray, Niki Maslarski, Oleksii Fedorov, William Martin, Adam Eijdenberg (for the plugin page anchor links pull request), David Grizzanti (for the delete orphaned routes pr)
Thank you to all our Community contributors, we appreciate the pull requests!
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0 (3.35). See our minimum supported version policy for more information.
v6.42.0
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Space to Space Policy story
Supports a Container to Container feature for cf add-network-policy to enable adding network policies between spaces. Changes include:
-oand-sflags have been added to thecf add-network-policyand thecf remove-network-policycommands to support adding network policies to a specific organization and space- the
cf network-policiestable output has been updated with additional columns to indicatedestination spaceanddestination org
Note:
- Users on versions of CC API lower than 3.56.0 may experience some latency due to the fact that the CC API did not support the
guidsfilter param (which we require to displaydestination organddestination spaceincf network policies. Users on versions of CC API greater than 3.56.0 should not experience latency issues. - This release includes changes to existing output to specify the destination app.
Services-related Refactors
Important Note:
We've discovered that for commands we've refactored previously, the CLI started incorrectly allowing for additional arguments to be passed in commands, which are silently ignored. Moving forward, if you provide additional arguments to a command, the command will fail with a meaningful message. We plan on making a global change in a future major release of the CLI. details
In order to prepare for a upcoming service-related feature, the Services API team in London refactored the following commands.
User-facing changes include:
Updating output where necessary and flavor text to promote consistently as described in our style guide
Minor Enhancements
- updated
cf restagehelp text and the first line in the command's output to indicate that using this command will cause app downtime story - updated the
cf bind-route-servicehelp text to clarify usage instructions story - improved an error message for
cf create-service-bokerto be more helpful when the CC API returns a502due to an invalid service broker catalog - upgraded to Golang 1.11.4 story
- added a short name
ueforcf unset-envstory - updated
cf marketplacecommand to include a newbrokercolumn to prepare for a upcoming services-related feature which will allow services to have the same name as long as they are associated with different service brokers story
Bugs
- fix for
cf enable-service-access -p planwhereby when we refactored the code in CLIv6.41.0it created service plan visibilities as part of a subsequent run of the command (the unrefactored code skipped creating the service plan visibilities); now the command will skip creating service plan visibilities as it did prior to the refactor story - updated the
cf rename-buildpackhelp text which was missing reference to the-sstack flag story - updated help text for when users use
brew search cloudfoundry-clistory - now when you run
cf service service-instancefor a route service, the route service url appears in the key value table story
Plugin Updates
Contributors: Thomas Viehman, Jennifer Spinney, Will Murphy, Magesh Kumar Murali, Abby Chau, SAPI Team (Big thanks to the SAPI team for providing the services-related refactors, along with some services-related bug fixes), Container to Container Networking Team (huge thanks for providing the pull requests for the C2C feature)
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.100.0. See our minimum supported version policy for more information.
v6.41.0
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Assign a Stack to a Buildpack epic
Supports the ability to assign a stack to a buildpack that is missing stack metadata. See official documentation for more details.
Important Note: It's important to note that once you assign a stack to a buildpack, you cannot undo the action unless you have access to your buildpack bits.
Additional notes:
- If you have two buildpacks with the same name, and one has a stack associated, and the other has a
nilstack; when you runcf update-buildpack buildpack-name --assign-stack stack- the buildpack withnilstack will be updated.
Service Discovery epic
With app service discovery, apps pushed to Cloud Foundry can establish container-to-container communications through a known route. This allows front end apps to easily connect with back end apps.
Now users can use cf create-shared-domain internal.com --internal to create an internal route, and domains has been updated to include a new details column to let users know if a route is internal.
See official documentation for more details.
Refactors
Important Note:
We've discovered that for commands we've refactored previously, the CLI started incorrectly allowing for additional arguments to be passed in commands, which are ignored silently. Moving forward and starting with these refactored commands, if you provide additional arguments to a command, the command will fail with a meaningful message. [details](https://www.pivotaltracker.com/story/show/162259630]
Note we intend to fix this bug for all refactored commands in a major CLI release see additional details
Services-related Refactors
In order to prepare for a upcoming service-related feature, the Services API team in London refactored the following commands. Big thanks to the SAPI team for providing this work to us.
User-facing changes include:
- Updating output where necessary and flavor text to promote consistently as described in our style guide
Create-shared-domain Refactor
In order to prepare for the Service Discovery (Container to Container Networking feature), we've refactored cf create-shared-domain.
story
User-facing changes include:
- Updating output where necessary and flavor text to promote consistently as described in our style guide
Built with Golang 1.11.x story
Updated to Golang 1.11. See the Golang release summaries for details on the bug fixes.
Enhancements
- updated
cf --helpto include thedeletecommand story
Plugin Updates
- Updated conduit plugin
v0.0.6 - Updated cf recycle plugin (cloudfoundry/cli-plugin-repo#268)
- Updated cf bg-restage plugin (cloudfoundry/cli-plugin-repo#269)
- Updated cf sync plugin (cloudfoundry/cli-plugin-repo#270)
Contributors: SAPI London team (for the marketplace refactor), Slawek Ligus and the C2C Networking team (for cross team efforts for the Service Discover feature) Thomas Viehman, Jennifer Spinney, Will Murphy, Magesh Kumar Murali, Abby Chau
Note: The minimum version of the CC API this CF CLI release is compatible with is CC API v2.69.0. See our minimum supported version policy for more information.
v6.40.1
Package Manager Installation
Installers
- Debian 64 bit / 32 bit (deb)
- Redhat 64 bit / 32 bit (rpm)
- Mac OS X 64 bit (pkg)
- Windows 64 bit / 32 bit (zip)
Binaries
Change Log
Create-service-key Refactor
In order to prepare for a upcoming service-related feature, the Services API team in London refactored create-service-key. Big thanks to the SAPI team for doing this work for us. story
User-facing changes include:
- improving error messages (for permissions-related errors, and successful output handling if a user is using a async broker)
- enhancing the UX to remove flavor text and
- updating output to return consistently for failures to promote consistency as described in our style guide
Service Instance Now Displays Binding Operation Type
Now when you run cf service service-instance to display information for a async binding, in the status field in the bound apps table, more verbose text is returned for when you create and delete a binding. story
Bug Fixes
- Updates the minimum version for the buildpacks-stacks association feature. In CLI v6.39.0, when the feature was released, we incorrectly set the minimum to cc api version as
2.114. The minimum cc api version is now correctly set to2.112. story - Fixes a bug with inspecting a service instance
cf service service-instance, now thedocumentationurl displays correctly for services which populate that field story
New Translations
New translations are included in this release - thanks to IBM who contributed updated translations of CLI output and help text. As usual, the update came in mid-release and a number of message strings may have changed since, but will be included in the next release.
Plugin Updates
- Updated CF Dev v0.0.12
- Updated MysqlTools v0.6.0
- Updated spring-cloud-services v1.0.3
- Updated log-cache-cli v2.0.0
- Updated metric-registrar v1.1.0
Contributors: SAPI London team (for the create-service-key refactor and the fix for the service documentation url), Anande Gaitonde, Thomas Viehman, Will Murphy, Abby Chau, Magesh Kumar Murali, Jennifer Spinney
Special Guests:
Dr. Max and the IBM China team (for translation updates)