NetStacksNetStacks
Contact SalesDownload

Version History

Enterprise

How NetStacks versions config templates, how to view and restore an earlier version, and how template changes reach stacks.

Overview

Every config template keeps a numbered history of its source. Creating a template saves version 1, and each later change to the source adds the next number. You can open any earlier version in the editor and save it again to roll the template back.

When a Version Is Created

  • Creating a template saves v1.
  • Every Save of an existing template in the editor saves a new version and makes it current, even if you only changed the name or description.

Each version records its source, the variables detected in it, when it was created, and who created it. The Version column in the Templates list shows the current version number.

View Version History

  1. Open the template from Config Automation → Templates.
  2. Scroll to the Version History card at the bottom of the page. It shows how many versions are available.
  3. Click the card header to expand it.
Version History card expanded, showing version v1 marked current with Created, Created By and a Load action

The table lists each version with its Created time and Created By user. The current version is marked (current).

Restore an Earlier Version

  1. In Version History, click Load on the version you want. Its source replaces the text in Template Source and a Version loaded into editor message appears.
  2. Review the source. The page shows Unsaved changes; nothing has changed on the server yet.
  3. Click Save. The loaded source is saved as a new version (for example v4 if you loaded v2 while v3 was current) and you return to the Templates list. The history is never rewritten, so you can always go forward again.
Compare before you restore

Loading a version only changes the editor; the preview always renders the saved source. To see what an old version produces, load it, save, reopen the template, and enter test values. If you change your mind, load the newer version and save again.

Versions and Stacks

Stacks refer to a template, not to a specific version. Every instance preview and every deployment renders the template's current source at that moment. Saving a template therefore changes what all the stacks that use it will push the next time they are deployed.

  • Before you edit a template, check the Linked column in the Templates list to see how many stacks use it. Click the number to list them.
  • Deployments that already ran are not affected. Each deployment keeps the exact config it rendered and sent, visible in its logs (see Deployments & Rollback).
  • To change a template for one stack only, create a copy under a new name and use the copy in that stack.