secrets-management

Manage and rotate secrets in CI/CD pipelines with Vault or AWS Secrets Manager.

38.6k|4.1k|Updated Jul 24, 2025

Search Tags:#ci/cd #security #secrets management #credentials #vault #aws secrets manager

Ready to run

npx skills add https://github.com/wshobson/agents --skill secrets-management-wshobson

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/wshobson/agents/tree/main/plugins/cicd-automation/skills/secrets-management
Command: npx skills add https://github.com/wshobson/agents --skill secrets-management-wshobson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill addresses the critical need to manage sensitive credentials and secrets securely within CI/CD pipelines, preventing hardcoding and reducing the risk of exposure.

Core Features & Use Cases

Centralized Secrets Management: Integrates with tools like HashiCorp Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager.
Secure Credential Handling: Provides examples for securely retrieving and using secrets in GitHub Actions and GitLab CI.
Use Case: Securely deploy your application by fetching API keys and database passwords from a secrets manager instead of embedding them directly in your pipeline configuration.

Quick Start

Use the secrets-management skill to store a new API key in AWS Secrets Manager.

Frequently Asked Questions about secrets-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I fetch database passwords from AWS Secrets Manager in a GitHub Actions CI/CD pipeline?▼

To fetch database passwords in a GitHub Actions CI/CD pipeline, retrieve credentials dynamically from AWS Secrets Manager instead of embedding them in configuration files. This secures sensitive data by integrating external secret stores with native platform variable management.

What is the best way to manage CI/CD secrets across HashiCorp Vault and AWS Secrets Manager?▼

The best way to manage CI/CD secrets across HashiCorp Vault and AWS Secrets Manager is using centralized secrets management. This approach standardizes secure credential handling, applies external secret stores, and prevents hardcoding sensitive credentials in pipeline configurations.

Why should I avoid hardcoding API keys in GitLab CI environments?▼

You should avoid hardcoding API keys in GitLab CI environments because it risks exposing sensitive credentials. Fetching secrets dynamically from external stores like HashiCorp Vault or AWS Secrets Manager prevents hardcoded credentials and secures CI/CD environments.

Can I rotate secrets securely within CI/CD pipelines using HashiCorp Vault?▼

Yes, you can rotate secrets securely within CI/CD pipelines using HashiCorp Vault. This secrets management process handles sensitive credential rotation and integrates with external secret stores to maintain secure CI/CD environments without downtime.

Does this approach support integrating native GitHub Actions variables with external secret stores?▼

Yes, this secrets management approach supports integrating native GitHub Actions variables with external secret stores. It bridges platform variable management with centralized tools like AWS Secrets Manager and HashiCorp Vault for secure credential handling.