From cf1a87dd6d4c9b64cf02abd389451efc6e2dfb31 Mon Sep 17 00:00:00 2001 From: aimee Date: Mon, 16 Oct 2023 13:08:15 -0500 Subject: [PATCH] docs(linkCheck): add link check disable around a code block (#82) ... to stop the link check fail --- content/en/deployment/kubernetes/argo-rollouts.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/en/deployment/kubernetes/argo-rollouts.md b/content/en/deployment/kubernetes/argo-rollouts.md index 09f95896..e16c433e 100644 --- a/content/en/deployment/kubernetes/argo-rollouts.md +++ b/content/en/deployment/kubernetes/argo-rollouts.md @@ -110,6 +110,7 @@ See {{< linkWithTitle "reference/deployment/_index.md" >}} if you want to create You can use webhooks in `afterDeployment` constraints to add specific logic for Argo Rollouts to finish deploying before starting integration tests. For example: + {{< highlight yaml "linenos=table,hl_lines=9-12 15-28" >}} # armoryDeployment.yaml version: v1 @@ -140,6 +141,7 @@ webhooks: "callbackURL": "{{armory.callbackUri}}/callback" } {{< /highlight >}} + This example employs [cmd-hook](https://hub.docker.com/r/demoimages/cmd-hook), which is an open source service deployed in the cluster to execute `kubectl` commands. CD-as-a-Service employs RNA to execute `kubectl` commands for monitoring the state of rollout objects. You can view the source code for `cmd-hook` in the [public repository](https://github.com/stephenatwell/cmdHook).