secrets-management

Centralize and rotate credentials for CI/CD pipelines across Vault and AWS Secrets Manager.

Updated Aug 30, 2025
One-click install
npx skills add https://github.com/vonomarap/kanokna --skill secrets-management-vonomarap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secrets-management
Source: https://github.com/vonomarap/kanokna/tree/main/.agents/skills/secrets-management
Command: npx skills add https://github.com/vonomarap/kanokna --skill secrets-management-vonomarap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Organizations struggle to securely manage credentials and rotate secrets across CI/CD pipelines, deployments, and cloud services, avoiding hard-coded keys and leaked tokens.

Core Features & Use Cases

  • Centralized secret storage and rotation across Vault, AWS Secrets Manager, and cloud-native stores
  • Fine-grained access control, auditing, and least-privilege workflows
  • GitHub Actions and GitLab CI integrations for secure deployment processes
  • Real-world use case: rotate database passwords and API keys without downtime

Quick Start

Configure a secret store for your CI/CD environment and reference it in your pipelines.

Frequently Asked Questions about secrets-management

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

FAQPage Schema
How do I manage secrets in GitHub Actions without hard-coding keys?

Manage secrets in GitHub Actions by centralizing credentials in Vault or AWS Secrets Manager and referencing them directly in your pipelines. This avoids hard-coded keys and enables secure, audited deployments.

What's the best way to rotate database passwords in CI/CD pipelines?

Rotate database passwords in CI/CD pipelines by integrating a centralized secret store to update credentials dynamically. This enables zero-downtime password rotation and API key updates without interrupting deployment workflows.

Does Vault work with GitLab CI for secure credential storage?

Vault works with GitLab CI to provide secure credential storage and fine-grained access control. It integrates directly into deployment pipelines to enforce least-privilege workflows and maintain auditability.

How do I enforce least-privilege access for secrets in Kubernetes deployments?

Enforce least-privilege access for secrets in Kubernetes by applying fine-grained access controls through a centralized manager. This restricts credential visibility to authorized services and logs all access attempts.

Can I use AWS Secrets Manager to centralize credentials across multiple cloud services?

AWS Secrets Manager centralizes credentials across multiple cloud services and CI/CD pipelines. It supports secure storage, automated rotation, and integrates with native cloud environments to protect deployment workflows.

Why do I need a secrets manager instead of using native CI/CD environment variables?

A secrets manager provides centralized rotation, least-privilege access control, and auditing that native CI/CD environment variables lack. It prevents leaked tokens and secures credentials across complex deployment pipelines.