Support to use rotate api to rotate token if a project access token already exists

Open
#117 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
gitlab, go

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.

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.

Dominant language
Go
Stars
63
Forks
12
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from splunk/vault-plugin-secrets-gitlab

All issues in splunk/vault-plugin-secrets-gitlab

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.