From 664bc60a803b95572b6dce6b5c76c68f547a23b4 Mon Sep 17 00:00:00 2001 From: PikaByter <912293783@qq.com> Date: Fri, 7 Feb 2025 10:00:46 +0000 Subject: [PATCH 1/3] =?UTF-8?q?Since=20argocd-notifications=20has=20been?= =?UTF-8?q?=20integrated=20into=20Argo=20CD=20and=20is=20now=20part=20of?= =?UTF-8?q?=20it,=20the=20argocd-notifications=20website=20has=20been=20sh?= =?UTF-8?q?ut=20down.=20The=20link=20to=20this=20page=20now=20results=20in?= =?UTF-8?q?=20a=20404=20error.=20Therefore,=20I'm=20migrating=20the=20link?= =?UTF-8?q?s=20in=20the=20documentation=20to=20the=20new=20websit=EF=BC=88?= =?UTF-8?q?ref:=20=20https://github.com/argoproj-labs/argocd-notifications?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- doc/ci/environments/external_deployment_tools.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ci/environments/external_deployment_tools.md b/doc/ci/environments/external_deployment_tools.md index 64ddecf964e445..6f6610936343ce 100644 --- a/doc/ci/environments/external_deployment_tools.md +++ b/doc/ci/environments/external_deployment_tools.md @@ -37,7 +37,7 @@ You can create a [project access token](../../user/project/settings/project_acce ### Example: Track deployments of ArgoCD -You can use [ArgoCD webhook](https://argocd-notifications.readthedocs.io/en/stable/services/webhook/) to send deployment events to GitLab Deployment API. +You can use [ArgoCD webhook](https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/services/webhook/) to send deployment events to GitLab Deployment API. Here is an example setup that creates a `success` deployment record in GitLab when ArgoCD successfully deploys a new revision: 1. Create a new webhook. You can save the following manifest file and apply it by `kubectl apply -n argocd -f `: @@ -83,6 +83,6 @@ Here is an example setup that creates a `success` deployment record in GitLab wh ``` NOTE: -If a deployment wasn't created as expected, you can troubleshoot with [`argocd-notifications` tool](https://argocd-notifications.readthedocs.io/en/stable/troubleshooting/). +If a deployment wasn't created as expected, you can troubleshoot with [`argocd-notifications` tool](https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/troubleshooting/). For example, `argocd-notifications template notify gitlab-deployment-status --recipient gitlab:argocd-notifications` triggers API request immediately and renders an error message from GitLab API server if any. -- GitLab From 816a119a7ba36dbe6fe05c491c42838d1cfb95b3 Mon Sep 17 00:00:00 2001 From: PikaByter <912293783@qq.com> Date: Mon, 17 Feb 2025 09:51:19 +0000 Subject: [PATCH 2/3] rebase --- doc/ci/environments/external_deployment_tools.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/doc/ci/environments/external_deployment_tools.md b/doc/ci/environments/external_deployment_tools.md index 6f6610936343ce..eac4675d47ca8d 100644 --- a/doc/ci/environments/external_deployment_tools.md +++ b/doc/ci/environments/external_deployment_tools.md @@ -82,7 +82,8 @@ Here is an example setup that creates a `success` deployment record in GitLab wh kubectl patch app -n argocd -p '{"metadata": {"annotations": {"notifications.argoproj.io/subscribe.on-deployed.gitlab":""}}}' --type merge ``` -NOTE: +{{< alert type="note" >}} + If a deployment wasn't created as expected, you can troubleshoot with [`argocd-notifications` tool](https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/troubleshooting/). For example, `argocd-notifications template notify gitlab-deployment-status --recipient gitlab:argocd-notifications` triggers API request immediately and renders an error message from GitLab API server if any. -- GitLab From 44f9c2059199c2cbc6e6f27cce8464a932230eca Mon Sep 17 00:00:00 2001 From: PikaByter <912293783@qq.com> Date: Fri, 7 Feb 2025 10:00:46 +0000 Subject: [PATCH 3/3] =?UTF-8?q?Since=20argocd-notifications=20has=20been?= =?UTF-8?q?=20integrated=20into=20Argo=20CD=20and=20is=20now=20part=20of?= =?UTF-8?q?=20it,=20the=20argocd-notifications=20website=20has=20been=20sh?= =?UTF-8?q?ut=20down.=20The=20link=20to=20this=20page=20now=20results=20in?= =?UTF-8?q?=20a=20404=20error.=20Therefore,=20I'm=20migrating=20the=20link?= =?UTF-8?q?s=20in=20the=20documentation=20to=20the=20new=20websit=EF=BC=88?= =?UTF-8?q?ref:=20=20https://github.com/argoproj-labs/argocd-notifications?= =?UTF-8?q?)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- doc/ci/environments/external_deployment_tools.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/ci/environments/external_deployment_tools.md b/doc/ci/environments/external_deployment_tools.md index ddc0825d9b8466..0e981aa965635a 100644 --- a/doc/ci/environments/external_deployment_tools.md +++ b/doc/ci/environments/external_deployment_tools.md @@ -46,7 +46,7 @@ You can create a [project access token](../../user/project/settings/project_acce ### Example: Track deployments of ArgoCD -You can use [ArgoCD webhook](https://argocd-notifications.readthedocs.io/en/stable/services/webhook/) to send deployment events to GitLab Deployment API. +You can use [ArgoCD webhook](https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/services/webhook/) to send deployment events to GitLab Deployment API. Here is an example setup that creates a `success` deployment record in GitLab when ArgoCD successfully deploys a new revision: 1. Create a new webhook. You can save the following manifest file and apply it by `kubectl apply -n argocd -f `: @@ -93,7 +93,7 @@ Here is an example setup that creates a `success` deployment record in GitLab wh {{< alert type="note" >}} -If a deployment wasn't created as expected, you can troubleshoot with [`argocd-notifications` tool](https://argocd-notifications.readthedocs.io/en/stable/troubleshooting/). +If a deployment wasn't created as expected, you can troubleshoot with [`argocd-notifications` tool](https://argo-cd.readthedocs.io/en/stable/operator-manual/notifications/troubleshooting/). For example, `argocd-notifications template notify gitlab-deployment-status --recipient gitlab:argocd-notifications` triggers API request immediately and renders an error message from GitLab API server if any. -- GitLab