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
Copy file name to clipboardExpand all lines: docs/big-data-cluster/reference-azdata.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ The following article provides reference for the **azdata** tool for [SQL Server
26
26
|[azdata logout](#azdata-logout) | Log out of cluster.
27
27
28
28
## azdata login
29
-
When your cluster is deployed, it will list the controller endpoint during deployment, which you should use to login. If you do not know the controller endpoint, you may login by having your cluster's kube config on your system in the default location of <userhome>/.kube/config or use the KUBECONFIG env var, i.e. export KUBECONFIG=path/to/.kube/config.
29
+
When your cluster is deployed, it will list the controller endpoint during deployment, which you should use to log in. If you do not know the controller endpoint, you may log in by having your cluster's kube config on your system in the default location of <userhome>/.kube/config or use the KUBECONFIG env var, that is, export KUBECONFIG=path/to/.kube/config.
30
30
```bash
31
31
azdata login [--cluster-name -n]
32
32
[--controller-username -u]
@@ -38,7 +38,7 @@ Log in interactively. Cluster name will always be prompted for if not specified
38
38
```bash
39
39
azdata login
40
40
```
41
-
Log in (non-interactively). Log in with cluster name, controller user name, controller endpoint, and EULA acceptance set as arguments. The environment variable CONTROLLER_PASSWORD must be set. If you do not want to specify the controller endpoint, please have the kube config on your machine in the default location of <userhome>/.kube/config or use the KUBECONFIG env var, i.e. export KUBECONFIG=path/to/.kube/config.
41
+
Log in (non-interactively). Log in with cluster name, controller user name, controller endpoint, and EULA acceptance set as arguments. The environment variable CONTROLLER_PASSWORD must be set. If you do not want to specify the controller endpoint, have the kube config on your machine in the default location of <userhome>/.kube/config or use the KUBECONFIG env var, that is, export KUBECONFIG=path/to/.kube/config.
Account user. If you do not want to use this arg, you may set the environment variable CONTROLLER_USERNAME.
54
54
#### `--controller-endpoint -e`
55
-
Cluster controller endpoint "https://host:port". If you do not want to use this arg, you may use the kube config on your machine. Please ensure the config is located at the default location of <userhome>/.kube/config or use the KUBECONFIG env var.
55
+
Cluster controller endpoint "https://host:port". If you do not want to use this arg, you may use the kube config on your machine. Ensure the config is located at the default location of <userhome>/.kube/config or use the KUBECONFIG env var.
56
56
#### `--accept-eula -a`
57
57
Do you accept the license terms? [yes/no]. If you do not want to use this arg, you may set the environment variable ACCEPT_EULA to 'yes'. The license terms for this product can be viewed at https://aka.ms/azdata-eula.
58
58
### Global Arguments
@@ -63,7 +63,7 @@ Show this help message and exit.
0 commit comments