should be able to select a profile via the environment

[jclulow]

Target component

• CLI
• SDK
• Something else
• Not sure

Overview

At present, it appears one can specify a URL and a token through the environment, using OXIDE_HOST and OXIDE_TOKEN. One can also select a profile via the global --profile option, or by setting one in the default-profile property of the configuration file.

It should be possible to provide a profile via the environment, by setting OXIDE_PROFILE to the name of the profile you would otherwise have to pass to the --profile option in every invocation of the CLI.

Implementation details

No response

Anything else you would like to add?

No response

[ahl]

Love it. How would you expect the variety of ways to specify credentials to interact? For example, if one specifies OXIDE_PROFILE and --profile: former, latter, error?

A⬇️ B➡️	default-profile	--profile	host/token env	$OXIDE_PROFILE
default-profile	X	B	B	B
--profile	X	X	error	error
host/token env	X	X	X	error
$OXIDE_PROFILE	X	X	X	X

Does that seem right? I could imagine --profile with $OXIDE_HOST / $HOST_TOKEN still working... in some fashion.

[jclulow]

I think I would probably use basically the same pattern for everything:

• take value from default in file (profile) or value configured in the profile (host, token) first
• override with value from environment, if set
• override with value from option argument, if provided

So basically the HOST and TOKEN variables can individually override the values from the profile, however that's chosen. One can set the PROFILE in the environment (e.g., as part of a shell function that maybe also influences the prompt or the terminal title so that you can see what context you're in) but also, if needed, run a one-off command in a specific profile that is not the current default/selected one.

[ahl]

What should happen if both $OXIDE_PROFILE is set and --profile is specified?

[wfchandler]

Personally I would expect the explicit CLI argument to override the environment variable.

[jclulow]

Personally I would expect the explicit CLI argument to override the environment variable.

Yes, definitely. That's what I was trying to convey in my suggested hierarchy: option arguments would override environment variables would override configuration from the file.

[ahl]

Personally I would expect the explicit CLI argument to override the environment variable.

Error or silently override?

[wfchandler]

Silently override. I can imagine users setting the environment variable in their bashrc as a convenience, overriding it when necessary.