How we’ll simplify Vault access for GitLab CI/CD users
Feb 13, 2020Valerie Silverthorne

Summary
This post details an MVC approach to integrate HashiCorp Vault with GitLab CI/CD. The proposed solution involves instructing GitLab Runner, via Rails, to fetch secrets from Vault. This simplifies access to stored variables by leveraging Vault as a dedicated secrets store and implementing rotation and access control for enhanced security. The approach prioritizes a simpler runner-based solution over a more complex Rails integration with Vault.
More from the GitLab Secrets Manager trail
- GitLab Secrets Manager adds ESO, Terraform, API support
- Manage CI/CD credentials with GitLab Secrets Manager
- A leaked personal access token shouldn't expose every project its owner can reach. Fine-grained PATs scope each token’s permissions to the job.
- Solving complex challenges with GitLab Duo Workflow
- How to scan a full commit history to detect sensitive secrets