Configuring odo global settings

The global settings for odo can be found in preference.yaml file; which is located by default in the .odo directory of the user's HOME directory.

Example:

Linux

/home/userName/.odo/preference.yaml

Windows

C:\\Users\userName\.odo\preference.yaml

Mac

/Users/userName/.odo/preference.yaml

---

A different location can be set for the preference.yaml by exporting GLOBALODOCONFIG in the user environment.

View the configuration

To view the current configuration, run odo preference view.

odo preference view

Example:

$ odo preference view
PARAMETER             CURRENT_VALUE
UpdateNotification
Timeout
PushTimeout
RegistryCacheTime
Ephemeral
ConsentTelemetry

Set a configuration

To set a value for a preference key, run odo preference set <key> <value>.

odo preference set updatenotification false

Example:

$ odo preference set updatenotification false
Global preference was successfully updated

Note that the preference key is case-insensitive.

Unset a configuration

To unset a value of a preference key, run odo preference unset <key>; use -f flag to skip the confirmation.

odo preference unset updatednotification

Example:

$ odo preference unset updatednotification
? Do you want to unset updatenotification in the preference (y/N) y
Global preference was successfully updated

Unsetting a preference key sets it to an empty value in the preference file. odo will use the default value for such configuration.

Preference Key Table

Preference	Description	Default
UpdateNotification	Control whether a notification to update odo is shown	True
NamePrefix	Set a default name prefix for an odo resource (component, storage, etc)	Current directory name
Timeout	Timeout for Kubernetes server connection check	1 second
PushTimeout	Timeout for waiting for a component to start	240 seconds
RegistryCacheTime	For how long (in minutes) odo will cache information from the Devfile registry	4 Minutes
Ephemeral	Control whether odo should create a emptyDir volume to store source code	True
ConsentTelemetry	Control whether odo can collect telemetry for the user's odo usage	False