expires_at is required by gitlab ~16.3
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 38/100
Research direction
Start with the README example for vault write gitlab/token and trace the implementation of the GitLab project access-token request at POST /projects/1/access_tokens. Confirm how the request handles GitLab's required expires_at field, then reproduce the command against a GitLab 16.3-or-newer instance; done means token creation no longer fails because expires_at is missing.
Written by the indexing model from the issue text.
Description
Hi, I'm testing this plugin which would be very useful for an instance-scoped external CI pipeline. But when I tried the examples in the README this error appears:
vault write gitlab/token id=1 name=ci-token scopes=api,write_repository
Error writing data to gitlab/token: Error making API request.
URL: PUT https://<vault host>/v1/gitlab/token
Code: 400. Errors:
* Failed to create a token - POST https://<gitlab host>/api/v4/projects/1/access_tokens: 400 {error: expires_at is missing}
Apparently Gitlab is changing the policy wrt expires_at, and now it's being required.
https://gitlab.com/gitlab-org/terraform-provider-gitlab/-/issues/4133
Could you please include this in the requests?
- Dominant language
- Go
- Stars
- 63
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from splunk/vault-plugin-secrets-gitlab
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Templated policiesOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
splunk/vault-plugin-secrets-gitlab#117 · 1 reaction ·
-
support for group level access tokenPossibly taken @M0roSan claimed this 1701 days ago. Openenhancement
Difficulty 3/5 1-2 days Newbie friendliness 35/100
splunk/vault-plugin-secrets-gitlab#36 · 6 comments · 1 reaction ·
-
documentation help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
All issues in splunk/vault-plugin-secrets-gitlab
Similar issues
-
bug needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
ClickHouse/clickhouse-go#2124 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
evener-transcript-v2-upgrade tool still scans transcript files through bufio's 4 KiB default bufferOpen
Difficulty 1/5 Under an hour Newbie friendliness 78/100
prime-radiant-inc/evener#6370 ·
Maintainers usually reply within 1 day
-
ManageSieve proxy: a backend's NO/BYE greeting is skipped as a capability line and reported as EOFOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Mend: dependency security vulnerability
Difficulty 2/5 1-3 hours Newbie friendliness 65/100