vela-secrets

Manage Vela CI/CD secret scopes, injection, and access controls.

Updated Mar 7, 2026

Search Tags:#ci/cd #security #configuration #pipeline #secrets #vela

Ready to run

npx skills add https://github.com/ryanmr/vela-skills --skill vela-secrets

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: vela-secrets
Source: https://github.com/ryanmr/vela-skills/tree/main/.agents/skills/vela-secrets
Command: npx skills add https://github.com/ryanmr/vela-skills --skill vela-secrets

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps users understand and manage secrets within the Vela CI/CD platform, ensuring sensitive information is handled securely and effectively.

Core Features & Use Cases

Secret Scopes: Explains and demonstrates repo, org, and shared secret scopes.
Declaration & Injection: Shows how to declare secrets in pipeline YAML and inject them into steps.
Security Features: Covers pull request restrictions, command/substitution allow settings, and image restrictions.
Use Case: Securely inject API keys into your build process without exposing them in logs or pipeline definitions.

Quick Start

Use the vela-secrets skill to understand how to declare and inject the 'docker_password' secret into a build step.

Frequently Asked Questions about vela-secrets

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

FAQPage Schema

How do I inject secrets into a Vela CI/CD pipeline step?▼

To inject secrets into a Vela CI/CD pipeline, you declare them in your pipeline YAML and reference them within build steps. This ensures sensitive data like API keys are securely passed without appearing in logs.

What is the difference between repo, org, and shared secret scopes in Vela?▼

Vela secret scopes control access levels: repo secrets are isolated to a single repository, org secrets are available across an organization, and shared secrets allow broader multi-scope pipeline access for reusable configurations.

Can I restrict secrets from being exposed in pull requests on Vela?▼

Yes, Vela secrets support pull request restrictions alongside command and substitution allow settings. These security features prevent unauthorized access or accidental exposure of sensitive information during automated build processes.

Why are my Vela pipeline secrets showing up as empty or missing?▼

Empty Vela secrets often result from incorrect source and target mapping or scope misconfigurations. You can troubleshoot this by verifying your secret declarations and ensuring the source and target remapping align correctly.

How do I remap source and target secrets for multi-scope pipelines in Vela?▼

You remap Vela secrets by defining source and target mappings in your pipeline YAML. This allows multi-scope pipelines to securely reference and inject secrets across different repository or organizational contexts.