Releases: nulldriver/cf-cli-resource
Releases · nulldriver/cf-cli-resource
v2.20.0
2.20.0 - 2020-07-09
Changed
push
command now supports the strategy
option when combined with using cf_cli_version: 7
Packaged Dependencies
v2.19.1
2.19.1 - 2020-07-08
Fixed
run-task
, add-network-policy
, remove-network-policy
, create-route
, create-buildpack
commands now work using cf_cli_version: 7
Packaged Dependencies
v2.19.0
2.19.0 - 2020-06-29
Added
- Introduced experimental support for
cf7
cli! This is enabled by configuring cf_cli_version: 7
globally on the resource source configuration.
Fixed
- The
environment_variables
handling introduced for the push
command introduced in v2.18.1 wasn't properly placing the env
node at the application level (it was placing it at the deprecated global level) with only one application in the manifest but no app_name
declared. This has been corrected and the test case updated to properly check for this condition.
Changed
- Major changes to
zero-downtime-push
command!!! The command has been refactored to no longer depend on the deprecated autopilot plugin and now provides a "hand crafted" zero downtime push experience and supports vars
and vars_files
arguments, thanks to a PR by shyamz-22. It also now supports docker_image
, show_app_log
on failed pushes, the no_start
flag, and staging_timeout
and startup_timeout
params. The zero-downtime-push
integration tests have also received a major overhaul to ensure a seamless transition.
push
command now supports the show_app_log
option to output app logs after a failed push (use with app_name
option)
bind-route-service
command now supports the path
option (used in combination with hostname
and domain
to specify the route to bind), thanks to a PR by shyamz-22!
- We use Alpine Linux as the base image for
cf-cli-resource
when it runs inside of Concourse. With Alipine v3.8
headed to End of Support on 2020-05-01 it was time to update to Alpine v3.11
which should keep us up-to-date till 2021-11-01.
- Removed
autopilot
cf cli plugin (see changes to zero-downtime-push
command)
- Updated
yq
cli to version 3.2.1
Packaged Dependencies
v2.18.1
2.18.1 - 2020-03-31
Fixed
- When
push
ing an app with environment_variables
without a manifest, we create a temporary manifest that contains the env:
attribute. This was being done at the global attribute level, resulting in cli deprecation warnings: Deprecation warning: Specifying app manifest attributes at the top level is deprecated. Found: env.
This is now fixed by creating a manifest with the env:
attribute properly set at the application level. No more deprecation warnings (thanks to a PR by @destasys)
Changed
- Replaced all direct calls to
cf
cli with a cf::cf
wrapper function. This is the first pass at being able to specify which version of the cf cli you want to use (in preparation for testing the cf7 version of the cli)
Packaged Dependencies
v2.18.0
2.18.0 - 2020-03-24
Changed
push
command now supports setting environment_variables
(thanks to a PR by @lbenedix)
set-env
command now supports setting multiple environment_variables
. This deprecates the original env_var_name
and env_var_value
params.
- Updated
yq
cli to version 3.2.1
Packaged Dependencies
v2.17.0
2.17.0 - 2020-02-27
This release introduces some major changes to the project structure. The cf-cli-resource
has come a long way since its humble beginnings in early 2017 and it was about time to do some spring cleaning. Thankfully our test cases have ensured that we were able to make these changes with confidence. Check out the rest of the release notes for all the details.
Added
Fixed
- The
create-users-from-file
command now logs a warning (instead of an error) if the Username
value is not set (since that's not a failing condition).
Changed
- Updated to cf cli v6.49.0
add-network-policy
and remove-network-policy
commands now support the destination_org
and destination_space
params for targeting a destination app in a different org and/or space.
create-service
command now supports the broker
param to disambiguate if you have two services with the same name.
- Renamed
assets
folder to resource
. This makes it simpler to locate scripts whether we are running tests locally or in a Docker image.
- Renamed
cf_*
functions to cf::*
to follow the "package" naming convention.
- Moved all supporting function libraries to respective
resource/lib
and itest/lib
folders.
- Refactored
resource/out
to invoke resource commands from separate files (see resource/commands
folder). This should make adding new commands much cleaner and easier.
Packaged Dependencies
v2.16.0
2.16.0 - 2020-01-27
Added
cf_home
param for supplying a CF_HOME
folder which (in this initial release) allows for passing on a previously configured .cf/config.json
file for CF API authentication (thanks to a PR by @lbenedix)
Changed
push
command now supports the domain
param, thanks to a PR by @vixus0
Packaged Dependencies
v2.15.2
2.15.2 - 2019-12-04
Fixed
create-buildpack
now supports globbing for path
param.
Added
- Validation tests for validating error exit codes
- logging library
Changed
Packaged Dependencies
v2.15.1
2.15.1 - 2019-07-06
Fixed
update-buildpack
now supports globbing for path
param.
Packaged Dependencies
v2.15.0
2.15.0 - 2019-06-27
Fixed
enable-service-access
and disable-service-access
used a very mis-leading service_broker
param to represent the name of the marketplace service to enable/disable. So, the service_broker
param is now deprecated and is superseded by the new properly named service
param.
Added
create-buildpack
- Create a buildpack
update-buildpack
- Update a buildpack
delete-buildpack
- Delete a buildpack
Changed
- Updated to cf cli v6.45.0
- Refactored
cf_functions.sh
to utilize the new cf curl --fail
option for better error api error handling
- Quite a bit of test code cleanup
Packaged Dependencies