Merge pull request #29135 from Srivaralakshmi/odcsrvls

Author: adellape

modules/odc-creating-apiserversource.adoc

@@ -7,19 +7,25 @@
 
 .Procedure
 
-. Navigate to the **Add** page and select **Event Source**.
-. In the **Event Sources** page, select **ApiServerSource** in the **Type** section.
-. Configure the **ApiServerSource** settings:
-.. Enter `v1` as the **APIVERSION**, and `Event` as the **KIND**.
-// .. Select **Resource** as the **Mode**. **Mode** is the mode that the receive adapter controller runs in. `Ref` sends only the reference to the resource. `Resource` sends the full resource.
+. In the *Developer* perspective, navigate to *+Add* → *Event Source*. The  *Event Sources* page is displayed.
+. Optional: If you have multiple providers for your event sources, select the required provider from the *Providers* list to filter the available event sources from the provider.
+. Select *ApiServerSource* and then click *Create Event Source*. The  *Create Event Source* page is displayed.
+. Configure the *ApiServerSource* settings by using the *Form view* or *YAML view*:
++
+[NOTE]
+====
+You can switch between the *Form view* and *YAML view*. The data is persisted when switching between the views.
+====
+.. Enter `v1` as the *APIVERSION* and `Event` as the *KIND*.
+// .. Select *Resource* as the *Mode*. *Mode* is the mode that the receive adapter controller runs in. `Ref` sends only the reference to the resource. `Resource` sends the full resource.
 // TODO: clarify what this is used for. Out of scope for this PR since not required.
-.. Select the **Service Account Name** for the service account that you created.
-.. Select the **Sink** for the event source. A **Sink** can be either a **Resource**, such as a channel, broker, or service, or a **URI**.
-. Click **Create**.
+.. Select the *Service Account Name* for the service account that you created.
+.. Select the *Sink* for the event source. A *Sink* can be either a *Resource*, such as a channel, broker, or service, or a *URI*.
+. Click *Create*.
 
 .Verification steps
 
-* After you have created the ApiServerSource, you will see it connected to the service it is sinked to in the **Topology** view.
+* After you have created the ApiServerSource, you will see it connected to the service it is sinked to in the *Topology* view.
 +
 image::toplogy-odc-apiserver.png[ApiServerSource Topology view]
 
@@ -32,7 +38,7 @@ If a URI sink is used, modify the URI by right-clicking on *URI sink* -> *Edit U
 
 .Procedure
 
-. Navigate to the **Topology** view.
-. Right-click the ApiServerSource and select **Delete ApiServerSource**.
+. Navigate to the *Topology* view.
+. Right-click the ApiServerSource and select *Delete ApiServerSource*.
 +
 image::delete-apiserversource-odc.png[Delete the ApiServerSource]

modules/serverless-pingsource-kn.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * serverless/event_workflows/serverless-pingsource.adoc
+// * serverless/event_sources/serverless-pingsource.adoc
 
 [id="serverless-pingsource-kn_{context}"]
 = Using a PingSource with the `kn` CLI

modules/serverless-pingsource-odc.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * serverless/event_workflows/serverless-pingsource.adoc
+// * serverless/event_sources/serverless-pingsource.adoc
 
 [id="serverless-pingsource-odc_{context}"]
 = Creating a PingSource using the Developer Perspective
@@ -39,8 +39,14 @@ spec:
 .. Click *Create*.
 
 . Create a PingSource in the same namespace as the service created in the previous step, or any other sink that you want to send events to.
-.. In the *Developer* perspective, navigate to *+Add* -> *Event Source*.
-.. Select *Ping Source*.
+.. In the *Developer* perspective, navigate to *+Add* -> *Event Source*. The  *Event Sources* page is displayed.
+.. Optional: If you have multiple providers for your event sources, select the required provider from the *Providers* list to filter the available event sources from the provider.
+.. Select *Ping Source* and then click *Create Event Source*. The *Create Event Source* page is displayed.
++
+[NOTE]
+====
+You can configure the *PingSource* settings by using the *Form view* or *YAML view* and can switch between the views. The data is persisted when switching between the views.
+====
 .. Enter a value for *Schedule*. In this example, the value is `*/2 * * * *`, which creates a PingSource that sends a message every two minutes.
 .. Optional: You can enter a value for *Data*, which is the message payload.
 .. Select a *Sink*. This can be either a *Resource* or a *URI*. In this example, the `event-display` service created in the previous step is used as the *Resource* sink.

modules/serverless-pingsource-yaml.adoc

@@ -1,6 +1,6 @@
 // Module included in the following assemblies:
 //
-// * serverless/event_workflows/serverless-pingsource.adoc
+// * serverless/event_sources/serverless-pingsource.adoc
 
 [id="serverless-pingsource-yaml_{context}"]
 = Using a PingSource with YAML