From 3fe6b52c878b9b9217ac525adc4d283360d075b6 Mon Sep 17 00:00:00 2001 From: encalada Date: Fri, 5 Jul 2024 11:52:01 +0200 Subject: [PATCH] fix diagrams paths webhook --- github-webhook/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/github-webhook/README.md b/github-webhook/README.md index a1f33560..506c2bda 100644 --- a/github-webhook/README.md +++ b/github-webhook/README.md @@ -15,7 +15,7 @@ Knowing when these events occur leads us to the questions; what actions can we t In this architecture, IBM Cloud Event Notifications is our integration of choice, taking a responsive action upon Git Events. -![architecture_diagram](./images/entocejobs.jpg) +![architecture_diagram](./images/architecture-en-git-ce.jpg) In the image above, we use Event Notifications as an intermediary, leveraging their source and destination concepts to facilitate the transportation of our Github event payloads to multiple destinations. @@ -27,7 +27,7 @@ By leveraging Code Engine with Event Notifications, we can take continuous deplo ## A Clever Workaround -![application_adapter](./images/architecture-en-git-ce.jpg) +![application_adapter](./images/workaround.jpg) If you paid attention to the first diagram, you will have noticed the need for an Application Adapter.