v3.0.0

What's Changed

• The base image switched from python to the official azure-cli image, improving runtime performance by eliminating the need to install azure-cli every run.

Breaking Changes

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: v2.0.1...v3.0.0

v2.0.1

What's Changed

• Lock Python version to 3.10 to avoid issue with Azure CLI missing support for Python 3.11 by @parse in #28

New Contributors

• @parse made their first contribution in #28

Full Changelog: v2.0.0...v2.0.1

v2.0.0

PLEASE READ ME BEFORE UPGRADING

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.

Changes since v1.2.0

Configurable Azure CLI Version

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'

Overwrite flag

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 required

As part of the recent parser changes, the sync flag is no longer a required flag. The default value is false.

v1.2.0

azure-blob-storage-upload v1.2.0

v1.1.1

azure-blob-storage-upload v1.1.1

v1.1.0

azure-blob-storage-upload v1.1.0

v1.0.0

Update README.md

v0.1.0: initial commit

Signed-off-by: Matthew Fisher <[email protected]>