splunk / splunk/vault-plugin-secrets-gitlab
documentation for group/project level secret mount installment
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 62
- Forks
- 12
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
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.
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.
Research direction
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.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- authorization, documentation, security
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100