actions-marketplace-validations/azure-blob-copy-action

Github action to allow copying to and from Azure Blob Storage

Trust Signals

workflow.ymlSHA-pinned

uses: actions-marketplace-validations/ulaval_azure-blob-copy-action@75fa2731bf148218f074994b98c87fb432cdfee1 # no releases — HEAD as of 2026-07-10

tags can be moved; commit SHAs can't. why a SHA?

name	description	required	default
action	Either upload or download	yes	upload
connection_string	Azure Blob Storage connection string	yes	—
container_name	Azure Blob Storage container name	yes	—
blob_directory	Directory in Azure to copy from or to	no	—
local_directory	Local directory to copy from or to; this can either be an absolute path or a relative path	yes	—
http_headers	YAML document that allows setting http headers on blobs when uploading to Azure. The supported headers are: Cache-Control, Content-Type, Content-Encoding, Content-Language, Content-Disposition (case sensitive). The yaml document must resolve to an array where each element has a <glob> and <headers> values. If a file is matched at multiple times, the first match wins. By default, the Content-Type is discovered using mime-db mostly using UTF-8 charset. For example: http_headers: \| - glob: "*/.js" headers: Cache-Control: public, max-age=604800, immutable Content-Type: application/javascript Content-Encoding: gzip Content-Language: fr-CA Content-Disposition: inline - glob: "*/": headers: Cache-Control: public, no-cache	no	—

no outputs