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
If `direnv` does not pick this up after saving the file, type
@@ -220,10 +220,10 @@ Deployed production API endpoints and docs are found by following links here: `h
220
220
221
221
3. To run all USAspending tests in the docker services run
222
222
```shell
223
-
docker compose run --rm -e DATA_BROKER_DATABASE_URL='' usaspending-test
223
+
docker compose run --rm -e BROKER_DB='' usaspending-test
224
224
```
225
225
226
-
_**NOTE**: If an env var named `DATA_BROKER_DATABASE_URL` is set, Broker Integration tests will attempt to be run as well. If doing so, Broker dependencies must be met (see below) or ALL tests will fail hard. Running the above command with `-e DATA_BROKER_DATABASE_URL=''` is a precaution to keep them excluded, unless you really want them (see below if so)._
226
+
_**NOTE**: If an env var named `BROKER_DB` is set, Broker Integration tests will attempt to be run as well. If doing so, Broker dependencies must be met (see below) or ALL tests will fail hard. Running the above command with `-e BROKER_DB=''` is a precaution to keep them excluded, unless you really want them (see below if so)._
227
227
228
228
To run tests locally and not in the docker services, you need:
229
229
@@ -273,7 +273,7 @@ To satisfy these dependencies and include execution of these tests, do the follo
1. Ensure you have the `DATA_BROKER_DATABASE_URL` environment variable set, and it points to what will be a live PostgreSQL server (no database required) at the time tests are run.
276
+
1. Ensure you have the `BROKER_DB` environment variable set, and it points to what will be a live PostgreSQL server (no database required) at the time tests are run.
277
277
1. _WARNING: If this is set at all, then ALL above dependencies must be met or ALL tests will fail (Django will try this connection on ALL tests' run)_
278
278
1. This DB could be one you always have running in a local Postgres instance, or one you spin up in a Docker container just before tests are run
279
279
1. If invoking `pytest` within a docker container (e.g. using the `usaspending-test` container), you _must_ mount the host's docker socket. This is declared already in the `docker-compose.yml` file services, but would be done manually with: `-v /var/run/docker.sock:/var/run/docker.sock`
@@ -286,15 +286,15 @@ Re-running the test suite using `pytest -rs` with these dependencies satisfied s
286
286
287
287
_From within a container_
288
288
289
-
_**NOTE**: `DATA_BROKER_DATABASE_URL` is set in the `docker-compose.yml` file (and could pick up `.env` values, if set)_
289
+
_**NOTE**: `BROKER_DB` is set in the `docker-compose.yml` file (and could pick up `.env` values, if set)_
Copy file name to clipboardExpand all lines: loading_data.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -35,7 +35,7 @@ To load in the reference data, from the same directory as manage.py:
35
35
36
36
To load certified submission data from the broker, you will need a read-only (or higher) connection string to the broker PostgreSQL database. If not running locally, you will also need to ensure your IP address has been whitelisted in the appropriate AWS Security Groups. Set this environment variable before running the **load_submission** command:
0 commit comments