python
to the official azure-cli
image, improving runtime performance by eliminating the need to install azure-cli
every run.This change means that the Azure CLI version is no longer configurable through the cli_version
field. If this is an issue for you, please file a ticket.
Full Changelog: https://github.com/bacongobbler/azure-blob-storage-upload/compare/v2.0.1...v3.0.0
Published by bacongobbler almost 2 years ago
Full Changelog: https://github.com/bacongobbler/azure-blob-storage-upload/compare/v2.0.0...v2.0.1
This is a major release, breaking compatibility with older workflows. Due to a bug in with Github Action's handling of boolean values, the action now expects a string value as input.
When upgrading, please make sure to change any workflows from this:
sync: true
To this:
sync: 'true'
This forces Github's YAML parser to treat this value as a string rather than a boolean.
Users can now specify which version of the Azure CLI they wish to use via the cli_version
flag:
- uses: bacongobbler/[email protected]
with:
cli_version: 2.33.0
source_dir: _dist
container_name: www
connection_string: ${{ secrets.ConnectionString }}
extra_args: '--pattern *.tar.gz'
Azure CLI >= v2.34.0 now requires the user to specify the --overwrite true
flag if they want to overwrite assets in the destination container. Many workflows relied on this default behaviour to upload nightly releases of their application. An overwrite
flag was introduced in 2.0.0 to make this simpler:
- uses: bacongobbler/[email protected]
with:
source_dir: _dist
container_name: www
connection_string: ${{ secrets.ConnectionString }}
extra_args: '--pattern *.tar.gz'
overwrite: 'true'
the default is false, preventing the action from overwriting existing blobs in the destination container.
sync
flag no longer requiredAs part of the recent parser changes, the sync
flag is no longer a required flag. The default value is false.
Published by bacongobbler over 4 years ago