How to use DefaultAzureCredential in plugin for backup on azure blob storage
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- azure, go, kubernetes
- Domain
- cloud, documentation
Research direction
Review PR #681 and the useDefaultAzureCredentials option described in the issue, then identify the documentation entry point for Azure Blob Storage authentication. Document the required configuration and clearly distinguish managed identity from workload identity, with examples covering the credential options mentioned; done means a user can choose and configure an authentication method without follow-up questions.
Written by the indexing model from the issue text.
Description
Hi @dosu, as per below PR feat: add support for DefaultAzureCredential authentication mechanism #681
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
Environment Variables (Service Principal)
Managed Identity
Azure CLI
Azure PowerShell
This is particularly useful when running on Azure Kubernetes Service (AKS) with
Workload Identity, eliminating the need to explicitly store credentials in
Kubernetes Secrets.
This will merge in 0.11.0 version.
But can you please tell me if i want to use this what i need to configure . I don’t know ant to use credentials or sas token directly. So will i required to use workload identity or managed identity. Could you please tell what is difference between managed identity and workload identity?
- Dominant language
- Go
- Stars
- 192
- Forks
- 75
- Avg merge
- 1d 7h
- Merged PRs (30d)
- 17
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from cloudnative-pg/plugin-barman-cloud
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
cloudnative-pg/plugin-barman-cloud#1104 · 4 reactions ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
Difficulty 3/5 1-2 days Newbie friendliness 65/100
cloudnative-pg/plugin-barman-cloud#1113 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 15/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in cloudnative-pg/plugin-barman-cloud
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug group: validation priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
codecheckers/chekhov#51 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100