snaptool as a docker service -- auth-token.json permissions concern

[vrragosta]

When snaptool is ran using docker, as outlined on docs.weka.io, at the following link, there seem to be some oddities regarding the placement of the auth-token.json file. Can these be confirmed?

https://docs.weka.io/monitor-the-weka-cluster/snapshot-management#option-2-install-the-snaptool-package-in-docker

In snaptool.yml, the cluster configuration is as follows:
cluster:
auth_token_file: auth-token.json
hosts: 172.31.11.135,172.31.1.65,172.31.14.21,172.31.1.132,172.31.11.215,172.31.10.18
force_https: True # only 3.10+ clusters support https
verify_cert: False # default cert cannot be verified

It appears that the auth-token.json file can only be read if the following conditions are met:

• The auth-token.json file is placed at /root/.weka/auth-token.json
• The permissions on the /root/.weka/auth-token.json path must be "world" readable

Please confirm the above is accurate.

If so, why is there no mechanism for specifying auth-token.json, at an arbitrary location on the filesystem, or incorporating it into the snaptool docker environment itself?