You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ In order to do this, make sure you have AWS CLI installed and configured, then r
65
65
make ENV=env truststore-pull-all
66
66
```
67
67
68
-
Where `env` is one of `dev`, `qa` , `int`, `ref` or `prod`.
68
+
Where `env` is one of `dev`, `qa` , `int`, `perftest`, `ref` or `prod`.
69
69
70
70
## Getting Started
71
71
@@ -414,7 +414,7 @@ If the Producer API has changed, or the documentation for that API has changed,
414
414
415
415
Once you have a new release version ready, you can deploy it through our environments as follows:
416
416
417
-
1. Use the "Persistent Environment Deploy" Github Action workflow to deploy the release tag to `dev`, `dev-sandbox`, `qa`, `qa-sandbox`, `int` and `int-sandbox` environments.
417
+
1. Use the "Persistent Environment Deploy" Github Action workflow to deploy the release tag to `dev`, `dev-sandbox`, `qa`, `qa-sandbox`, `int`, `int-sandbox` and `perftest` environments.
418
418
2. If any issues arise in the deployment, fix the issues, create a new release version and start this process again.
419
419
3. Once the deployments are complete, use the "Persistent Environment Deploy" Github Action workflow to deploy the release version to `ref`.
420
420
4. Once that is complete, use the "Persistent Environment Deploy" workflow to deploy the release version to `prod`.
0 commit comments