From b0b467f29739e02ad2ffbed514d7362777d2fc7f Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 20 May 2025 18:35:50 -0400 Subject: [PATCH 01/12] AAP-45886 Added a link to the interact demo in the SER chapter in EDA user guide --- .../assemblies/eda/assembly-simplified-event-routing.adoc | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc index f3282408f1..ebe3c10647 100644 --- a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc +++ b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc @@ -16,7 +16,9 @@ include::eda/proc-eda-replace-sources-with-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-resend-webhook-data-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-check-rule-audit-event-stream.adoc[leveloffset=+1] - +[role="_additional-resources"] +.Additional resources +* To view an end-to-end demo of the simplified event routing process using event streams, see link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams]. From ce21b1e637fa4efea4e7b8d34c4ab993728b5d21 Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 20 May 2025 18:41:14 -0400 Subject: [PATCH 02/12] AAP-45886 Moved additional resources section further up in the assembly --- .../assemblies/eda/assembly-simplified-event-routing.adoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc index ebe3c10647..f2f8af226f 100644 --- a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc +++ b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc @@ -7,6 +7,10 @@ Simplified event routing enables {EDAcontroller} to capture and analyze data fro Event streams are an easy way to connect your sources to your rulebooks. This capability lets you create a single endpoint to receive alerts from an event source and then use the events in multiple rulebooks. +[role="_additional-resources"] +.Additional resources +* To view an end-to-end demo of the simplified event routing process using event streams, see link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams]. + include::eda/con-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-create-event-stream-credential.adoc[leveloffset=+1] include::eda/proc-eda-create-event-stream.adoc[leveloffset=+1] @@ -16,9 +20,7 @@ include::eda/proc-eda-replace-sources-with-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-resend-webhook-data-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-check-rule-audit-event-stream.adoc[leveloffset=+1] -[role="_additional-resources"] -.Additional resources -* To view an end-to-end demo of the simplified event routing process using event streams, see link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams]. + From 898c93af5c2ddf451cb7fa2e39adebe55d2d3967 Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 20:17:45 -0400 Subject: [PATCH 03/12] AAP-45886 First user scenario for GitHub event streams w/ EDA --- .../eda/assembiy-eda-user-examples.adoc | 22 +++++++++++++ ...da-user-examples-github-event-streams.adoc | 7 +++++ ...example-check-rule-audit-event-stream.adoc | 14 +++++++++ ...proc-eda-example-configure-remote-sys.adoc | 18 +++++++++++ ...c-eda-example-eda-github-event-stream.adoc | 17 ++++++++++ ...c-eda-example-github-eventstream-cred.adoc | 17 ++++++++++ ...-replace-sources-attach-event-streams.adoc | 31 +++++++++++++++++++ ...ple-resend-webhook-data-event-streams.adoc | 14 +++++++++ ...eda-example-verify-event-streams-work.adoc | 14 +++++++++ 9 files changed, 154 insertions(+) create mode 100644 downstream/assemblies/eda/assembiy-eda-user-examples.adoc create mode 100644 downstream/modules/eda/con-eda-user-examples-github-event-streams.adoc create mode 100644 downstream/modules/eda/proc-eda-example-check-rule-audit-event-stream.adoc create mode 100644 downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc create mode 100644 downstream/modules/eda/proc-eda-example-eda-github-event-stream.adoc create mode 100644 downstream/modules/eda/proc-eda-example-github-eventstream-cred.adoc create mode 100644 downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc create mode 100644 downstream/modules/eda/proc-eda-example-resend-webhook-data-event-streams.adoc create mode 100644 downstream/modules/eda/proc-eda-example-verify-event-streams-work.adoc diff --git a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc new file mode 100644 index 0000000000..2a7e25979b --- /dev/null +++ b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc @@ -0,0 +1,22 @@ +:_mod-docs-content-type: ASSEMBLY +[id="eda-user-examples"] + += {EDAName} user scenarios + +[role="_abstract"] + +The following content provides detailed scenarios and practical examples for leveraging event streams (such as GitHub, GitLab, ServiceNow, and Dynatrace) with rulebook activations to automate responses to specific events within your environment. Through these examples, you can experience how to configure and apply diverse integrations to streamline your automation workflows and enhance your system's responsiveness. + +include::eda/con-eda-user-examples-github-event-streams.adoc[leveloffset=+1] + +include::eda/proc-eda-example-github-eventstream-cred.adoc[leveloffset=+2] + +include::eda/proc-eda-example-eda-github-event-stream.adoc[leveloffset=+2] + +include::eda/proc-eda-example-configure-remote-sys.adoc[leveloffset=+2] + +include::eda/proc-eda-example-verify-event-streams-work.adoc[leveloffset=+2] + +include::eda/proc-eda-example-replace-sources-attach-event-streams.adoc[leveloffset=+2] + +include::eda/proc-eda-example-check-rule-audit-event-stream.adoc[leveloffset=+2] \ No newline at end of file diff --git a/downstream/modules/eda/con-eda-user-examples-github-event-streams.adoc b/downstream/modules/eda/con-eda-user-examples-github-event-streams.adoc new file mode 100644 index 0000000000..3db31e824a --- /dev/null +++ b/downstream/modules/eda/con-eda-user-examples-github-event-streams.adoc @@ -0,0 +1,7 @@ +:_mod-docs-content-type: CONCEPT +[id="eda-user-examples-github-event-streams"] + += Simplified Event Routing using GitHub event streams + +[role="_abstract"] +You can learn how to achieve end-to-end simplified event routing using GitHub event streams in the the following sections. The goal is to demonstrate how to efficiently capture, process, and route GitHub events for seamless integration with your automation workflows, ensuring your rulebooks react precisely to repository activities. \ No newline at end of file diff --git a/downstream/modules/eda/proc-eda-example-check-rule-audit-event-stream.adoc b/downstream/modules/eda/proc-eda-example-check-rule-audit-event-stream.adoc new file mode 100644 index 0000000000..9daec64e47 --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-check-rule-audit-event-stream.adoc @@ -0,0 +1,14 @@ +:_mod-docs-content-type: PROCEDURE +[id="eda-example-check-rule-audit-event-stream"] + += Check the Rule Audit for events on your new event stream + +You can check the Rule Audit for events associated with your new event stream, *Repo Event Stream*. This process guides you to locate and view the details of specific events and their actions, allowing you to verify event processing. + +.Procedure +. From the {PlatformNameShort} navigation panel, select {MenuADRuleAudit} to see the event and actions. +. Select the name of the event in the list that is associated with the rulebook activation you created. The Details tab is displayed. +. Click the *Events* tab to view the event details. + +//[JMSelf]Remove screen shot for now +//image:eda-rule-audit-event-streams.png[Rule audit - Event stream] diff --git a/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc b/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc new file mode 100644 index 0000000000..0149a8b217 --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc @@ -0,0 +1,18 @@ + +[id="eda-example-configure-remote-sys"] + += Configuring your remote system to send events + +Complete the following procedure to configure your remote system to send events by setting up a webhook in your GitHub repository. + +.Procedure + +. Go to your GitHub account to configure your event source. +. Click *Your profile name → Your repositories* and select the repository you want to configure. +. Navigate to Settings (top tool bar). +. In the *General* navigation pane (left), select *Webhooks*, then click btn:[Add webhook] to create a webhook in your GitHub repository that will send events to your event stream.* +. In the *Payload URL* field, paste the event stream URL that is displayed in the details of your event stream. +. In the *Content type* field, change the content type to *application/json* for your payload. +. In the *Secrets* field, add your secret from your event stream credential you created earlier. +. Click *Add webhook* to save your configuration. +. Now that the webhook has been created, return to {PlatformNameShort}. diff --git a/downstream/modules/eda/proc-eda-example-eda-github-event-stream.adoc b/downstream/modules/eda/proc-eda-example-eda-github-event-stream.adoc new file mode 100644 index 0000000000..c697850f13 --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-eda-github-event-stream.adoc @@ -0,0 +1,17 @@ +:_mod-docs-content-type: PROCEDURE +[id="eda-example-eda-github-event-stream"] + += Creating a GitHub event stream + +You can create an event stream and link it to a pre-configured credential, producing a generated URL for webhook configuration. + +.Procedure + +. From the {PlatformNameShort} navigation, click {MenuADEventStreams}. +. Click *Create event stream*. +. Enter the name for your event stream: `Repo Event Stream` +. Select your organization: *Default* +. Select *GitHub Event Stream* from the Event stream type list. +. Select the credential you created in the previous procedure: `Repo-EventStream` +. Click *Create event stream*. +. Now view the details of your new event stream and note the URL for it. Copy and paste this URL to use when you configure your webhook. \ No newline at end of file diff --git a/downstream/modules/eda/proc-eda-example-github-eventstream-cred.adoc b/downstream/modules/eda/proc-eda-example-github-eventstream-cred.adoc new file mode 100644 index 0000000000..71815349be --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-github-eventstream-cred.adoc @@ -0,0 +1,17 @@ +:_mod-docs-content-type: PROCEDURE +[id="eda-example-github-eventstream-cred"] + += Creating a GitHub event stream credential + +Complete the following procedure to create a GitHub event stream credential to enable authentication with your chosen event stream source. + + +.Procedure + +. Log in to the {PlatformNameShort} Dashboard. +. Select {MenuADCredentials}. +. Click btn:[Create credential]. +. Enter the following name for your event stream credential: `Repo-EventStream` +. Select the credential type: *GitHub Event Stream*. +. Under *Type Details*, add an HMAC secret of your choosing. +. Click *Create credential* to save your credential. \ No newline at end of file diff --git a/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc b/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc new file mode 100644 index 0000000000..b98346e97d --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc @@ -0,0 +1,31 @@ +:_mod-docs-content-type: PROCEDURE +[id="eda-replace-sources-with-event-streams"] + += Replacing sources and attaching event streams to activations + +You can create a new rulebook activation, select a project and rulebook for it, and crucially, update its event source to subscribe to a desired event stream (in this case, *Repo Event Stream* that you created earlier). + + +.Procedure + +. From the {PlatformNameShort} navigation panel, select {MenuADRulebookActivations}. +. Click btn:[Create rulebook activation] to create a rulebook for events on an application repository for Linux servers. +. In the *Name* field, enter `Repo Events - RHEL`. +. For your *Organization*, select *Default* from the list. +. From the *Project* list, select *GitOps EventStream*. +. Select *gitops-rhel.yml* for your *Rulebook*. +. In the *Event streams* field, click the gear icon to select which event stream the rulebook needs to subscribe to. The Event streams window is displayed. +. Replace an ansible.eda.webhook or compatible custom source with the desired event stream. This modifies the activation only, while leaving your filters intact. +. Select *Repo Event Stream* from the list of event streams that you created. +. Click *Save* to save your event stream. +. Next to the *Credential* field, click the *Search* icon to access {ControllerName} and connect with job templates and workflows. The *Select credential* message is displayed. +. Select the *AAP* credential and click *Confirm*. +. Select the *Decision Environment* from the list. +. Click *Create rulebook activation*. The activation status is displayed (if successful, the *Running* status displays). +. Repeat the following steps to create an additional rulebook activation using the same process as your first activation: +.. In the *Event streams* field, click the gear icon to select which event stream the rulebook needs to subscribe to. +.. Select the *Repo Event Stream* from the list of event streams that you created. +.. Click *Save* to save your event stream. +.. Click *Create rulebook activation* to save the configuration and start the rulebook. Now, there are two rulebook activations running and you can commit some code to one of your repositories. An event has been received and routed to your rulebooks. + + diff --git a/downstream/modules/eda/proc-eda-example-resend-webhook-data-event-streams.adoc b/downstream/modules/eda/proc-eda-example-resend-webhook-data-event-streams.adoc new file mode 100644 index 0000000000..3addbec6c6 --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-resend-webhook-data-event-streams.adoc @@ -0,0 +1,14 @@ +:_mod-docs-content-type: PROCEDURE +[id="eda-resend-webhook-data-event-streams"] + += Resending webhook data from your event stream type + +After configuring an event stream (in this case, *Repo Event Stream*), and linking it to rulebook activations, you can verify that events are correctly received and processed. This allows you to confirm your setup and ensure that your rulebook activations are correctly subscribed and responsive. + +.Procedure +. Go back to the *GitHub Webhook / Manage webhook* page. +. Click the *Recent Deliveries* tab. +. Click the btn:[ellipsis]. +. Click btn:[Redeliver]. A *Redeliver payload?* window is displayed with a delivery message. +. Click *Yes, redeliver this payload*. +. Return to the {PlatformNameShort} to check your rule audit. \ No newline at end of file diff --git a/downstream/modules/eda/proc-eda-example-verify-event-streams-work.adoc b/downstream/modules/eda/proc-eda-example-verify-event-streams-work.adoc new file mode 100644 index 0000000000..af7c76de39 --- /dev/null +++ b/downstream/modules/eda/proc-eda-example-verify-event-streams-work.adoc @@ -0,0 +1,14 @@ +:_mod-docs-content-type: PROCEDURE +[id="eda-example-verify-event-streams-work"] + += Verifying your event streams work + +Verify that you can use your event stream to connect to a remote system and receive data. + +. From the navigation panel in {PlatformNameShort}, select {MenuADEventStreams}. +. Select the event stream you created: `Repo Event Stream` +. Toggle the *Forward events to rulebook activation* option in the top right to disable event forwarding. The *Disable forwarding of events* message is displayed. +. In the *Disable forwarding of events* message window, click the *Yes, I confirm I want to disable the forwarding of events* checkbox. +. Click btn:[Disable forwarding of events]. +. Then click *Close*. A banner is displayed notifying you that events will not be forwarded. You can commit on a Git repo. +. In the *Repo Event Stream* that you just created, re-enable the event forwarding capability by toggling the Forward events to rulebook activation option on. \ No newline at end of file From 918d1cbb56302b82dee5a95214f9c6efbc04ea25 Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 20:21:13 -0400 Subject: [PATCH 04/12] AAP-45886 Added new user scenario/examples chapter to master.adoc --- downstream/titles/eda/eda-user-guide/master.adoc | 1 + 1 file changed, 1 insertion(+) diff --git a/downstream/titles/eda/eda-user-guide/master.adoc b/downstream/titles/eda/eda-user-guide/master.adoc index 95ab8c84cc..840d2457c2 100644 --- a/downstream/titles/eda/eda-user-guide/master.adoc +++ b/downstream/titles/eda/eda-user-guide/master.adoc @@ -26,3 +26,4 @@ include::eda/assembly-simplified-event-routing.adoc[leveloffset=+1] include::eda/assembly-eda-performance-tuning.adoc[leveloffset=+1] include::eda/assembly-eda-event-filter-plugins.adoc[leveloffset=+1] include::eda/assembly-eda-logging-strategy.adoc[leveloffset=+1] +include::eda/assembiy-eda-user-examples.adoc[leveloffset=+1] From 7bfd104d94651ea55920e58e200bd7a4d710ab42 Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 21:04:27 -0400 Subject: [PATCH 05/12] AAP-45886 Updated ID for new example file for replacing --- .../proc-eda-example-replace-sources-attach-event-streams.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc b/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc index b98346e97d..28f8308061 100644 --- a/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc +++ b/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc @@ -1,5 +1,5 @@ :_mod-docs-content-type: PROCEDURE -[id="eda-replace-sources-with-event-streams"] +[id="eda-example-replace-sources-attach-event-streams"] = Replacing sources and attaching event streams to activations From df7c1f27e3ae77a6c586a8ae47d944e21f4bcb82 Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 21:21:49 -0400 Subject: [PATCH 06/12] AAP-45886 Tweaked abstract for user scenarios chapter --- downstream/assemblies/eda/assembiy-eda-user-examples.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc index 2a7e25979b..b230ed4aa9 100644 --- a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc +++ b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc @@ -5,7 +5,7 @@ [role="_abstract"] -The following content provides detailed scenarios and practical examples for leveraging event streams (such as GitHub, GitLab, ServiceNow, and Dynatrace) with rulebook activations to automate responses to specific events within your environment. Through these examples, you can experience how to configure and apply diverse integrations to streamline your automation workflows and enhance your system's responsiveness. +The following content provides practical, end-to-end scenarios for integrating event streams (such as GitHub, GitLab, ServiceNow, and Dynatrace) with rulebook activations. Through these examples, you can experience how to configure and apply diverse integrations to automate responses to specific environmental events, streamline your workflows, and enhance system responsiveness. include::eda/con-eda-user-examples-github-event-streams.adoc[leveloffset=+1] From 830d05e2fc84bc2f22fb8b4b0e72643ec9bb2bdb Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 21:30:04 -0400 Subject: [PATCH 07/12] AAP-45886 Added block title Results to procedure --- ...roc-eda-example-replace-sources-attach-event-streams.adoc | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc b/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc index 28f8308061..76e5f011a7 100644 --- a/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc +++ b/downstream/modules/eda/proc-eda-example-replace-sources-attach-event-streams.adoc @@ -26,6 +26,9 @@ You can create a new rulebook activation, select a project and rulebook for it, .. In the *Event streams* field, click the gear icon to select which event stream the rulebook needs to subscribe to. .. Select the *Repo Event Stream* from the list of event streams that you created. .. Click *Save* to save your event stream. -.. Click *Create rulebook activation* to save the configuration and start the rulebook. Now, there are two rulebook activations running and you can commit some code to one of your repositories. An event has been received and routed to your rulebooks. +.. Click *Create rulebook activation* to save the configuration and start the rulebook. + +.Results +Now, there are two rulebook activations running and you can commit some code to one of your repositories. An event has been received and routed to your rulebooks. From 90b31d082a6a71bd6a4a8d579b35213d94b3b9a2 Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 23:00:39 -0400 Subject: [PATCH 08/12] AAP-45886 Updated links under Additional resources in original SER chapter --- .../assemblies/eda/assembly-simplified-event-routing.adoc | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc index f2f8af226f..398b293c94 100644 --- a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc +++ b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc @@ -9,7 +9,8 @@ Event streams are an easy way to connect your sources to your rulebooks. This ca [role="_additional-resources"] .Additional resources -* To view an end-to-end demo of the simplified event routing process using event streams, see link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams]. +* link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] +* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_automation_decisions/index#eda-user-examples[Event-Driven Ansible user scenarios] include::eda/con-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-create-event-stream-credential.adoc[leveloffset=+1] From 2b67a7df9b1507264a17f41b414854af83f0c27b Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 23:07:34 -0400 Subject: [PATCH 09/12] AAP-45886 Updates to add'l resources in new and original event streams content --- .../assemblies/eda/assembiy-eda-user-examples.adoc | 9 ++++++++- .../eda/assembly-simplified-event-routing.adoc | 2 +- 2 files changed, 9 insertions(+), 2 deletions(-) diff --git a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc index b230ed4aa9..09b1143dc1 100644 --- a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc +++ b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc @@ -7,6 +7,11 @@ The following content provides practical, end-to-end scenarios for integrating event streams (such as GitHub, GitLab, ServiceNow, and Dynatrace) with rulebook activations. Through these examples, you can experience how to configure and apply diverse integrations to automate responses to specific environmental events, streamline your workflows, and enhance system responsiveness. +[role="_additional-resources"] +.Additional resources +* link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] +* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_automation_decisions/index#simplified-event-routing[Simplified event routing] + include::eda/con-eda-user-examples-github-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-example-github-eventstream-cred.adoc[leveloffset=+2] @@ -19,4 +24,6 @@ include::eda/proc-eda-example-verify-event-streams-work.adoc[leveloffset=+2] include::eda/proc-eda-example-replace-sources-attach-event-streams.adoc[leveloffset=+2] -include::eda/proc-eda-example-check-rule-audit-event-stream.adoc[leveloffset=+2] \ No newline at end of file +include::eda/proc-eda-example-check-rule-audit-event-stream.adoc[leveloffset=+2] + + \ No newline at end of file diff --git a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc index 398b293c94..0a8e6d30cd 100644 --- a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc +++ b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc @@ -10,7 +10,7 @@ Event streams are an easy way to connect your sources to your rulebooks. This ca [role="_additional-resources"] .Additional resources * link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] -* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_automation_decisions/index#eda-user-examples[Event-Driven Ansible user scenarios] +* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_automation_decisions/index#eda-user-examples[{EDAName} user scenarios] include::eda/con-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-create-event-stream-credential.adoc[leveloffset=+1] From 9b4b4ca5e8a85bb2537a80d2a3cd3c2f9996426b Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 23:18:58 -0400 Subject: [PATCH 10/12] AAP-45886 Updates to add'l resources in new and original event streams content --- .../assemblies/eda/assembiy-eda-user-examples.adoc | 10 ++++------ .../eda/assembly-simplified-event-routing.adoc | 9 ++++----- 2 files changed, 8 insertions(+), 11 deletions(-) diff --git a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc index 09b1143dc1..762d68eea2 100644 --- a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc +++ b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc @@ -7,11 +7,6 @@ The following content provides practical, end-to-end scenarios for integrating event streams (such as GitHub, GitLab, ServiceNow, and Dynatrace) with rulebook activations. Through these examples, you can experience how to configure and apply diverse integrations to automate responses to specific environmental events, streamline your workflows, and enhance system responsiveness. -[role="_additional-resources"] -.Additional resources -* link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] -* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_automation_decisions/index#simplified-event-routing[Simplified event routing] - include::eda/con-eda-user-examples-github-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-example-github-eventstream-cred.adoc[leveloffset=+2] @@ -26,4 +21,7 @@ include::eda/proc-eda-example-replace-sources-attach-event-streams.adoc[leveloff include::eda/proc-eda-example-check-rule-audit-event-stream.adoc[leveloffset=+2] - \ No newline at end of file + [role="_additional-resources"] +.Additional resources +* link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] +* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/using_automation_decisions/simplified-event-routing[Simplified event routing] \ No newline at end of file diff --git a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc index 0a8e6d30cd..4949a3ba55 100644 --- a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc +++ b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc @@ -7,11 +7,6 @@ Simplified event routing enables {EDAcontroller} to capture and analyze data fro Event streams are an easy way to connect your sources to your rulebooks. This capability lets you create a single endpoint to receive alerts from an event source and then use the events in multiple rulebooks. -[role="_additional-resources"] -.Additional resources -* link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] -* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html-single/using_automation_decisions/index#eda-user-examples[{EDAName} user scenarios] - include::eda/con-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-create-event-stream-credential.adoc[leveloffset=+1] include::eda/proc-eda-create-event-stream.adoc[leveloffset=+1] @@ -21,6 +16,10 @@ include::eda/proc-eda-replace-sources-with-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-resend-webhook-data-event-streams.adoc[leveloffset=+1] include::eda/proc-eda-check-rule-audit-event-stream.adoc[leveloffset=+1] +[role="_additional-resources"] +.Additional resources +* link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] +* link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/using_automation_decisions/eda-user-examples[{EDAName} user scenarios] From 5149e65bc73cb87630bf8200eba1fdc1e747892b Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 23:22:04 -0400 Subject: [PATCH 11/12] AAP-45886 Updates to add'l resources in new event streams content --- downstream/assemblies/eda/assembiy-eda-user-examples.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc index 762d68eea2..32ccf762a8 100644 --- a/downstream/assemblies/eda/assembiy-eda-user-examples.adoc +++ b/downstream/assemblies/eda/assembiy-eda-user-examples.adoc @@ -21,7 +21,7 @@ include::eda/proc-eda-example-replace-sources-attach-event-streams.adoc[leveloff include::eda/proc-eda-example-check-rule-audit-event-stream.adoc[leveloffset=+2] - [role="_additional-resources"] +[role="_additional-resources"] .Additional resources * link:https://interact.redhat.com/share/E1HhKjGqhls8JF5NsBNz[Event-Driven Ansible with Event Streams] * link:https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/using_automation_decisions/simplified-event-routing[Simplified event routing] \ No newline at end of file From fb1ba7eff7e76f9af6884e4fbf947dd4376e5b1a Mon Sep 17 00:00:00 2001 From: Jameria Self Date: Tue, 29 Jul 2025 23:31:34 -0400 Subject: [PATCH 12/12] AAP-45886 Added pre-migration attributes to files for DITA migration --- .../eda/assembly-simplified-event-routing.adoc | 9 ++++++++- .../eda/proc-eda-example-configure-remote-sys.adoc | 2 +- downstream/titles/eda/eda-user-guide/master.adoc | 14 ++++++++++++++ 3 files changed, 23 insertions(+), 2 deletions(-) diff --git a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc index 4949a3ba55..69102dc8a7 100644 --- a/downstream/assemblies/eda/assembly-simplified-event-routing.adoc +++ b/downstream/assemblies/eda/assembly-simplified-event-routing.adoc @@ -1,4 +1,4 @@ - +:_mod-docs-content-type: ASSEMBLY [id="simplified-event-routing"] = Simplified event routing @@ -8,12 +8,19 @@ Simplified event routing enables {EDAcontroller} to capture and analyze data fro Event streams are an easy way to connect your sources to your rulebooks. This capability lets you create a single endpoint to receive alerts from an event source and then use the events in multiple rulebooks. include::eda/con-event-streams.adoc[leveloffset=+1] + include::eda/proc-eda-create-event-stream-credential.adoc[leveloffset=+1] + include::eda/proc-eda-create-event-stream.adoc[leveloffset=+1] + include::eda/proc-eda-config-remote-sys-to-events.adoc[leveloffset=+1] + include::eda/proc-eda-verify-event-streams-work.adoc[leveloffset=+1] + include::eda/proc-eda-replace-sources-with-event-streams.adoc[leveloffset=+1] + include::eda/proc-eda-resend-webhook-data-event-streams.adoc[leveloffset=+1] + include::eda/proc-eda-check-rule-audit-event-stream.adoc[leveloffset=+1] [role="_additional-resources"] diff --git a/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc b/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc index 0149a8b217..7c8f59ba8f 100644 --- a/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc +++ b/downstream/modules/eda/proc-eda-example-configure-remote-sys.adoc @@ -1,4 +1,4 @@ - +:_mod-docs-content-type: PROCEDURE [id="eda-example-configure-remote-sys"] = Configuring your remote system to send events diff --git a/downstream/titles/eda/eda-user-guide/master.adoc b/downstream/titles/eda/eda-user-guide/master.adoc index 840d2457c2..accc4d0ce7 100644 --- a/downstream/titles/eda/eda-user-guide/master.adoc +++ b/downstream/titles/eda/eda-user-guide/master.adoc @@ -12,18 +12,32 @@ include::attributes/attributes.adoc[] Developed by Red Hat, this feature is designed for simplicity and flexibility. include::{Boilerplate}[] + include::eda/assembly-eda-user-guide-overview.adoc[leveloffset=+1] + include::eda/assembly-eda-credentials.adoc[leveloffset=+1] + include::eda/assembly-eda-credential-types.adoc[leveloffset=+1] + include::eda/assembly-eda-projects.adoc[leveloffset=+1] + include::eda/assembly-eda-decision-environments.adoc[leveloffset=+1] + include::eda/assembly-eda-set-up-rhaap-credential.adoc[leveloffset=+1] + //include::eda/assembly-eda-set-up-token.adoc[leveloffset=+1] include::eda/assembly-eda-rulebook-activations.adoc[leveloffset=+1] + include::eda/assembly-eda-rulebook-troubleshooting.adoc[leveloffset=+1] + include::eda/assembly-eda-rule-audit.adoc[leveloffset=+1] + include::eda/assembly-simplified-event-routing.adoc[leveloffset=+1] + include::eda/assembly-eda-performance-tuning.adoc[leveloffset=+1] + include::eda/assembly-eda-event-filter-plugins.adoc[leveloffset=+1] + include::eda/assembly-eda-logging-strategy.adoc[leveloffset=+1] + include::eda/assembiy-eda-user-examples.adoc[leveloffset=+1]