Skip to content

Azure Blobs Content Uploader is designed as a github action, to help developers upload their build artifacts to multiple az-storage accounts, taking into account the absolute paths / relative paths / recursive structure from your file system. It's especially meant to help with SPA developers (ex: artifacts of create-react-app) to quickly upload …

armhil/azure-blobs-content-uploader

Use this GitHub action with your project
Add this Action to an existing workflow or create a new one
View on Marketplace

Repository files navigation

Azure blobs - content uploader

No real build - some simple tests & executing the action itself

Azure Blobs Content Uploader is designed as a github action, to help developers upload their build artifacts to multiple az-storage accounts, taking into account the absolute paths / relative paths / recursive structure from your file system.

It's especially meant to help with SPA developers (ex: artifacts of create-react-app) to quickly upload artifacts to a lot of storage accounts for redundancy and performance.

Configuration details

To configure this job, you'll need a few things.

Your local files

You should decide which directory to upload and to where on the storage accounts. This information is passed as parameters to the *.yaml file. See the directoriesToUpload parameter, which supports passing multiple directories. Note that while you can upload multiple directories, they will be uploaded to the same location.

      - name: Upload Static Content
        uses: armhil/azure-blobs-content-uploader@1.0.0
        with:
          azureBlobConfiguration: ${{ secrets.AZ_BLOB_CONFIGURATION }} # could be any secret that you have, see below for the format
          directoriesToUpload: '[{"directoryToUpload": "test/integrationtest-directory", "shouldRecurse": "true", "baseContainerPath": "somePath" }]'

Azure blob details

The content uploader supports uploading to multiple storage accounts, so you're going to need the connection strings of all the blob storages that you want to upload the files to.

      - name: Upload Static Content
        uses: armhil/azure-blobs-content-uploader@1.0.0
        with:
          azureBlobConfiguration: ${{ secrets.AZ_BLOB_CONFIGURATION }} # could be any secret that you have, see below for the format
          directoriesToUpload: '[{"directoryToUpload": "test/integrationtest-directory", "shouldRecurse": "true", "baseContainerPath": "somePath" }]'

You should use the below format for the azureBlobConfiguration parameter and this value should come from the secrets. azureBlobConfiguration parameter is expected to contain the connection strings to blob storage accounts, so it's incredibly important to store it in github repository secrets, rather than some plaintext mechanism.

// Secret value schema
[
  {
    "connectionString": string, // Az Blobs connection string
    "container": string, // Container to upload the files to
  },
]

// Example secret value
[{"connectionString": "DefaultEndpointsProtocol=https;AccountName=azblobuploadtest;AccountKey=someAccountKeyNotReal;EndpointSuffix=core.windows.net
", "container": "$web"}]

Hint: If you're uploading some static content for web-apps (like artifacts of create-react-app) - you can use the $web container from Azure Blob Storage.

About

Azure Blobs Content Uploader is designed as a github action, to help developers upload their build artifacts to multiple az-storage accounts, taking into account the absolute paths / relative paths / recursive structure from your file system. It's especially meant to help with SPA developers (ex: artifacts of create-react-app) to quickly upload …

Topics

Resources

Stars

Watchers

Forks

Packages

No packages published