Versions & publishing
Save versions, keep history, and publish a version so it can be deployed.
Telflo uses an explicit, manual save model — similar to committing changes — so you control exactly what's recorded and when. On top of that, publishing marks a version as ready to deploy.
Saving versions
- Click Save in the toolbar to record the current state of the canvas and YAML as a version.
- An Unsaved changes marker appears whenever you have edits that aren't yet saved.
- You can attach a short note to a version to describe what changed.
Current version vs. new version
- Save updates the current version in place.
- Save as new version branches off a new version, leaving the previous one intact.
Read-only versions
Older versions — and published versions — may be read-only. If you edit one, Telflo shows a "This version is read only" indicator and offers to save your changes as a new version rather than rewriting history.
Version history
Switch between versions using the version select in the toolbar. From there you can review previous versions (with their notes and timestamps) and return to any of them.
Undo/Redo vs. versions. Undo/Redo (Ctrl/Cmd + Z / Shift + Z) is a session-only safety net that clears when you close the editor. Versions are saved to your account and persist. Use Undo for quick fixes; save a version when you reach a state worth keeping.
| Mechanism | Scope | Persistence |
|---|---|---|
| Undo / Redo | Every action | Session only |
| Versions | Manual saves | Saved to your account |
Publishing
Saving keeps a version private to the editor. Publishing promotes a version to a release that can be deployed to collectors:
- Open the version you want to release.
- Choose Publish from the version controls (Telflo saves any pending changes first so the published version matches the canvas).
- Confirm in the publish dialog.
Once published, that version becomes selectable when you create or update a fleet. Only published versions are deployable.
Copying a version
Use Copy version to start a new configuration (or version) from an existing one as a base — handy for creating environment variants from a known-good config.
Next
- Manage your configurations — rename, share, and organize.
- Deploy a published version to real collectors.