Config password - mount without password or with different password from the config one?

Help and Support
7

yeah, it works well but not without some controversy.
https://forum.rclone.org/t/rclone-1-5-6-windows-finds-trojan-win32-cryptinject-msr/26172/35
https://forum.rclone.org/t/rclone-exe-is-a-virus-workarounds/26223/1

  1. use rclone create - easy. but credentials are visible on the command line, not able to use environment variables.
  2. use connection strings, easy. but credentials are visible on the command line.
    tho able to use environment variables
  3. use environment variables

in my scripts, i use a 2+3.
convenience of connection strings, secrets using environment variables.

to convert this script

@set RCLONE_CONFIG_WASABI_TYPE=s3
@set RCLONE_CONFIG_WASABI_ACCESS_KEY_ID=xyzLSI7YXRMTYNN
@set RCLONE_CONFIG_WASABI_SECRET_ACCESS_KEY=xzmh7HOLraG0sBNWerCRB53CCvSd0zCJc4n
@set RCLONE_CONFIG_WASABI_ENDPOINT=s3.us-east-2.wasabisys.com

rclone lsd wasabi:

into this something like this, using pseudo code.

  1. create a dictionary with environment variables
  2. create the rclone command.
  3. feed 1+2 to subprocess.run
RcloneEnv={"RCLONE_CONFIG_WASABI_TYPE":"s3", "RCLONE_CONFIG_WASABI_ACCESS_KEY_ID":"xyzLSI7YXRMTYNN", "RCLONE_CONFIG_WASABI_SECRET_ACCESS_KEY": "xyzCmh7HOLraG0sBNWerCRB53CCvSd0zCJc4n", "RCLONE_CONFIG_WASABI_ENDPOINT": "s3.us-east-2.wasabisys"}

CMD='rclone lsd wasabi:'

x=subprocess.run(CMD, shell=True, capture_output=True, text=True, env=RcloneEnv)

if you are already using gcs command line tool, there is --gcs-env-auth