Skip to content
Update local workflow - Added comments around the new VS lanuch configs authored by Kim Carter's avatar Kim Carter
......@@ -9,6 +9,8 @@ Leaving `docker stats` running in a terminal is often useful to see which contai
Adding the `--debug` flag to the end of `sam local` commands can be helpful.
We have tried [these launch configurations](https://aws.amazon.com/blogs/developer/introducing-launch-configurations-support-for-sam-debugging-in-the-aws-toolkit-for-vs-code/). The fact that you are expected to add your environment variables in yet another place, specify your runtime again, and add your event again, along with the fact that some environment variables would override and some wouldn't was enough to make us stick with our existing VS Code launch configurations.
## Testing the [`provisionAppSlaves`](https://gitlab.com/purpleteam-labs/purpleteam-lambda/-/blob/master/local/app-slave-provisioner/index.js)
1. Terminal 1: Run docker-compose-ui from the `purpleteam-s2-containers/` root directory. Run the following command:
......
......