sameersbn / sameersbn/docker-gitlab
How to update GITLAB_SECRETS_DB_KEY_BASE?
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 8.1k
- Forks
- 2.1k
- Avg merge
- 17h 47m
- Merged PRs (30d)
- 7
Description
Currently my GITLAB_SECRETS_DB_KEY_BASE is less than 32 characters.
After increasing the length I've got 500 error on all CI related pages.
Are there any ways to do it without losing secrets?
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 with the GITLAB_SECRETS_DB_KEY_BASE setting and the CI-related pages described in the report. Determine the supported key-update procedure and verify that existing secrets remain usable without producing 500 errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, gitlab
- Domain
- ci-cd, security
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100