feat: add support for DefaultAzureCredential authentication mechanism #681
Conversation
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
dosubot
bot
added
size:L
armru
changed the title
GabriFedi97
reviewed
Dec 22, 2025
Contributor
|
@armru the manifests generation seems to be missing in this PR |
GabriFedi97
added a commit
to GabriFedi97/plugin-barman-cloud
that referenced
this pull request
Dec 23, 2025
…g#681) Make explicit in docs that the inheritFromAzureAD option enables the usage of Azure Managed Identity authentication mechanism. Signed-off-by: Gabriele Fedi <[email protected]>
GabriFedi97
added a commit
to GabriFedi97/plugin-barman-cloud
that referenced
this pull request
Dec 23, 2025
…g#681) Make explicit in docs that the inheritFromAzureAD option enables the usage of Azure Managed Identity authentication mechanism. Signed-off-by: Gabriele Fedi <[email protected]>
mnencia
pushed a commit
that referenced
this pull request
Dec 29, 2025
Make explicit in docs that the inheritFromAzureAD option enables the usage of Azure Managed Identity authentication mechanism. Signed-off-by: Gabriele Fedi <[email protected]>
mnencia
pushed a commit
that referenced
this pull request
Dec 29, 2025
Make explicit in docs that the inheritFromAzureAD option enables the usage of Azure Managed Identity authentication mechanism. Signed-off-by: Gabriele Fedi <[email protected]>
mnencia
force-pushed
the
dev/default-azure-cred
branch
from
3b36d4d to
b46a7cf
Compare
GabriFedi97
approved these changes
Dec 29, 2025
mnencia
pushed a commit
that referenced
this pull request
Dec 29, 2025
Make explicit in docs that the inheritFromAzureAD option enables the usage of Azure Managed Identity authentication mechanism. Signed-off-by: Gabriele Fedi <[email protected]>
mnencia
force-pushed
the
dev/default-azure-cred
branch
from
b46a7cf to
f273895
Compare
mnencia
previously approved these changes
Dec 29, 2025
This commit adds support for the DefaultAzureCredential authentication mechanism in Azure Blob Storage. Users can now use the `useDefaultAzureCredentials` option to enable Azure's default credential chain, which automatically discovers and uses available credentials in the following order Signed-off-by: Armando Ruocco <[email protected]>
Signed-off-by: Armando Ruocco <[email protected]>
Make explicit in docs that the inheritFromAzureAD option enables the usage of Azure Managed Identity authentication mechanism. Signed-off-by: Gabriele Fedi <[email protected]>
Signed-off-by: Marco Nenciarini <[email protected]>
Signed-off-by: Marco Nenciarini <[email protected]>
mnencia
force-pushed
the
dev/default-azure-cred
branch
from
ef0871d to
631ff20
Compare
mnencia
approved these changes
Dec 29, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 commit adds support for the DefaultAzureCredential authentication mechanism in Azure Blob Storage. Users can now use the
useDefaultAzureCredentialsoption to enable Azure's default credential chain, which automatically discovers and uses available credentials in the following orderThis is particularly useful when running on Azure Kubernetes Service (AKS) with
Workload Identity, eliminating the need to explicitly store credentials in
Kubernetes Secrets.