CMSNAV-798: Create new make command for getting Apigee token

Author: tomhosker-bjss

Makefile

@@ -53,6 +53,9 @@ release: clean publish build-proxy
 	cp ecs-proxies-deploy.yml dist/ecs-deploy-internal-qa-sandbox.yml
 	cp ecs-proxies-deploy.yml dist/ecs-deploy-internal-dev-sandbox.yml
 
+get_apigee_access_token:
+	SSO_LOGIN_URL=https://login.apigee.com get_token
+
 #################
 # Test commands #
 #################
@@ -76,7 +79,7 @@ smoketest:
 
 test:
 	$(TEST_CMD) \
-	--junitxml=test-report.xml \
+	--junitxml=test-report.xml
 
 smoketest-prod:
 	$(PROD_TEST_CMD) \

README.md

@@ -38,12 +38,7 @@ Consider using a **dev container**. While this is in no way a requirement, you m
     - 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).
     - 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`.
 
-:bulb: One way to use the `get_token` command is to call:
-
-```
-export APIGEE_ACCESS_TOKEN=$(SSO_LOGIN_URL=https://login.apigee.com get_token)
-echo $APIGEE_ACCESS_TOKEN
-```
+:bulb: The `make get_apigee_access_token` command provides a useful shorthand for calling `get_token` with all the right environmental variables.
 
 ### Let's Roll