CMSNAV-798: Fix build script

Author: tomhosker-bjss

Makefile

@@ -1,7 +1,10 @@
 SHELL=/bin/bash -euo pipefail
 
-include .env
-export
+# Only include .env if it exists.
+ifneq ("$(wildcard .env)","")
+	include .env
+	export
+endif
 
 #Installs dependencies using poetry.
 install-python:
@@ -53,7 +56,7 @@ 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:
+token:
 	SSO_LOGIN_URL=https://login.apigee.com get_token
 
 #################

README.md

@@ -38,7 +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: The `make get_apigee_access_token` command provides a useful shorthand for calling `get_token` with all the right environmental variables.
+:bulb: The `make token` command provides a useful shorthand for calling `get_token` with all the right environmental variables.
 
 ### Let's Roll
 

azure/templates/run-tests.yml

@@ -20,7 +20,6 @@ steps:
     # In order to run tests in prod you must supply the unique ID of an Apigee app
     # that has authorized access to your service proxy.
     - bash: |
-        touch .env
         export PROXY_NAME="$(FULLY_QUALIFIED_SERVICE_NAME)"
         export APIGEE_ACCESS_TOKEN="$(secret.AccessToken)"
         export APIGEE_APP_ID="MY APP ID"