CD - Push blueprint updates

Push blueprint updates directly from your CI\CD Pipeline
As your application grows, new services are frequently added, and your environment configuration changes and evolves. To keep your dev/test environments effective and prevent drift between your production configuration and your dev/test configuration, Velocity recommends pushing blueprint updates repeatedly directly from your CI\CD Pipeline.
The following guide explains using the Blueprints API to send automated blueprint updates.


  • A valid blueprint file with Velocity annotations. The file should concatenate all the K8s resources that are part of the environment configuration.
  • An API token with permissions to manage blueprints.
To get an API token, contact Velocity Support

Using curl to automate ongoing blueprint updates

The Blueprints API is a simple REST API that can be triggered using curl.
The following curl command sends Velocity an updated version of the blueprint file. Before running the command replace the <VELOCITY_TOKEN> with the token received from Velocity
helm template ./path/to/chart | curl -X POST \
-H "Content-Type: application/x-yaml" \
-H "Authorization: Token <VELOCITY_TOKEN>" \
--data-binary @-
curl can be called directly from your CD pipeline, so when a PR is merged to master, you can update your blueprint version in Velocity to align with the latest updates.