From 1cad93d499c2cfbfb8d4ca1ab092a53194764067 Mon Sep 17 00:00:00 2001 From: Stomzy <45337015+airamare01@users.noreply.github.com> Date: Mon, 23 Dec 2024 16:09:13 +0300 Subject: [PATCH] Adding emphasis to steps A couple customers are getting confused and using both env vars and cody auth login to authenticate with the CLI leading to undesirable effects. This change adds emphasis for customers getting started with CLI --- docs/cody/clients/install-cli.mdx | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/cody/clients/install-cli.mdx b/docs/cody/clients/install-cli.mdx index 6032539be..32dee1062 100644 --- a/docs/cody/clients/install-cli.mdx +++ b/docs/cody/clients/install-cli.mdx @@ -98,8 +98,8 @@ export SRC_ENDPOINT=ENDPOINT export SRC_ACCESS_TOKEN=ACCESS_TOKEN cody auth login # stores the access token securely ``` -You don't need to export `SRC_ENDPOINT` or `SRC_ACCESS_TOKEN` after running `cody auth login`. -Subsequent command invocation will use the stored access token. +You don't need to export `SRC_ENDPOINT` or `SRC_ACCESS_TOKEN` after running `cody auth login`. +Subsequent command invocation will use the stored access token. @@ -112,7 +112,8 @@ cody auth whoami ## Authenticate with only environment variables -Skip this step if you have already authenticated with the `cody auth login` command. +**Skip this step if you have already authenticated with the `cody auth login` command.** + If you prefer not to let Cody CLI store your access token, you can also pass the endpoint URL and access token through the environment variables `SRC_ENDPOINT` and `SRC_ACCESS_TOKEN`.