Skip to content

Commit 4dd4f24

Browse files
CMSNAV-798: Add further guidance for using the get_token command
1 parent e618123 commit 4dd4f24

1 file changed

Lines changed: 7 additions & 0 deletions

File tree

README.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -38,6 +38,13 @@ Consider using a **dev container**. While this is in no way a requirement, you m
3838
- You can get an `APIGEE_ACCESS_TOKEN` via the `get_token` command. If you don't already have access to the `get_token` command, you can install it using [these instructions](https://docs.apigee.com/api-platform/system-administration/auth-tools#install).
3939
- You can get the latest `SOURCE_COMMIT_ID` via the `/_ping` endpoint of the proxy you're using. For example, with `PROXY_NAME` set to `nhs-website-content-api-internal-dev`, we would want to access the URL https://internal-dev.api.service.nhs.uk/nhs-website-content/_ping - this should return some JSON, and the value we want has key `commitId`.
4040

41+
:bulb: One way to use the `get_token` command is to call:
42+
43+
```
44+
export APIGEE_ACCESS_TOKEN=$(SSO_LOGIN_URL=https://login.apigee.com get_token)
45+
echo $APIGEE_ACCESS_TOKEN
46+
```
47+
4148
### Let's Roll
4249

4350
1. Install by running `make install` from this directory.

0 commit comments

Comments
 (0)