From 5fdb5274e52f151fd6f7eac1edabc165f81ecc2e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ma=C5=82gorzata=20=C5=9Awieca?= Date: Mon, 15 Jan 2024 16:13:06 +0100 Subject: [PATCH] Update tabs config (#395) * Update tabs config * Add tab end --- .../evnt-02-subs-with-multiple-filters.md | 25 +++++++------------ docs/user/tutorials/evnt-03-type-cleanup.md | 12 ++++----- .../evnt-04-change-max-in-flight-in-sub.md | 12 ++++----- .../tutorials/evnt-05-send-legacy-events.md | 4 +-- 4 files changed, 23 insertions(+), 30 deletions(-) diff --git a/docs/user/tutorials/evnt-02-subs-with-multiple-filters.md b/docs/user/tutorials/evnt-02-subs-with-multiple-filters.md index cb4190dc..88ef6eb7 100644 --- a/docs/user/tutorials/evnt-02-subs-with-multiple-filters.md +++ b/docs/user/tutorials/evnt-02-subs-with-multiple-filters.md @@ -13,11 +13,9 @@ The [Subscription](../resources/evnt-cr-subscription.md) CustomResourceDefinitio To subscribe to multiple events, you need a [Subscription](../resources/evnt-cr-subscription.md) custom resource (CR). In the following example, you learn how to subscribe to events of two types: `order.received.v1` and `order.changed.v1`. -
-
- - Kyma Dashboard - + + +#### **Kyma Dashboard** 1. Go to **Namespaces** and select the default namespace. 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**. @@ -33,11 +31,7 @@ To subscribe to multiple events, you need a [Subscription](../resources/evnt-cr- 4. Click **Create**. 5. Wait a few seconds for the Subscription to have status `READY`. -
-
- - kubectl - +#### **kubectl** Run: @@ -65,8 +59,7 @@ kubectl get subscriptions lastorder-sub -o=jsonpath="{.status.ready}" The operation was successful if the returned status says `true`. -
-
+ ## Trigger the workload with an event @@ -83,7 +76,7 @@ In the following example, you port-forward the [Event Publisher Proxy](../evnt-a -#### CloudEvents Conformance Tool +#### **CloudEvents Conformance Tool** ```bash cloudevents send http://localhost:3000/publish \ @@ -95,7 +88,7 @@ cloudevents send http://localhost:3000/publish \ --yaml ``` -#### curl +#### **curl** ```bash curl -v -X POST \ @@ -115,7 +108,7 @@ curl -v -X POST \ -#### CloudEvents Conformance Tool +#### **CloudEvents Conformance Tool** ```bash cloudevents send http://localhost:3000/publish \ @@ -127,7 +120,7 @@ cloudevents send http://localhost:3000/publish \ --yaml ``` -#### curl +#### **curl** ```bash curl -v -X POST \ diff --git a/docs/user/tutorials/evnt-03-type-cleanup.md b/docs/user/tutorials/evnt-03-type-cleanup.md index 9dcf5318..0533796c 100644 --- a/docs/user/tutorials/evnt-03-type-cleanup.md +++ b/docs/user/tutorials/evnt-03-type-cleanup.md @@ -13,7 +13,7 @@ You learn how Eventing behaves when you create a [Subscription](../resources/evn -#### Kyma Dashboard +#### **Kyma Dashboard** ```js module.exports = { @@ -24,7 +24,7 @@ module.exports = { } ``` -#### kubectl +#### **kubectl** ```bash cat < -#### Kyma Dashboard +#### **Kyma Dashboard** 1. Go to **Namespaces** and select the default namespace. 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**. @@ -74,7 +74,7 @@ Create a [Subscription](../resources/evnt-cr-subscription.md) custom resource (C 4. Click **Create**. 5. Wait a few seconds for the Subscription to have status `READY`. -#### kubectl +#### **kubectl** Run: @@ -128,7 +128,7 @@ Next, you see that you can still publish events with the original Event name (i. -#### CloudEvents Conformance Tool +#### **CloudEvents Conformance Tool** ```bash cloudevents send http://localhost:3000/publish \ @@ -140,7 +140,7 @@ cloudevents send http://localhost:3000/publish \ --yaml ``` -#### curl +#### **curl** ```bash curl -v -X POST \ diff --git a/docs/user/tutorials/evnt-04-change-max-in-flight-in-sub.md b/docs/user/tutorials/evnt-04-change-max-in-flight-in-sub.md index 8d73baab..6a7917f8 100644 --- a/docs/user/tutorials/evnt-04-change-max-in-flight-in-sub.md +++ b/docs/user/tutorials/evnt-04-change-max-in-flight-in-sub.md @@ -13,7 +13,7 @@ The "in-flight messages" config defines the number of events that Kyma Eventing -#### Kyma Dashboard +#### **Kyma Dashboard** ```js module.exports = { @@ -27,7 +27,7 @@ module.exports = { } ``` -#### kubectl +#### **kubectl** ```bash cat < -#### Kyma Dashboard +#### **Kyma Dashboard** 1. Go to **Namespaces** and select the default namespace. 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**. @@ -82,7 +82,7 @@ Create a [Subscription](../resources/evnt-cr-subscription.md) custom resource (C 4. Click **Create**. 5. Wait a few seconds for the Subscription to have status `READY`. -#### kubectl +#### **kubectl** Run: @@ -128,7 +128,7 @@ Next, publish 15 events at once and see how Kyma Eventing triggers the workload. -#### CloudEvents Conformance Tool +#### **CloudEvents Conformance Tool** ```bash for i in {1..15} @@ -143,7 +143,7 @@ do done ``` -#### curl +#### **curl** ```bash for i in {1..15} diff --git a/docs/user/tutorials/evnt-05-send-legacy-events.md b/docs/user/tutorials/evnt-05-send-legacy-events.md index 3fb82f90..5fefdbae 100644 --- a/docs/user/tutorials/evnt-05-send-legacy-events.md +++ b/docs/user/tutorials/evnt-05-send-legacy-events.md @@ -17,7 +17,7 @@ To subscribe to events, we need a [Subscription](../resources/evnt-cr-subscripti -#### Kyma Dashboard +#### **Kyma Dashboard** 1. Go to **Namespaces** and select the default namespace. 2. Go to **Configuration** > **Subscriptions** and click **Create Subscription+**. @@ -31,7 +31,7 @@ To subscribe to events, we need a [Subscription](../resources/evnt-cr-subscripti 4. Click **Create**. 5. Wait a few seconds for the Subscription to have status `READY`. -#### curl +#### **curl** Run: