From 1e4c374934e7a091e96b6129a6d3962fc88a2569 Mon Sep 17 00:00:00 2001 From: Jasmine Multani Date: Mon, 10 Apr 2023 17:09:22 -0400 Subject: [PATCH] Fixed Broken Links in Events Documentation Resolves issue Broken links in Cloud Event docs #6423 Replaces broken link for CloudEvents Spec Fixes: #6423 --- docs/events.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/events.md b/docs/events.md index 6a2a3eec6a5..24b0ef95f11 100644 --- a/docs/events.md +++ b/docs/events.md @@ -50,7 +50,7 @@ but the underlying `TaskRun` do. # Events via `CloudEvents` -When you [configure a sink](install.md#configuring-cloudevents-notifications), Tekton emits +When you [configure a sink](./additional-configs.md#configuring-cloudevents-notifications), Tekton emits events as described in the table below. Tekton sends cloud events in a parallel routine to allow for retries without blocking the @@ -75,7 +75,7 @@ Resource |Event |Event Type `Run` | `Succeed` | `dev.tekton.event.run.successful.v1` `Run` | `Failed` | `dev.tekton.event.run.failed.v1` -`CloudEvents` for `Runs` are only sent when enabled in the [configuration](./install.md#configuring-cloudevents-notifications). +`CloudEvents` for `Runs` are only sent when enabled in the [configuration](./additional-configs.md#configuring-cloudevents-notifications). **Note**: `CloudEvents` for `Runs` rely on an ephemeral cache to avoid duplicate events. In case of controller restart, the cache is reset and duplicate events @@ -83,7 +83,7 @@ may be sent. ## Format of `CloudEvents` -According to the [`CloudEvents` spec](https://github.com/cloudevents/spec/blob/master/spec.md), HTTP headers are included to match the context fields. For example: +According to the [`CloudEvents` spec](https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md), HTTP headers are included to match the context fields. For example: ``` "Ce-Id": "77f78ae7-ff6d-4e39-9d05-b9a0b7850527",