Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs(broker): Describe what Broker does and how to interact with it #571

Merged
merged 23 commits into from
Sep 20, 2023
Merged
Show file tree
Hide file tree
Changes from 9 commits
Commits
Show all changes
23 commits
Select commit Hold shift + click to select a range
06df14c
docs(broker): Describe what Broker does and how to interact with it
lukehesluke Sep 12, 2023
9d2608b
morrrre
lukehesluke Sep 12, 2023
88f6dd6
finished all API endpoints ---.---
lukehesluke Sep 13, 2023
d90f622
completed concepts and summary, linking with API
lukehesluke Sep 13, 2023
038ea9f
.
lukehesluke Sep 13, 2023
3665c04
.
lukehesluke Sep 13, 2023
d7ea91a
.
lukehesluke Sep 13, 2023
149ca30
.
lukehesluke Sep 13, 2023
d24a601
.
lukehesluke Sep 13, 2023
0f46229
some review comments
lukehesluke Sep 19, 2023
1e3307e
Merge remote-tracking branch 'origin/master' into feature/broker-func…
lukehesluke Sep 19, 2023
d1ac9a5
headlessAuth puppeteer setting elaboration
lukehesluke Sep 19, 2023
6cdaa44
include tip with description of status report for non-found criteria
lukehesluke Sep 19, 2023
b4dc173
consistency of reference
lukehesluke Sep 19, 2023
75cd21b
improve sellerTaxModeNet criteria msg
lukehesluke Sep 19, 2023
efad4d5
Merge branch 'feature/broker-functionality-docs' of github.com:openac…
lukehesluke Sep 19, 2023
0ccfb9f
if it references one that exists
lukehesluke Sep 19, 2023
68365d3
create order listener response example
lukehesluke Sep 19, 2023
6329db9
need to be -> are
lukehesluke Sep 19, 2023
27712a4
how opps get into buckets
lukehesluke Sep 19, 2023
0e4b2f1
Merge branch 'feature/broker-functionality-docs' of github.com:openac…
lukehesluke Sep 19, 2023
831050b
failed -> was not met
lukehesluke Sep 19, 2023
2216226
no "default behaviour"
lukehesluke Sep 19, 2023
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -31,13 +31,16 @@ Note that the above command only runs the "core" tests within the test suite, wh
The hosted OpenActive Reference Implementation is running on a basic developer tier Azure instance with a burst quota, so it will not handle the load of a test suite run for all tests (hence `npm start -- core`); if the hosted application shuts down, simply wait 5 minutes and try again.

## Configuration

In order to run the test suite against your own implementation, configure the test suite by creating a copy of [`config/default.json`](./config/default.json) named `config/{NODE_ENV}.json` (where `{NODE_ENV}` is the value of your `NODE_ENV` environment variable), including the following properties:
- [`broker` microservice configuration](./packages/openactive-broker-microservice/#configuration-for-broker-within-confignode_envjson)
- [`integrationTests` and `sellers` configuration](./packages/openactive-integration-tests/#configuration-for-integrationtests-within-confignode_envjson)

The test suite uses the file `config/{NODE_ENV}.json` to override the settings in `default.json`. It is recommended that for development and deployment a such a new file is created instead of making changes to the `default.json` file, so that any new required settings that are added in future versions can be automatically updated in `default.json`.
The test suite uses the file `config/{NODE_ENV}.json` to override the settings in `default.json`. For development and deployment create a new file instead of making changes to the `default.json` file, so that any new required settings that are added in future versions can be automatically updated in `default.json`.

For more information about this use of `NODE_ENV` see this [documentation](https://github.com/lorenwest/node-config/wiki/Environment-Variables#node_env).

For more information see this [documentation](https://github.com/lorenwest/node-config/wiki/Environment-Variables#node_env).
By convention, much of the documentation assumes you to have created a `config/dev.json` file, which Test Suite will use when env var `NODE_ENV=dev`. But you can use any name you like, and have multiple configuration files for different environments.

## Installation

Expand Down
6 changes: 6 additions & 0 deletions packages/openactive-broker-microservice/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
# Contributing

## Keeping Documentation up-to-date

* **If changing Broker Microservice's API** e.g. adding new endpoints or query params:
* Please update the [Broker Microservice API](./README.md#broker-microservice-api) section of the README.
Loading
Loading