Skip to main content
Telepúrte uses the saved directory file and the exact action on the path on the node to configure the park, so you can apply the approved content or just check that the server matches it. This is different from the manual Web SFTP editor: the editor works with the current file, and the playbook associates a specific artifact with the goals and saves the launch results.

Prepare an approved file

In Playbooks and Schedules add a file to the directory. Specify a clear name, for example, app.conf, and download the contents. The card saves the size and checksum; the material is stored encrypted. Before the first replacement, download the current configuration from the node and save it as a separate source version. The Telepúrte directory does not automatically back up each file that will be overwritten on the server.

Apply the content

Add to the playbook Apply the configuration file and ask:
  • artifact from the catalog;
  • an absolute path, such as /etc/example/app.conf;
  • 0600, 0640 or 0644 mode according to application requirements.
On the node, this exact path has to be allowed to the agent, you need OS rights and permission to write in the agent’s service system constraints, and adding a path to the panel policy doesn’t automatically make the protected directory available. First, run on a test node. Recording is done by checking the content and replacing the file; symbolic links and insecure paths are rejected; an existing file can be replaced, which is a change operation. Using a file does not mean restarting the application. Add the appropriate separate step only after the service requirements and configuration check are clear.

Check unchanged

Action. Check the configuration file It uses the same artifact, path and mode, but it doesn’t rewrite the file. It compares content and rights. For example, if the text matched, but the file became available to everyone instead of 0600, the check will also detect a discrepancy, such a check is convenient on a schedule and does not require regular overwriting of the already correct file.

Example of a work cycle

  1. Save the original configuration of the test machine.
  2. Add the new version of app.conf to the catalog.
  3. Create a file application playbook with a precise path and mode.
  4. Run it on a test node and check the application with a regular validator.
  5. Create a separate reading playbook to check out the same artifact.
  6. Check with unchanged, then set up the check schedule for work purposes.
If you detect drifted, first determine if the change is an error or a new agreed-upon state. Do not correct it by automatically overwriting without understanding the cause.

A history of discrepancies

Telepúrte stores the last successful observation of the node + path pair, the expected artifact, the actual checksum, the mode and the time of verification. A transition event appears when the state or approved base changes. Repeating the same discrepancy updates the observation without creating the same notification each time. Changing the approved file is changing the comparison base, matching the new database does not mean that the previous configuration has been restored. The content of the file is not copied to the divergence event. The results are visible in the tasks; the summary and discrepancies history are available through the readable APIs /api/v1/config-drift and /api/v1/config-drift/events. This is not continuous observation of the file system: the state is current at the time of the last validation performed.

Verification

After application, re-read the file, check the rights and the application. After the control task, check the time, path and ID of the artifact, not just the word unchanged. Obsolete observation does not confirm the current state.

Rollback

Apply the separately stored original configuration and the previous mode, perform a regular check and the necessary use of the service. If the original copy is not saved, it is impossible to restore the previous text from the checksum. Extended parameters, designated as APIs, may not be present in the current interface form.