I regularly get confused by the naming of the environment variables for SSH keys. For example, when I read MANAGER_KEY, I immediately assume that it's the key to access the manager when it's actually the manager's key to access the controller.
Similarly, there are MANAGER_KEYS and CONTROLLER_KEYS which I wouldn't know how to use either if it weren't for the explanatory comments next to them in the example .env file.
Therefore, I propose the following new names:
MANAGER_KEY -> MANAGER__CONTROLLER_ACCESS_KEY
MANAGER_KEYS -> MANAGER__AUTHORIZED_KEYS
CONTROLLER_KEYS -> CONTROLLER__AUTHORIZED_KEYS
Note that I included double underscores after the name of the service that the respective variables belong to. I find that it especially communicates the purpose of MANAGER__CONTROLLER_ACCESS_KEY more clearly that way.
I regularly get confused by the naming of the environment variables for SSH keys. For example, when I read
MANAGER_KEY, I immediately assume that it's the key to access the manager when it's actually the manager's key to access the controller.Similarly, there are
MANAGER_KEYSandCONTROLLER_KEYSwhich I wouldn't know how to use either if it weren't for the explanatory comments next to them in the example.envfile.Therefore, I propose the following new names:
MANAGER_KEY->MANAGER__CONTROLLER_ACCESS_KEYMANAGER_KEYS->MANAGER__AUTHORIZED_KEYSCONTROLLER_KEYS->CONTROLLER__AUTHORIZED_KEYSNote that I included double underscores after the name of the service that the respective variables belong to. I find that it especially communicates the purpose of
MANAGER__CONTROLLER_ACCESS_KEYmore clearly that way.