Description
On many CLI actions, a password (or Cloud token) is a required. We normally recommend people customize their start scripts to include your password, other credentials, and other regular specified parameters so you don't have to type them in on the command line. Even after hiding the password in the file, however, some operating systems still have mechanisms to that allow an administrator to see running processing commands including whatever password was typed. This support describes an alternative.
Specifying passwords in environment variables
We provide support for specific environment variables to be recognized and used as substitutes for passwords typed on the command.
The environment variables are:
| Environment Variable | Description |
|---|---|
ATLASSIAN_CLI_PASSWORD | Will be used when user specifies –password @ |
ATLASSIAN_CLI_DB_PASSWORD | Will be used when user specifies –dbPassword @ |
ATLASSIAN_CLI_TARGET_PASSWORD | Will be used when user specifies –targetPassword @ |
Property file
Since Release 8.8, you can also specify any environment variable in your property file configuration using a standard environment variable reference often supported in property files. This is now the recommended way to use environment variables for CLI actions instead of the variables mentioned above. That support now considered to be deprecated with the possibility the support may be removed in a future version.
myjira = jira https://jira.examplegear.com -u automation -p ${MY_PASSWORD}
cloud = https://examplegear.atlassian.net --user automation@examplegear.com --token ${MY_ATLASSIAN_CLOUD_TOKEN}