documentation for group/project level secret mount installment

未关闭
#24 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
文档
描述清晰度
基本清楚
活跃度
停滞
技术栈
gitlab, go

调研方向

No files or tests are named. Start by locating the secret-mount implementation and its existing authorization tests, then exercise group-maintainer and project-maintainer tokens. Done means the supported scopes are tested and documented, including access to projects within the group and denial for projects outside it.

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

描述

documentation help wanted

I've tested at instance level where an admin token is used. This allows to create project access token for any projects.

For SaaS or limited use, this secret mount should work for

  • group maintainer or higher access token for projects under a group
  • project maintainer or higher access token for a project

We'll need to test and document that situation where group maintainer token is used. it should be able to create project access token for projects under the group. it shouldn't be able to create project access token for a project outside of the group where the token configured in plugin doesn't have access to.

主要语言
Go
星标
63
派生
12
PR 合并指标
30 天内没有已合并 PR

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

splunk/vault-plugin-secrets-gitlab 的其他 Issue

查看 splunk/vault-plugin-secrets-gitlab 的全部 Issue

相似的 Issue

更多 Go Issue

把新 issue 发到你的邮箱

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