You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the API key/secret are expected via environment variables. That's great, but it would also be great if this container supported using secrets. This would mean the value of the api key/secret would be available in /run/secrets/MY_SECRET. This would allow us to deploy this solution using something like https://rancher.com without exposing our api key/secret in the GUI.
The text was updated successfully, but these errors were encountered:
Currently the API key/secret are expected via environment variables. That's great, but it would also be great if this container supported using secrets. This would mean the value of the api key/secret would be available in
/run/secrets/MY_SECRET
. This would allow us to deploy this solution using something like https://rancher.com without exposing our api key/secret in the GUI.The text was updated successfully, but these errors were encountered: