Committing to a Blueprint

Velocity Environments can be created from local files, but for a Velocity Blueprint to be accessible for an entire organization, it must first be committed to Velocity. This guide will walk you through the process of committing to a Velocity Blueprint.
After you've added the required Velocity Annotations and Templates to your Kubernetes manifests, you can add them to your Blueprint via the CLI with the veloctl blueprint commit command.
NOTE: Each time you commit a group of files to your Blueprint, you will need to designate a Blueprint Source.

Committing from a single K8s manifest:

veloctl blueprint commit -f example.yaml --source <logical_descriptor or repo_name>

Committing from a Helm Chart:

helm template . -f velocity-values.yaml | veloctl blueprint commit -f - --source <helm_chart_descriptor>