feat(azblob): add azure blob storage provider - #257
Open
Jonas-Beck wants to merge 6 commits into
Open
Conversation
Signed-off-by: Jonas Beck <dev@jonasbeck.dk>
Signed-off-by: Jonas Beck <dev@jonasbeck.dk>
Signed-off-by: Jonas Beck <dev@jonasbeck.dk>
Signed-off-by: Jonas Beck <dev@jonasbeck.dk>
Signed-off-by: Jonas Beck <dev@jonasbeck.dk>
Jonas-Beck
commented
Aug 4, 2026
| { | ||
| 'STORAGE_DRIVER': type.unit('azblob'), | ||
| 'STORAGE_AZBLOB_ACCOUNT': 'string', | ||
| 'STORAGE_AZBLOB_CONTAINER': 'string', |
Author
There was a problem hiding this comment.
I was initially considering if STORAGE_AZBLOB_CONTAINER should be optional and default to e.g gh-actions-cache.
Currently it's using createIfNotExists() when creating the container client, so that there would always be a container available.
Jonas-Beck
marked this pull request as draft
August 4, 2026 07:01
Signed-off-by: Jonas Beck <dev@jonasbeck.dk>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds support for using azure blob storage as a storage provider
This has support for authentication using connection string and also authentication using the
@azure/identitypackage DefaultAzureCredentialsPart of #256
helmchart has also been updated to support configuring the new env variables for azblob storage driver, currently any authentication related configuration when using DefaultAzureCredentials are not exposed in the
storage.azblobvalues.This means that for anyone using workload identity to authenticate, annotations should be added to the ServiceAccount using
serviceAccount.annotationsand labels on the pods should added usingpodLabels