Versions & publishing
Save versions, keep history, and publish a version to deploy to a fleet.
Telflo uses an explicit save model: you control what is recorded and when. Publishing marks a version as ready to deploy.
Save versions
- Select Save in the toolbar to record the current canvas and YAML as a version.
- The unsaved-changes indicator appears when there are edits that are not yet saved.
- Rename a version in the version dropdown to describe the change.
Read-only versions
Published versions and older versions are read-only. Editing a read-only version prompts you to save the changes as a new version, so history is not overwritten.
Version history
Use the version control in the toolbar to switch between versions and review their names and timestamps.
Undo and redo are separate from versions.
| Mechanism | Scope | Persistence |
|---|---|---|
| Undo and redo | Each action | Session only |
| Versions | Manual saves | Saved to your account |
Publishing
A saved version is private to the editor. Publishing promotes a version to a release that can be deployed.
- Open the version to publish.
- Select Publish in the toolbar. The Publish Configuration dialog opens; Telflo saves any pending changes first, so the published version matches the canvas.
- Confirm in the dialog.
A published version can be assigned to a fleet's deploy group. Only published versions can be deployed. See Create a fleet.
Start from an existing version
Use Create New Version in the version controls to copy the current version into a new version of the configuration. Use this to iterate from a known-good version, such as a published release, without editing it in place.
Next steps
- Manage your configurations. See Managing configurations.
- Deploy a published version. See Fleet management.
Last updated on