…est.yaml

This allows us to fully mock the Eventbus instance used when testing,
while still piping events through the same functions used
for prod by creating them in eventbus-init-utils.js

to be compatible with node 6

This makes configuration of Eventbus for the route cleaner.  Instead
of the app.conf.eventbus_init_module exporting both an Eventbus instance
and a createEventError function, it only needs to export the Eventbus instance.
createEventError is given to the Eventbus constructor, and Eventbus
handles event error processing.

- schema_field -> schema_uri_field
- config file cleanup
- allow protocol less uris, assume these are local file paths

Ajv already caches its compiled validators (and schemas) by
$id. This makes it really handy to look up event schemas if
their schema URIs match the schema's $id property.

$refs get a little tricky, but I think I got it.  Unfortunetly,
in order to properly resolve, we need to make event schema $schema
URIs start with /, other wise $ref that point at schemas will not
be correct.

objectGet just wraps _.get, but throws PropertyNotFoundError
if undefined.

Also fix test logging to make it easier to enable logging
output during tests.

TODO: update README docs about this

…mmit

Also throw EventSchemaLoadError when schema fails loading from uri

Makes things easier to customize

Makes it clearer what these function generators are doing.

This makes it more clear as to what the default-eventbus is and what it is doing.
Individual function makers are renamed to make*, and they are exported
along with the default eventbus factory function for reuse elsewhere.

This allows implementers of mapToEventError to decide which
types of event errors they want to be produced to the error topic.

lib/errors.js should have been added days ago

+ some lines in .gitignore

+ some lines in .gitignore

This adds some extra default behavior if events don't have stream
or topic names in them.  This makes the explanation and usage
of a default eventbus install simpler; The 'only' extra information
clients need to include in their events is the schema URI.
If stream_field is not configued, Extracted schema URIs will be
sanitized and used as the Kafka topic.

This allows for users of Eventbus (like the service template route)
to pass in extra context for validate() and produce() implementaitons
to use.

This is used by wikimedia-eventbus to instantiate two different
Kafka producers, a guarunteed and a 'hasty' producer, to use
for both reliable and fire and forget ?hasty=true cases.

default-eventbus changes:
- remove topic_prefix support
- remove partition_field support
- remove key_field support
- remove HastyKafkaProducer support
- remove id_field support

wikimedia-eventbus changes:
- remove schema_uri -> stream name default mapping; all events must have stream_name
- topic_prefix, id_field and HastyKafkaProducer support moved into wikimedia-eventbus

This removes the restriction that schema URIs match exactly $id fields.

This allows us to use the title rather to ensure that an event
of a particular schema is allowed in the stream, rather than
relying on the schema_uri.  The title will be more consistent
and canonical than schema_uris, which might change due to location
moving, etc.

Also refactory wikimedia-eventbus a bit to simplify.

we can consider implementing this if we have a use case

The default Ajv instance knows about the Draft 7 JSONSchema meta schema,
but does not on its own include meta schemas for other JSONSchema drafts.
Schemas should point to their meta schema in the $schema field.
JSONSChema meta schemas are self validating, so they have their
$id fields and $schema fields set to the same URL.  If Ajv
does not yet have a meta schema referneced by that URL, this will
cause infinite recursion as our loadSchema implementation will
look up remote schemas by $id.

This patch adds a option for EventValidator to match $id schema URLs
as being meta schemas, instead of data (event) schemas.  If a schema's
URL matches, it will be added as a meta schema to Ajv, breaking the
infinite recursion.

---

This patch also includes a change to the default-eventgate schema_uri_field
option.  If this is given as an array, the event will be searched for
the field names in the array when extracting a schema uri.

Both of thse changes allow wikimedia to support draft 4 events
with schema URIs at meta.schema_uri, as well as new draft 7 ones
we will make with schema URIs at $schema.

…entgate

…nctions