vela-deployments

Manage deployment targets, parameters, and CLI triggers for Vela CI/CD.

Updated Mar 7, 2026
One-click install
npx skills add https://github.com/ryanmr/vela-skills --skill vela-deployments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vela-deployments
Source: https://github.com/ryanmr/vela-skills/tree/main/.agents/skills/vela-deployments
Command: npx skills add https://github.com/ryanmr/vela-skills --skill vela-deployments

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines the process of triggering, configuring, and managing deployments within the Vela CI/CD platform, reducing manual effort and ensuring consistency.

Core Features & Use Cases

  • Trigger Deployments: Initiate deployments via CLI or UI to specified targets (e.g., staging, production).
  • Parameterization: Pass custom parameters to deployment jobs, which are available as environment variables.
  • Pipeline Gating: Define steps that only execute on deployment events or for specific deployment targets.
  • UI Form Generation: Configure deployment parameters and targets to generate user-friendly forms in the Vela UI.
  • Use Case: Automatically deploy a new version of your application to the 'staging' environment when a specific Git tag is pushed, passing a 'region' parameter to the deployment script.

Quick Start

Use the vela-deployments skill to trigger a deployment to the 'production' target for the current repository, passing 'region=us-east' as a parameter.

Frequently Asked Questions about vela-deployments

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

FAQPage Schema
How do I trigger a Vela deployment to a specific target environment?

You can trigger a Vela deployment to targets like staging or production using CLI commands or the generated UI forms, passing custom parameters such as region to the deployment job dynamically.

How do I pass custom parameters to a Vela CI/CD pipeline job?

Custom parameters passed during a Vela deployment are exposed as runtime environment variables, specifically using the DEPLOYMENT_PARAMETER_* format, allowing dynamic job execution within your pipeline.

Can I gate pipeline steps to only run on Vela deployment events?

Yes, you can gate pipeline steps to execute exclusively on deployment events or for specific deployment targets, ensuring certain jobs only run when deploying to environments like production.

How does Vela generate UI forms for deployment inputs?

Vela generates UI forms by configuring deployment parameters and targets within your pipeline, creating user-friendly inputs that capture custom variables before triggering the deployment job.

What environment variables are available during a Vela deployment?

During a Vela deployment, runtime environment variables like DEPLOYMENT_PARAMETER_* and VELA_DEPLOYMENT are available, providing dynamic context and custom inputs to the executing pipeline jobs.

Do I need to configure dependencies to automate Vela deployments?

No external dependencies are required to automate Vela deployments, as the skill manages deployment targets, parameters, and CLI triggers natively within the Vela CI/CD system.