secrets-management

Centralize secrets management across Vault, AWS, Azure, and Google for CI/CD pipelines.

3|1|Updated Feb 3, 2026

Search Tags:#secrets #vault #github-actions #ci-cd #aws-secrets-manager #secret-rotation #kubernetes-external-secrets

Ready to run

npx skills add https://github.com/duanbiao2000/obsidianDoc26 --skill secrets-management-duanbiao2000

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

The secure handling of credentials in CI/CD pipelines without hardcoding secrets, enabling rotation and least-privilege access.

Core Features & Use Cases

Centralized secrets management with Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager.
Dynamic secrets generation, automatic rotation, and audit logging.
Seamless integration with GitHub Actions, GitLab CI, and Kubernetes External Secrets, plus guidance on best practices.

Quick Start

Configure Vault or AWS Secrets Manager in your CI/CD workflow and reference secrets in your pipelines to enable automatic rotation and access control.

Frequently Asked Questions about secrets-management

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

FAQPage Schema

How do I manage CI/CD secrets across multiple cloud providers without hardcoding credentials?▼

Managing CI/CD secrets without hardcoding requires centralizing credentials across Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager. This enables dynamic secrets generation, automatic rotation, and audit logging while maintaining least-privilege access in your pipelines.

How do I integrate AWS Secrets Manager with GitHub Actions workflows?▼

Integrating AWS Secrets Manager with GitHub Actions workflows involves configuring the secrets manager in your CI/CD pipeline and securely retrieving credentials at runtime. This approach provisions, rotates, and audits secrets dynamically without exposing them in your repository.

Does this approach to secrets management work with Kubernetes External Secrets?▼

Yes, centralized secrets management integrates seamlessly with Kubernetes External Secrets to provision and retrieve credentials. It supports dynamic secrets generation and automatic rotation, ensuring secure credential handling across your Kubernetes clusters and CI/CD workflows.

What's the best way to implement automatic secret rotation in CI/CD pipelines?▼

The best way to implement automatic secret rotation in CI/CD pipelines is by using centralized secrets managers like Vault or AWS Secrets Manager. They handle dynamic secrets generation, automatic rotation, and audit logging, enforcing least-privilege access without hardcoded credentials.

When do I need centralized secrets management for my deployment workflows?▼

You need centralized secrets management for deployment workflows when handling credentials securely without hardcoding. It is essential when you require dynamic secrets generation, automatic rotation, audit logging, and least-privilege access across multiple CI/CD pipelines and cloud platforms.

Can I use Vault to provision and audit credentials across GitLab CI pipelines?▼

Yes, you can use Vault to provision, retrieve, rotate, and audit credentials in GitLab CI pipelines. Centralized secrets management applies across Vault, AWS Secrets Manager, Azure Key Vault, and Google Secret Manager to secure your CI/CD workflows.