As referenced here, an accepted methodology is to create a second environment variable for files, i.e.:
- WEBEX_BOTID
Containing the raw string, e.g. "1234-0987-ABCD" - WEBEX_BOTID_FILE
Containing the filename to the secret, e.g. /run/secrets/WEBEX_BOTID
An alternative would be to assume that any unreferenced environment variable could also be a secret, and proactively check the file location as part of the environment variable check, but this seems like it might be too opaque and prone to error.
As referenced here, an accepted methodology is to create a second environment variable for files, i.e.:
Containing the raw string, e.g. "1234-0987-ABCD"
Containing the filename to the secret, e.g. /run/secrets/WEBEX_BOTID
An alternative would be to assume that any unreferenced environment variable could also be a secret, and proactively check the file location as part of the environment variable check, but this seems like it might be too opaque and prone to error.