Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Support Azure workload identity for Azure Blob object storage

未关闭
#1,697 0 条评论 2 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
azure, go, kubernetes
领域
backend, cloud

调研方向

The account-key requirement lives in secret.go, so start there to see where the Azure Blob key is read and how it is wired into the storage settings. Check the settings.py template that the operator renders, plus the pod_labels and sa_annotations options, to see where a token_credential would go. Done means a workload-identity configuration works without an account key, while the key path still works and the azure-identity package is present in the shipped images.

由索引模型根据 Issue 内容生成。

描述

Feature Triage-Needed

Is your feature request related to a problem? Please describe.
Azure Blob storage requires an account key (secret.go), so there's no way to use workload identity and avoid long-lived keys.

Describe the solution you'd like
Support workload identity. django-storages already supports token_credential (e.g. DefaultAzureCredential()), and the pod labels / SA annotations needed can already be set via pod_labels and sa_annotations. So it'd be:

  • make the account key optional
  • set token_credential in settings.py when no key is given
  • ship azure-identity in the images

Describe alternatives you've considered
Account key, which works but is a long-lived secret.

Additional context
Happy to help test or send a PR.

主要语言
Go
星标
88
派生
69
平均合并
3 天 3 小时
30 天内合并 PR
1

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

pulp/pulp-operator 的其他 Issue

查看 pulp/pulp-operator 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。