v2.5.1

2.5.1 - 2018-04-03

Fixed

• create-service-broker command now only targets an org and space if space_scoped: true
• Remove un-necessary cf_target call from create-domain

v2.5.0

2.5.0 - 2018-04-02

Added

• scale command - Change or view the instance count, disk space limit, and memory limit for an app
• create-domain command - Create a domain in an org for later use
• delete-domain command - Delete a domain
• map-route command - Add a url route to an app
• unmap-route command - Remove a url route from an app
• run-task command - Run a one-off task on an app, thanks to a PR by @bigorangemachine

Changed

• Updated to cf cli v6.35.2

General Code Cleanup

• Change tests to support Orgs and Spaces with spaces
• Add necessary variable quoting
• Remove un-necessary variable quoting
• Use parameter expansion in cf_* functions to check all required args and allow optional args
• Use array for dynamic argument building for cf cli calls to retain argument quoting
• Removed unused function: cf_create_org_if_not_exists
• Removed unused function: cf_create_space_if_not_exists

v2.4.3

2.4.3 - 2018-02-23

Fixed

• create-user-provided-service when checking if a ups already exists, the command now only checks the current space instead of every space the user has access to.

v2.4.2

2.4.2 - 2018-02-16

Fixed

• delete-service command's wait_for_service now only checks the current space instead of every space the user has access to.

v2.4.1

2.4.1 - 2018-02-09

Fixed

• cf_trace: true no longer messes up cf calls that are intended to capture the json output inside scripts. For now, we set CF_TRACE=false for all cf calls where we need to capture the output. I think there is a way to redirect the CF_TRACE output, but I couldn't figure it out with the way we do stdout and stderr redirects in the out script. Until then, please note that you won't see the trace info every cf command used in the script.

v2.4.0

2.4.0 - 2018-02-08

Added

• We now have a dedicated Cloud Foundry instance to use for integration testing (thanks Pivotal!!). This should help turn-around PRs and issues a little faster.
• Support cf_trace, cf_dial_timeout and cf_trace configurations for source and command params.
• unbind-service command - Unbind a service instance from an app

Changed

• Updated docs to clarify the use of logical names for put steps.
• delete-service command now supports wait_for_service param for deleting asynchronous services.
• Refactored integration tests to default to PCF Dev for local testing while allowing for overriding by exporting env vars before running the test script.
• Added test job to pipeline to run the integration tests after the Docker image is built.
• Refactored service creation/binding/deletion tests to better focus on synchronous and asynchronous services.

Fixed

• wait-for-service command errors if the service does not exist.

v2.3.1

2.3.1 - 2018-01-08

Fixed

• Fixed enable-service-access and disable-service-access both now properly treat plan and access_org as optional, thanks to a PR by @legnoh
• Docs for enable-service-access and disable-service-access have been corrected to reference service_broker argument name (was incorrectly set to service).

v2.3.0

2.3.0 - 2017-11-14

Added

• Output the cf --version in the logs.
• create-service-broker command - Create/Update a service broker
• delete-service-broker command - Delete a service broker
• enable-service-access command - Enable access to a service or service plan for one or all orgs
• disable-service-access command - Disable access to a service or service plan for one or all orgs

Changed

• Updated cf cli to version 6.32.0. This paves the way for introducing some of the new v3 commands (although we haven't implemented any yet...)
• Log messages have been cleaned up and now use color coded severity levels (in green and red, respectively): [INFO], [ERROR]

v2.2.1

2.2.1 - 2017-10-04

Added

• Change log.
• Generate release notes from change log for github release.

Changed

• create-user-provided-service command no longer fails if there is an existing user provided service by the same name. NOTE: This is a departure from how the normal cf cups ... command works as it normally fails with an error:

  Server error, status code: 400, error code: 60002, message: The service instance name is taken: my-cups-service

v2.2.0

learned to create-user-provided-service