Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

What data Devolutions CLI sends

Devolutions CLI itself talks to the workspaces you sign in to, and keeps its configuration on your computer, in your user account. This page explains what leaves your computer, what's stored locally, and how to control both.

What goes over the network

WHEN YOU USE
DEVOLUTIONS CLI CONTACTS

A Devolutions Cloud context

The Devolutions Cloud address you signed in to. With a browser sign-in (--oauth), also Devolutions Account (login.devolutions.com), to sign you in and renew your session.

A Devolutions Server context

The Devolutions Server address you signed in to. With a username and password or Windows authentication, the sign-in request also includes your computer name, your local user name, and your operating system platform.

A local profile context

No address of its own. A local context only points at a profile folder on your computer.

The telemetry preference

Telemetry is off until you turn it on. To see the current preference:

devo config telemetry get

To change it, pass true or false and confirm with --yes:

devo config telemetry set false --yes

The preference is saved on your computer, in the Devolutions CLI configuration folder.

What's stored on your computer

Devolutions CLI keeps its configuration in one folder for your user account:

  • By default: a Devolutions/CLI folder in your user's local application data folder.

  • If your system has no local application data folder: .devolutions/cli in your home folder.

  • If DEVO_CLI_CONFIG_HOME is set: that folder. See Move the configuration folder.

When Devolutions CLI records its background process, it restricts this folder to your account and the system account on Windows, and to your account only on macOS and Linux.

devo context list shows the path of the context file on its Store: line.

WHAT
WHERE AND HOW

Contexts

Their names, the workspace address or profile folder, and which one is current, in JSON files of the configuration folder. On macOS and Linux, the files themselves are also readable and writable by your account only.

Browser sign-in sessions

In your operating system's secure store: protected with your Windows user account on Windows, the Keychain on macOS, and the Secret Service (libsecret) on Linux. Without a supported secure store, browser sign-in isn't available.

Application secrets, API keys, and passwords

Never saved. The context keeps only the name of the environment variable or the path of the file you gave at sign-in, and reads the value again each time it's needed.

Devolutions Cloud application key

Saved in the context file, with the pointer to its secret.

Telemetry preference

In the configuration folder.

devo logout clears the sign-in of a Devolutions Cloud or Devolutions Server context but keeps the context. devo context delete removes the context and, for a Devolutions Cloud or Devolutions Server login, its stored session too. See Switch between workspaces.

Move the configuration folder

Set the DEVO_CLI_CONFIG_HOME environment variable to use another folder, for example an isolated folder on a build agent:

Every devo command started with this variable reads and writes its contexts in that folder. When you don't select a local profile, Devolutions CLI also uses an rdm subfolder of this folder as its default profile folder. See Install Devolutions CLI on build agents.

Export your configuration

devo config export writes your local profile contexts, the name of the current context, and the telemetry preference to a .json file. It never includes a sign-in session or a secret value.

Add --no-contexts or --no-tooling to leave out the contexts or the telemetry preference, and --force to replace an existing file.

Next

Last updated

Was this helpful?