Kevin Bader
Kevin Bader
## CloudEvents 1.0 Consider this example, straight from the spec: ```json { ... "datacontenttype" : "text/xml", "data" : "" } ``` Clearly, `data` is some structure that has been encoded...
## Problem description c4builder currently assumes that markdown files don't use h1 (`#`) and h2 (`##`) headers. For example: If you don't know this, you might be tempted to start...
By ignoring the output folder (DIST_FOLDER), we allow a user to use the top-level directory as the source folder (ROOT_FOLDER). This is useful when the top-level README file provides introduction...
Repositories typically have a top-level README file that explains what the project is about and how to get started using it. I think it would be helpful to re-use that...
Fixes #377. - For subscription requests, JWTs that can't be validated are now ignored. This allows to validate JWTs in an external service as configurable via the SUBMISSION_CHECK and SUBSCRIPTION_CHECK...
https://github.com/Accenture/reactive-interaction-gateway/blob/6543746a9008bb9ab81622309c4e4279e28adf9a/kinesis-client/src/main/java/com/accenture/rig/App.java#L68
The first release of the spec! https://github.com/cloudevents/spec/releases/tag/v1.0
In order to enhance the reliability of event transmission, the SSE endpoint should support the [`last-event-id`] field as sent by the client. The idea is to maintain a buffer of...
...as described in #102. The relevant environment variables are introduced by #124 (update: has been removed again temporarily, see a17f490174fb876a0eaeb0b83a846acf954d0bf2).
# A Refined Vision We're need to know what we're aiming at, and users need to know what they can expect from using RIG in their infrastructure. Given new requirements...