Versions & publishing

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. The button is enabled while the configuration has unsaved edits, marked by the Unsaved badge in the toolbar.
• Saving updates the current version in place. A new version is created when you save edits to a read-only version, or when you copy a version. telflo config push in the CLI follows the same rule: it validates the file, then edits the latest draft in place, or appends a new version when the latest version is published. The API refuses an edit to a published version.
• A new version inherits the configuration's collector distribution, which cannot be changed; the collector version is chosen per version and can differ between versions. See Key concepts.

Read-only versions

A version becomes read-only once it has been published, and shows a Read-only version badge on the canvas. You can still edit the canvas: selecting Save opens the Read-Only Version dialog, and Save as New Version records your edits as a new version, which the editor switches to. Unpublished versions, including older ones, are saved in place, so history is not overwritten by accident.

Unsaved changes

If you switch versions or leave the editor with unsaved edits, the Unsaved Changes dialog offers Save & Continue, Discard Changes, and Cancel. On a read-only version, Save & Continue saves the edits as a new version.

Version history

Use the Version: dropdown in the toolbar to switch between versions. Each entry shows the version's name and number, such as v3, and Published when the version has been published; an unnamed version is listed as Version N. To name an unpublished version, select the pencil icon next to it in the dropdown. The Rename Version dialog takes a Version name of up to 80 characters. Published versions cannot be renamed and show a lock icon instead.

Undo and redo are separate from versions.

Publishing

A version of a configuration that has never been published is visible only to the configuration's author, in the editor and through the CLI and API. Publishing promotes a version to a release that can be deployed and makes the configuration, its version history included, visible to the organization.

1. Open the version to publish.
2. Select Publish in the toolbar. The Publish Configuration dialog opens and notes that unsaved changes will be saved.
3. Select Publish in the dialog. Telflo saves any pending changes, then publishes the version, so the published version matches the canvas.

The version is now read-only, and the toolbar's Publish button is disabled for it; hovering it shows Already Published. A published version can be assigned to a fleet's deploy group. Only published versions can be deployed. See Create a fleet.

From the terminal, telflo config publish <id> --version <n> publishes a version, and telflo config push <id> -f <file> --publish saves and publishes in one step; publishing an already published version succeeds and points the configuration's published version at it again. Publishing requires the contributor or admin role, in the editor and through the API. telflo deploy --fleet <id> --config <id> then rolls the configuration's published version out to a deploy group and refuses a configuration that has none. See Commands.

Start from an existing version

Open the Version: dropdown and select Create New Version. The Copy Version dialog opens; optionally enter a Version name and select Continue. Telflo creates a new version from the current canvas, including any unsaved edits, copies the version's validation rules and test suites along with it, and opens the new version. The version you started from is not changed. 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.