Authentication commands

The first step for using Aggregator CLI is to logon into both Azure and Azure DevOps. You can a single command, logon.env, or two separate commands, logon.azure and logon.ado. The former is most useful in an automated scenario, while the other two can be more practical in an interactive session. Use the logoff command to remove any cached authentication data.

logon.azure #

Logon into Azure. This must be done before other verbs. The credentials are cached locally and expire after 2 hours. Takes four mandatory options.

OptionShort formDescription
--subscription-sAzure Subscription Id.
--tenant-tAzure Active Directory Tenant Id.
--client-cService Principal Client Id also known as Application Id.
--password-pService Principal password also known as Client secret.

logon.ado #

Logon into Azure DevOps. This must be done before other verbs. The credentials are cached locally and expire after 2 hours. Takes three mandatory options.

OptionShort formDescription
--url-uAccount/server URL, e.g. myaccount.visualstudio.com.
--mode-mAuthentication mode. Currently the only valid mode is PAT.
--token-tAzure DevOps Personal Authentication Token.

logon.env [v0.9.14] #

Logon into both Azure and Azure DevOps using Environment. The credentials are cached locally and expire after 2 hours. It has no specific options.

Environment VariableDescription
AGGREGATOR_SUBSCRIPTIONIDAzure Subscription Id
AGGREGATOR_TENANTIDAzure Active Directory Tenant Id.
AGGREGATOR_CLIENTIDService Principal Client Id also known as Application Id.
AGGREGATOR_CLIENTSECRETService Principal password also known as Client secret.
AGGREGATOR_AZDO_URLAccount/server URL, e.g. myaccount.visualstudio.com .
AGGREGATOR_AZDO_MODEAuthentication mode. Currently the only valid mode is PAT.
AGGREGATOR_AZDO_TOKENAzure DevOps Personal Authentication Token.

logoff [v0.9.14] #

Logoff removing any locally cached credential.