GitLab Secrets Manager: Govern secrets like your code
From the source: GitLab Blog
Credentials often start in an engineer's local dev environments, then get copied into unscoped CI/CD variables to keep pipelines running. Stored there as a raw value rather than a reference to a scoped secret, a signing key reaches every job in the pipeline, compromised or not. Standing up a standalone vault narrows that exposure but requires mirroring every change to project membership,…
Read the full story on GitLab BlogAsk the square
The story is what was announced. If it raises a question for your team, ask the people who run this technology day to day. Your post links back to this story, so the next reader finds it too.
Recent threads in DevOps & Platform Engineering
How are you measuring platform engineering success?
DORA metrics, developer surveys, time-to-first-deploy, cost per service? What convinced leadership the platform team is worth it?
What is in your internal developer platform, and what did developers actually adopt?
Golden paths, templates, portals, self-service environments. Which parts get used every day and which became shelfware?
Something wrong or out of date? Suggest a correction. We reply within 5 business days.
More from GitLab
Recent updates from GitLab, so you can tell whether this is a one-off or part of a pattern.
More in DevOps & Platform Engineering
What other companies in DevOps & Platform Engineering are doing. The category page shows who’s active, side by side.
