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.
- 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.
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 @- https://api.velocity.tech/api/v1/blueprints