Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 2 additions & 2 deletions content/documentation/explanations/async-triggers.md
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,9 @@ The important things to notice here:
Specifying a trigger using above notation has the following consequences:

1. Upon the execution of a mock for the `POST /register` operation, the original request and response will be captured before the response is sent back to the caller,
2. Request and response will then be transfered asynchronously to the [Microcks Aync Minion component](/documentation/explanations/deployment-options/#complete-logical-architecture) with the information on the services, versions and operations to trigger,
2. Request and response will then be transferred asynchronously to the [Microcks Aync Minion component](/documentation/explanations/deployment-options/#complete-logical-architecture) with the information on the services, versions and operations to trigger,
3. The Async Minion will then take care of selecting the appropriate asynchronous service operatino and will try to find a **contextualized message** within this operation,
4. If such a **contextualized message** is found, then it will be rendered and it will be sent over all the procotol bindings that are available for this asynchronous service (Kafka, WebSocket, etc.)
4. If such a **contextualized message** is found, then it will be rendered and it will be sent over all the protocol bindings that are available for this asynchronous service (Kafka, WebSocket, etc.)

Now you may wonder: what is a **contextualized message**? 🧐

Expand Down
2 changes: 1 addition & 1 deletion content/documentation/guides/usage/openapi-webhooks.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ Let's take the example of a Petstore event stream for new pets registration!

## 1. An Example

The `Petstore Webhooks` API declares a single webhook to allow consumers to receive information about new pets avaialble into our store. A pet definition is simplictic here: it has an `id`, a `name` and a `tag` (either a cat or a dog).
The `Petstore Webhooks` API declares a single webhook to allow consumers to receive information about new pets available into our store. A pet definition is simplistic here: it has an `id`, a `name` and a `tag` (either a cat or a dog).

Bolow is an example on how you would define this with OpenAPI Spec. You can get our full [`Petstore-webhooks-openapi.yaml`](https://github.com/microcks/microcks/blob/1.13.x/samples/Petstore-webhooks-openapi.yaml) file from our samples.

Expand Down
Loading