Skip to content

V7 Beta Release

Abby Chau edited this page Aug 20, 2019 · 59 revisions

7.0.0-beta.23

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • cf stage backed by the v3 API story
  • cf apply-manifest backed by the v3 API; also changes the behavior whereby if no flags are passed, the command defaults to using the manifest located in their pwd

Rolling Deployments epic

  • Now app developers using cf push can use a new --strategy flag on cf push to deploy their applications without down time. cf push app_name --strategy rolling exits when at least one instance of each process is healthy story
  • Adds support for a --no-wait flag to push; when used, the command exits when the one instance of one process becomes healthy
  • Adds support for a cf cancel-deployment command; when a rolling deployment is in progress, the command will reset the current droplet to be the previously deployed droplet. story

Routes epic

  • routes-related CLI commands are backed by v3 (delete-route, routes, map-route, unmap-route,check-route (no longer requires a backslash), delete-orphaned-routes)
    • Breaking:
      • routes - the services column has not yet been implemented (waiting on the v3 services endpoint to be implemented).

create-service-broker

  • support for create-service-broker --space-scoped(Thanks, SAPI team, for this work.) story

7.0.0-beta.22

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

Domains

  • delete-private-domain uses the v3 API (epic)
    • Breaking:
      • Removes support for router groups and tcp routing.
      • Renamed delete-domain to delete-private-domain to explicitly call out that the command deletes a private domain

Routes epic

  • create-route is backed by the v3 API.
  • Breaking:
    • Space is no longer a required argument. The command defaults to the current targeted space.
    • Support for TCP Routing removed in favor of using an upcoming Istio solution. Support for --random-port and --port have been removed.
  • cf routes is backed by the v3 API.
  • Breaking:
    • Display changes including removing port and type from the table.

CF Push

  • adds support for --droplet story

Service Brokers

  • cf service-brokers is backed by the v3 API

Other Updates

  • prefixed v3 commands on v6 are now the default command on v7 epic:
    • cf apps
      • Breaking:
      • Updates the app display to display information about processes. The url field renamed to routes. Removes display information about instances, memory, and disk. And now the command lists apps alphabetically.
    • cf start
      • Breaking:
      • cf start no longer stages an app. We will introduce a new --stage flag in an upcoming release.
    • cf restart-app-instance
      • Supports a new --process flag
    • cf create-package
    • cf restart
    • cf packages
      • Updated to display the most recent package in the list in descending order.
    • cf create-app
    • cf set-droplet
    • cf droplets
    • cf stop

7.0.0-beta.21

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

CF Push epic

  • Support for server-side manifests epic
  • Push resource matching works if all of an application's files are already cached (story)
  • Support for all v6 flags push flags except for --random-route and --route-path
    • Changes:
      • adds a new --endpoint flag to support a path for setting a health check type
      • setting a --health-check-type for an HTTP health check now requires an endpoint flag
      • specifying --no-route no longer unmaps routes from the app
    • added short form and long form support (For example, -t now has a long form name: --app-start-timeout) for flags

Domains

  • create-shared-domain, create-private-domain, domains, share-private-domain``unshared-private-domain, delete-shared-domain uses the v3 API (epic)
    • Breaking:
      • Removes support for router groups and tcp routing.
      • domains table changes including renaming column headers (status to availability), and text to indicate a private domain from own to private, removal of type column
      • Renamed create-domain to create-private-domain to explicitly call out that the command creates a private domain

7.0.0-beta.20

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log


7.0.0-beta.19

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.19 is an edge release of the CC API: capi-1.79.0-rc.90-3ec83a. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.18

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • Application manifests support pushing public docker images (story)
  • Application manifests support paths to application source (story)
  • Application manifests support the no-route property (story)
  • Push uses resource matching to speed up pushing the same files multiple times (story)
  • Push detects manifests in current directory ending with .yaml extension (story)
  • Push detects manifests ending with .yaml extension in directory specified by -f flag (story)

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.18 is an edge release of the CC API: capi-1.79.0-rc.58-30b9d1. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.17

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • Add error if file paths in manifests are invalid (story)
  • Application manifests support pushing private docker images (story)
  • Push supports manifests with multiple private docker images with the same password (story)

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.17 is an edge release of the CC API: capi-1.79.0-rc.35-6e675c. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.16

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • Re-organize help text for cf-push to match v6 (story)
  • Push flags apply when pushing a single application from a multi-app manifest (story)

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.16 is an edge release of the CC API: capi-1.78.0-rc.43-871337. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.15

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • Using -s flag will override stack value in manifests (story)
  • Using -t will override health check timeout value in manifest (story)
  • Update output of feature-flag command (story)
  • Update output of enable-feature-flag (story)
  • Update output of disable-feature-flag (story)
  • Push now supports manifests with multiple applications (story)
  • Add error when using flag options (exceptions: no-start and -f) with a multiple app manifest (story)
  • App name positional argument is no longer required when pushing with a manifest containing an app name (story)
  • Specifying an app name positional argument when pushing with a multi-app manifest will only update that app (story)
  • Add error when pushing a multi-app manifest with an app name positional argument that does not match the name of an app in the manifest (story)
  • Failures when pushing with a multi-app manifest will not update apps after the one that failed (story)

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.15 is an edge release of the CC API: capi-1.78.0-rc.27-9a6243. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.14

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • Add -s/--stack flag to push command (story)
  • Add --endpoint flag to push command. Breaking: This flag is now required if you set health check type to http when pushing an application. Previously, the health check endpoint would default to \. (story)

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.14 is an edge release of the CC API: capi-1.78.0-rc.15-27462d. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.13

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

  • No Changes

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.13 is an edge release of the CC API: capi-1.77.0-rc.23-850836. We plan to start supporting older versions of the CC API once we GA the V7 CLI.


7.0.0-beta.12

Important Note: The CF CLI v7-beta binaries are currently in the process of development and are therefore dynamic in nature - features and commands are subject to change. We welcome feedback on the beta releases - reach us via email (cf-cli-eng@pivotal.io) or on Cloud Foundry Slack (#v3-acceleration-team).

Package Manager Installation

  • homebrew - Note: cf7-cli is the formula name for the V7 Beta.

Installers

Binaries

Change Log

As the V7 CLI is currently under development, we've attempted to list any (major or minor) changes here so that app developers can track any changes which might impact their workflows and deployment strategies. However, since we are supporting a new V3 CC API, there may be additional behavioral changes we have not noted. For instance, in V3, deleting an app is now done asynchronously.

Backwards Compatibility

So that we may rapidly develop the new major version of the CLI, CLI v7-beta is not compatible with older versions of the CC API. During beta development, the CLI V7 beta releases will only be compatible with the CC API release it was developed and tested against which in this case for 7.0.0-beta.12 is an edge release of the CC API: capi-1.77.0-rc.17-4ad377. We plan to start supporting older versions of the CC API once we GA the V7 CLI.

Commands now backed by the V3 API

  • cf stacks V3 API documentation
  • buildpacks-related commands (create-buildpack, update-buildpack, delete-buildpack)

Commands removed from v7 CLI

  • cf rename-buildpack has been removed in favour of a new --rename flag which has been added to cf update-buildpack story
  • cf files removed since the command only worked with DEAs, which has no longer been supported since 2016

The following services commands were removed from v7 CLI for the following reason: these commands were for interacting with service brokers that implemented the V1 Broker API, which has not been supported since at least January 2015:

  • cf create-service-auth-token
  • cf delete-service-auth-token
  • cf update-service-auth-token
  • cf service-auth-tokens
  • cf migrate-service-instances

Deprecated manifest properties have been removed in V7

  • in CF CLI v6.34.0, several manifest-related features and properties were deprecated, in CLI V7 deprecated properties domain, domains, host, hosts, and no-hostname have been removed in favor of routes
  • removed health-check-type: none, which was deprecated since at least February 2017 in favor of using health-check-type: process

CLI no longer ignores additional arguments

  • when additional arguments are provided to CLI commands, the CLI exits 1 and provides a useful error message. For additional background regarding this change, see the release notes for CLI v6.42.0. story

Manifest related changes:

  • if using cf create-app-manifest to download the manifest, the manifest now includes default information for app processes story
    • the disk default is not in megabytes instead of gigabytes
    • health-check-type now appears for each process

Exit codes

  • create-buildpack now exits with 1 if you attempt to create a buildpack and stack association which already exists AND a database entry for buildpack with a nil stack association is created in the CC API. An improved error message is outputted to help users update or delete the database entry for the buildpack with a nil stack
  • create-buildpack exits with 1 if attempting to create a buildpack with a nil stack and a buildpack with a nil stack already exists

CF PUSH

  • We are still building cf push and so this release is missing some core push functionality including flag parity, and some manifest properties (docker, path, multiple app support) is not yet supported.
  • --health-check-type none removed from cf push in favor of --health-check-type process story (https://www.pivotaltracker.com/story/show/159289266)
  • Pushing with the --no-route flag no longer unbinds all existing routes associated with the application; now using no-route only skips route creation story
  • Applying a manifest to an app is now done at a space level, rather than at the app level. This change should not impact user-facing behavior. story

CF Buildpacks

  • updated cf buildpacks table display to reorder columns for clarity story
  • removed --enable from the create-buildpack command as creating a buildpack by default enables it, and there is no supported way to disable a buildpack upon creation story
  • cf update-buildpack now supports use of --path and --unlock so that users can upload new bits and simultaneously unlock their buildpack story
  • now using cf update-buildpack with assign-stack if you only have one buildpack with that name results in an idempotent response, previously the command would error and exit 1 story
  • changes to output text to promote consistency and to provide a TIP where it is helpful to do so

Changes to v3 prefixed commands:

  • removal of experimental text and warnings
  • all previously prefixed commands (see list below) are now all backed by the v3 API output for all commands now are consistent with our style guide
  • polling information for certain commands have been either reduced or removed for a cleaner user experience
  • Changes to these commands include:
    • cf env
      • changes include cleaning up the output such that OK and environmental variables are outputted as per our style guide help text for the command
    • cf set-env
      • no changes
    • cf delete
      • currently does not support the -r flag. We plan to support this flag in a future beta release
    • cf scale
      • supports a new --process flag so that app developers can scale select an app process to scale (Default: web)
      • the output for this command has been updated to the app view, allowing app devs to instantly view app details
      • no longer outputs information about app starting and command information
      • polling information has been removed including app starting and running information and command-related output; now users can obtain this information from viewing the app details which is now outputted for this command
    • cf ssh
      • supports a new --process flag (to specify the app process) and a new environmental variable all_proxy= (to specify a proxy server to enable proxying for all requests)
    • cf unset-env
      • no changes
    • cf set-health-check
      • supports a new --process flag so that app developers can select which app process the health check belongs to. (Default: web)
      • supports a new --invocation-timeout flag, allowing app devs to set per invocation timeouts for http and port health checks for individual health checks
    • cf get-health-check
      • the output has been updated to a table instead of a key value display so that users can more easily view related information including details about invocation timeout

UX Changes

  • Updated command output for clarity
  • Updated commands to display the new "refactored" style including standardizing UI output (for example, warnings and errors will consistently be outputted to stderr instead of stdout, no flavor text in table display, reordering of error messages)
  • Long form flags have been added to commands with their short form counterparts

Minor Enhancements

  • cf target now displays the V3 API version you are targeted to, V2 API information is no longer displayed story
You can’t perform that action at this time.