7a6603b03d | ||
---|---|---|
.vscode | ||
docs | ||
experiments | ||
scripts | ||
src/a01 | ||
.gitignore | ||
.python-version | ||
.travis.yml | ||
HISTORY.rst | ||
LICENSE | ||
Pipfile | ||
Pipfile.lock | ||
README.md | ||
pylintrc | ||
setup.py |
README.md
A01 - The CLI for ADX Automation System
Prerequisite
- Install Python 3.6
- Install Docker CE
- Install Azure CLI
- Run
az aks install-cli
to install Kubectl using Azure CLI - Run
az login
to login Azure using Azure CLI. Please use the corp account.
Install
- Path to the latest version can be found here: https://a01tools.blob.core.windows.net/client/latest
- Note:
- Through virtual environment is not required, it is nevertheless included in following examples as a good practice.
- The earlier version can be found at https://a01tools.blob.core.windows.net/client/archive/adx_automation_cli-{VERSION}-py3-none-any.whl
Bash
$ virtualenv env --python=python3
$ . env/bin/activate
$ curl -s https://a01tools.blob.core.windows.net/client/latest | xargs pip install
Windows
- In a browser navigate to https://a01tools.blob.core.windows.net/client/latest
- Write down the path
> python -m virtualenv env --python=python3.6
> env\Scripts\activate
> pip install <path>
Initialize
- Run
a01 check
to validate environment. - Run
a01 login --endpoint secondapi.azclitest.com
to login. - Run
az aks get-credentials -g adx-automation-a01 -n adx-automation
to get cluster creds.
Onboard your own tests
Find onboard documentation here.
Contributing
This project welcomes contributions and suggestions. Most contributions require you to agree to a Contributor License Agreement (CLA) declaring that you have the right to, and actually do, grant us the rights to use your contribution. For details, visit https://cla.microsoft.com.
When you submit a pull request, a CLA-bot will automatically determine whether you need to provide a CLA and decorate the PR appropriately (e.g., label, comment). Simply follow the instructions provided by the bot. You will only need to do this once across all repos using our CLA.
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.