Precedence rules for config?

ncw · July 6, 2020, 9:39pm

Yes they are

If you want to see the precedence exactly then take a look at

rclone/rclone/blob/b2f4f52b642ed6b9d70849156e93145d16956a9f/fs/fs.go#L1279



// ConfigMap creates a configmap.Map from the *RegInfo and the
// configName passed in.
//
// If fsInfo is nil then the returned configmap.Map should only be
// used for reading non backend specific parameters, such as "type".
func ConfigMap(fsInfo *RegInfo, configName string) (config *configmap.Map) {
	// Create the config
	config = configmap.New()

	// Read the config, more specific to least specific

	// flag values
	if fsInfo != nil {
		config.AddGetter(&regInfoValues{fsInfo, false})
	}

	// remote specific environment vars
	config.AddGetter(configEnvVars(configName))

	// backend specific environment vars

From more specific to less specific

flag values
remote specific environment vars
backend specific environment vars
config file
default values

I note that rclone may be frustrating for NixOS because it writes tokens back to the config file.

There has been some discussion on GitHub about writing to a separate file and leaving the config file as read only.