Hmmm, not sure how to articulate this question because searching forum seems to only reference situations where an EXISTING rclone.conf can be replicated and also sliced/diced by an external script.
Rather, I am asking whether it is technically feasible to script the config process itself, from [New Remote] creation through [auto-config] for tokens where required.
An example situation would be for Onedrive on Windows, which automates the browser authentication, using cmd.
Thank you in advance for your time and attention and this miraculous product.
I’ve been adding subcommands to config in the latest beta - check those out
Available Commands:
create Create a new remote with name, type and options.
delete Delete an existing remote <name>.
dump Dump the config file as JSON.
edit Enter an interactive configuration session.
file Show path of configuration file in use.
providers List in JSON format all the providers and options.
show Print (decrypted) config file, or the config for a single remote.
update Update options in an existing remote.
Start with rclone --help - that gives you a list of subcommands, next rclone config --help, repeat for the subcommands rclone config dump --help. After the release they will have proper docs on the website made from those help pages.