local/local-workflow.md

@@ -90,11 +90,11 @@ No local Lambda service needs to be running first, in our case:
 2. Then simply run one of the following [`sam local invoke`](https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/sam-cli-command-reference-sam-local-invoke.html) commands:  
    * For `provisionAppSlaves`, from the `purpleteam-lambda/` root directory, run the following command:  
      ```shell
-     echo '<same-JSON-payload-as-above>' | sam local invoke --event - --docker-network compose_pt-net provisionAppSlaves
+     echo '<same-JSON-payload-as-above>' | sam local invoke --event - --env-vars local/env.json --docker-network compose_pt-net provisionAppSlaves
      ```
    * For `provisionSeleniumStandalones`, from the `purpleteam-lambda/` root directory, run the following command:  
      ```shell
-     echo '<same-JSON-payload-as-above>' | sam local invoke --event - --docker-network compose_pt-net provisionSeleniumStandalones
+     echo '<same-JSON-payload-as-above>' | sam local invoke --event - --env-vars local/env.json --docker-network compose_pt-net provisionSeleniumStandalones
      ```
 3. Then check that conatiners are running as already discussed
 4. Bring them down again as already discussed