a097a0ce61
New designs call for a streamlined New Portfolio page, with far fewer input options. This commit refactors that page according to those designs. Some of the route functions in this commit refer to a "step 1" of creating a new Portfolio. Though there is no "step 2" right now, the designs call for a multistep flow for Portfolio creation process, so this commit sets the stage for that.
Load Testing
We're using Locust.io for our load tests. The tests can be run locally or in a VM.
Available Option (Env Vars)
TARGET_URL - The host address that locust should load test against
- If you're running the app locally http://docker.for.mac.localhost:8000
- This is for running on a mac, you may need to use other methods to get the container to communicate with localhost on other systems
- Staging - https://staging.atat.code.mil
- Prod - https://azure.atat.code.mil
DISABLE_VERIFY - False by default, set to true to prevent SSL verification
ATAT_BA_USERNAME + ATAT_BA_PASSWORD - Username and password for the basic auth on the staging and production sites
To Run Locally
-
Build the docker container:
docker build . -t pwatat.azurecr.io/loadtest/locust -
Run the container:
docker run --rm -p 8089:8089 \ -e TARGET_URL=https://staging.atat.code.mil \ -e DISABLE_VERIFY=false \ -e ATAT_BA_USERNAME=<username> \ -e ATAT_BA_PASSWORD=<password> \ --name locust pwatat.azurecr.io/loadtest/locust:latest
To Update Image
-
Build the docker container:
docker build . -t pwatat.azurecr.io/loadtest/locust -
Push to our container registry
docker push pwatat.azurecr.io/loadtest/locust-
If you get an authorization failed message, you may need to re-authorize with this command first:
az acr login --name pwatat
-
-
Restart the
atat-load-testapp service in the azure portal- Note the load test service is running on a free tier VM, so it will likely be paused. Start it up and press restart to referesh before beginning your load testing.