Publishing a Blueprint

Visual version control and publishing to your Cloud Maker feed

Nick Smith avatar
Written by Nick Smith
Updated over a week ago

We believe in the power of Infrastructure-as-Code and the advantages that a software development approach and tooling can bring to the cloud solution workflow. That's why we've brought the concept of version history and feeds to the visual paradigm of Cloud Maker.

Publishing a Blueprint

Once you have completed your Cloud Maker blueprint and have configured it using the properties panel, you can publish it to your Cloud Maker feed.

Once published, the blueprint can then be deployed to the cloud using Cloud Maker Pipelines.

To publish your active blueprint:

  1. Save your blueprint if it's in an unsaved state

  2. Then select the 'Publish' button on the Cloud Maker toolbar

  3. Enter a title for the publication summarising the changes that have been made

  4. Enter any additional information you wish to associate with the publication

  5. You can see which versions are published on the 'Blueprint History' panel

You can also publish older versions of a blueprint by doing the following:

  1. Open the 'Blueprint History' panel

  2. Locate the version of the blueprint you wish to publish

  3. Select the ellipses menu and then select 'Publish Version'

  4. Enter a 'Title' for the publication summarising the changes made

  5. Add any additional information such as the detail of what has changed

  6. Select the publish button to publish your blueprint

Version History

Every time you save a Cloud Maker blueprint, Cloud Maker records this in the Blueprint History. You can quickly see the versions that have been saved over the lifetime of a blueprint by selecting the Blueprint History icon on the right dock system.

Restore a Blueprint Version

You can easily restore a blueprint version by doing the following:

  1. Open the 'Blueprint History' panel

  2. Locate the version you wish to restore

  3. Select the ellipses menu and then select 'Restore Version'

  4. If you haven't saved your blueprint you will be warned that continuing will lead to any unsaved changes being lost

  5. The restored version of the blueprint will become the latest version

Did this answer your question?