secret-adapters

Integrate HashiCorp Vault secret storage with NestJS projects.

6|3|Updated Apr 8, 2022
One-click install
npx skills add https://github.com/Rytass/Utils --skill secret-adapters
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: secret-adapters
Source: https://github.com/Rytass/Utils/tree/main/.claude/skills/secret-adapters
Command: npx skills add https://github.com/Rytass/Utils --skill secret-adapters

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a unified secret-management interface designed to securely store, retrieve, rotate, and audit credentials across services, with HashiCorp Vault as a primary backend.

Core Features & Use Cases

  • Unified SecretManager abstraction: defines a common API for secret storage, retrieval, and deletion across adapters.
  • Vault integration & offline/online modes: supports deterministic local caching with online sync and automatic token renewal.
  • NestJS integration: includes NestJS-friendly module and service patterns for easy DI and configuration.
  • Real-world use cases: store DB credentials, API keys, and configuration values, and switch between vault-backed and env-backups when Vault is unavailable.

Quick Start

Install the vault adapters and initialize a VaultSecret with a path and host to begin reading secrets.

Frequently Asked Questions about secret-adapters

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

FAQPage Schema
How do I manage HashiCorp Vault secrets in a NestJS application?

HashiCorp Vault secret management in NestJS uses a unified SecretManager abstraction with typed contracts like VaultSecretOptions, providing dependency injection patterns to securely store and retrieve credentials with automatic token renewal.

What happens to secret retrieval when HashiCorp Vault is offline?

When HashiCorp Vault is unavailable, secret retrieval switches to environment-based fallback mechanisms using deterministic local caching, ensuring services maintain offline operation while waiting for online sync to resume.

Can I use environment variables as a fallback for Vault credentials?

Yes, environment variables serve as fallback credentials through environment-based fallback mechanisms, allowing your application to switch between vault-backed storage and local env-backups when HashiCorp Vault is unavailable.

How does automatic token renewal work with HashiCorp Vault integrations?

Automatic token renewal with HashiCorp Vault integrations continuously refreshes authentication tokens during online sync operations, ensuring uninterrupted secure access to stored credentials without manual intervention or session expiration.

Does this secret management interface support typed contracts for different operation modes?

Yes, the secret management interface defines typed contracts like VaultSecretOptions and VaultSecretOnlineOptions, enforcing mode-dependent return types for get, set, and delete operations across online and offline adapters.

What is the best way to centralize database credentials and API keys across multiple services?

Centralizing database credentials and API keys across services is best achieved through a unified secret-management interface with HashiCorp Vault as the primary backend, providing a common API for secure storage, retrieval, rotation, and auditing.