splunk / splunk/vault-plugin-secrets-gitlab
Support to use rotate api to rotate token if a project access token already exists
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 62
- Forks
- 12
- Avg merge
- 35m
- Merged PRs (30d)
- 1
Description
When using create api, every api call will create a new token with a new bot user. While using rotate api, the same bot user (user_id) will be kept which will benefit branch protection configuration if a bot user is allowed to push to some protected branch, eg. release branch.
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
Start by inspecting the implementation of the GitLab project access token create API and how existing tokens are identified. Compare that flow with the linked rotate API documentation; done means an existing token can be rotated while preserving its bot user, including behavior relevant to protected branches.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- gitlab, go
- Domain
- api, authentication
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100