Routemaster Client v0.3.0 Routemaster.Config View Source
Centralized access to the client configuration.
Link to this section Summary
Functions
The HTTP Basic Authorization Header value to authenticate
requests to the event bus server. It’s derived from
a base64-encoded Config.bus_api_token
The API token to authenticate requests to the event bus server
The HTTPS URL of the Routemaster event bus server
The cache TTL, as an integer number of seconds represented as a string. Defaults to one day (86400 seconds)
Options passed to the Director’s hackney adapter.
See the hackney docs
for more details
The auth token used by the Drain to authenticate incoming HTTP requests. This token is specific to this application (an event consumer, AKA subscriber)
The HTTPS URL where this application will mount the Drain app. This is usually a path, and that is where the event bus server will send HTTP POST requests to deliver events
Options passed to the Fetcher’s hackney adapter.
See the hackney docs
for more details
Options passed to the Publisher’s hackney adapter.
See the hackney docs
for more details
Returns the connection condfiguration for Redis. It could be either a Keyword List of parameters or a binary URI
Authentication credentials for other services with which we’re going to interact. These are usually the origins or sources of the entities linked to in the events
For the given hostname, it returns a HTTP Authorization header value.
The hostname must be found in the credentials Map returned by
service_auth_credentials/0
The user-agent HTTP header used when talking with the bus server and when fetching entities from their URLs
Link to this section Functions
The HTTP Basic Authorization Header value to authenticate
requests to the event bus server. It’s derived from
a base64-encoded Config.bus_api_token.
The API token to authenticate requests to the event bus server.
The HTTPS URL of the Routemaster event bus server.
The cache TTL, as an integer number of seconds represented as a string. Defaults to one day (86400 seconds).
Options passed to the Director’s hackney adapter.
See the hackney docs
for more details.
The auth token used by the Drain to authenticate incoming HTTP requests. This token is specific to this application (an event consumer, AKA subscriber).
This token is sent to the event bus server when subscribing to topics, where it will be stored with this subscriber’s metadata. Later, when delivering events, the server will send it back in the HTTP Authorization header of the POST requests to this drain.
The HTTPS URL where this application will mount the Drain app. This is usually a path, and that is where the event bus server will send HTTP POST requests to deliver events.
This URL is sent to the event bus server when subscribing to topics.
Options passed to the Fetcher’s hackney adapter.
See the hackney docs
for more details.
Options passed to the Publisher’s hackney adapter.
See the hackney docs
for more details.
Returns the connection condfiguration for Redis. It could be either a Keyword List of parameters or a binary URI.
Authentication credentials for other services with which we’re going to interact. These are usually the origins or sources of the entities linked to in the events.
It returns a Map where the keys are the hostnames of the other services (binaries) and the values are the pre-built values for the HTTP Authorization header.
The credentials need to be configured beforehand.
For the given hostname, it returns a HTTP Authorization header value.
The hostname must be found in the credentials Map returned by
service_auth_credentials/0
The user-agent HTTP header used when talking with the bus server and when fetching entities from their URLs.