add information on how to run tests

Author: Vlasis-Perdikidis

.env.template

@@ -2,7 +2,7 @@
 GITHUB_TOKEN=
 
 # Apigee proxy name to be used for test execution
-# nhs-notify-supplier--internal-dev--nhs-notify-supplier-PR-XX
+# nhs-notify-supplier--internal-dev--nhs-notify-supplier-prxxx
 PROXY_NAME=
 
 # APIM env to run e2e tests against, other options are: ref, int, prod
@@ -25,17 +25,30 @@ TARGET_ENVIRONMENT=prxx
 # API Keys
 # ========
 # In order to find out the value of an environments given API key, follow these steps
-# 1. Log in to Non-Prod
-# 2. Navigate to 'Publish' > 'Apps' and search for the app linked to authentication
-# 3. Copy the "key" from the Credentials related to the app
+# 1. Log in to the AWS NHS Notify Suppliers Dev account
+# 2. Open the paramenter store and search for the parameter /dev/e2e/keys/apim/pr
+# 3. Copy the decrypted "value"
 # Note: For INT and higher environments use developer portal https://identity.prod.api.platform.nhs.uk/
 export NON_PROD_API_KEY=xxx
 export INTEGRATION_API_KEY=xxx
 export PRODUCTION_API_KEY=xxx
+
+# Status Endpoint API Key
+# In order to find the value of the status endpoint API key, follow these steps:
+# 1. Log in to the AWS NHS Notify Suppliers Dev account
+# 2. Open the paramenter store and search for the parameter /dev/e2e/keys/apim/status
+# 3. Copy the decrypted "value"
 export STATUS_ENDPOINT_API_KEY=xxx
 
 # Private Keys
 # ============
+# In order to set the NON_PROD_PRIVATE_KEY, follow these steps:
+# 1. Log in to the AWS NHS Notify Suppliers Dev account
+# 2. Open the paramenter store and search for the parameter /dev/e2e/keys/private
+# 3. Copy the decrypted "value"
+# 4. Create a .pem file and paste the value copied in step 3,
+#    save the file and provide the path to the file as the value for NON_PROD_PRIVATE_KEY
+#    for example /workspaces/nhs-notify-supplier-api/scripts/JWT/internal-dev-test-1.pem
 # private key path used to generate authentication for tests ran against the internal-dev and internal-qa
 export NON_PROD_PRIVATE_KEY=xxx
 # private key path used to generate authentication for tests ran against the int environment

.gitignore

@@ -13,6 +13,7 @@ version.json
 # Please, add your custom content below!
 .idea
 .env
+.devcontainer/devcontainer-lock.json
 
 # dependencies
 node_modules

CONTRIBUTING.md

@@ -1,4 +1,6 @@
-## Contributing to NHS Notify Supplier API
+<!-- vale off -->
+
+# Contributing to NHS Notify Supplier API
 
 ## Feature Branches
 
@@ -51,3 +53,5 @@ You can test your branch in a dynamic environment prior to merging to `main`. Th
 Each Lambda and internal package has a `README.md` alongside the source describing its purpose, flow, integration points, and peculiarities. These are bundled into the docs site via `docs/generate-includes.sh`.
 
 When making changes to a Lambda or internal package, check whether the corresponding README needs updating. Function documentation is not auto-generated and can become stale if not maintained alongside code changes.
+
+<!-- vale on -->

config/suppliers/README.md

@@ -1,3 +1,5 @@
+<!-- vale off -->
+
 # Supplier Configuration
 
 ## Purpose
@@ -6,14 +8,14 @@ Static JSON configuration files that define the supplier allocation rules for th
 
 ## Configuration Entities
 
-| Entity | Directory | Description |
-| --- | --- | --- |
-| **Supplier** | `supplier/` | Print supplier definitions with ID, name, channel type, daily capacity, and status (PROD/DRAFT) |
-| **Letter Variant** | `letter-variant/` | Letter type definitions with physical constraints (sheets, sides, ink coverage, delivery days), associated pack specification IDs, and volume group assignment |
-| **Volume Group** | `volume-group/` | Groupings of letter variants for allocation purposes, with status and date range validity |
-| **Supplier Allocation** | `supplier-allocation/` | Maps a supplier to a volume group with a target `allocationPercentage` and status |
-| **Pack Specification** | `pack-specification/` | Detailed print assembly specs (paper, envelope, print colour, duplex) with constraints and billing ID |
-| **Supplier Pack** | `supplier-pack/` | Links a supplier to a pack specification with approval status |
+| Entity                  | Directory              | Description                                                                                                                                                    |
+| ----------------------- | ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| **Supplier**            | `supplier/`            | Print supplier definitions with ID, name, channel type, daily capacity, and status (PROD/DRAFT)                                                                |
+| **Letter Variant**      | `letter-variant/`      | Letter type definitions with physical constraints (sheets, sides, ink coverage, delivery days), associated pack specification IDs, and volume group assignment |
+| **Volume Group**        | `volume-group/`        | Groupings of letter variants for allocation purposes, with status and date range validity                                                                      |
+| **Supplier Allocation** | `supplier-allocation/` | Maps a supplier to a volume group with a target `allocationPercentage` and status                                                                              |
+| **Pack Specification**  | `pack-specification/`  | Detailed print assembly specs (paper, envelope, print colour, duplex) with constraints and billing ID                                                          |
+| **Supplier Pack**       | `supplier-pack/`       | Links a supplier to a pack specification with approval status                                                                                                  |
 
 ## Allocation Lookup Chain
 
@@ -33,3 +35,5 @@ When the `supplier-allocator` Lambda processes a `LetterRequestPreparedEvent`:
 - `status: "PROD"` is required at multiple levels (supplier, volume group, allocation) for an allocation to be active.
 - Volume groups have `startDate` (and optional `endDate`) fields. Allocations are only valid when the current date falls within this range (evaluated in London timezone).
 - Supplier `dailyCapacity` is tracked separately in `SUPPLIER_QUOTAS_TABLE` and resets at midnight London time. It is not stored in these config files.
+
+<!-- vale on -->