Storing config flag in the back-end configuration. E.g. store: `--header` permanently on the back-end level

Help and Support
1

What is the problem you are having with rclone?

I am trying to store the: --header values permanently in the rclone.conf on the remote/back-end level, so I no longer need to repeat these values in the CLI.

Run the command 'rclone version' and share the full output of the command.

rclone v1.67.0

  • os/version: ubuntu 24.04 (64 bit)
  • os/kernel: 6.8.0-40-generic (x86_64)
  • os/type: linux
  • os/arch: amd64
  • go/version: go1.22.4
  • go/linking: static
  • go/tags: none

Which cloud storage system are you using? (eg Google Drive)

N/A, even though I use S3, my question is applicable to all remotes.

The command you were trying to run (eg rclone copy /tmp remote:tmp)

rclone ls --header "Header: Value" remoteCustomAuthHeader:

If storing: --header in the back-end config isn't possible at the moment, could Rclone support similar approach that's used in librclone - Remote Control / API ?

That is, there is a specific field: _config where user can pass custom Rclone config.

I think similar question was asked here: Using concurrency and transfer settings per remote / backend section in config file - #5 by CoolCold with regards to transfers

E.g. back-end config could look like this:

[s3]
type = s3
endpoint = https://s3.endpoint.com
_config = {"header": [{"CustomHeader": "customValue"}], "Transfers":10}

Thanks for your help!

2

that is not possible

can use environment variables
RCLONE_HEADER=

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.