From 726879fb2a381da91279016792b7dca88e80667b Mon Sep 17 00:00:00 2001 From: Austin Abro <37223396+AustinAbro321@users.noreply.github.com> Date: Thu, 15 Aug 2024 14:36:26 -0400 Subject: [PATCH] docs: explain no wait & helm hooks interaction (#2895) Signed-off-by: Austin Abro --- site/src/content/docs/ref/deploy.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/site/src/content/docs/ref/deploy.mdx b/site/src/content/docs/ref/deploy.mdx index dbb5dc1679..b0974485d6 100644 --- a/site/src/content/docs/ref/deploy.mdx +++ b/site/src/content/docs/ref/deploy.mdx @@ -140,6 +140,12 @@ By default, Zarf waits for all resources to deploy successfully during install, You can override this behavior during install and upgrade by setting the `noWait: true` key under the `charts` and `manifests` fields. +:::note + +Deployments will wait for helm [post-install hooks](https://helm.sh/docs/topics/charts_hooks/#the-available-hooks) to complete even with `noWait` set to `true` as Zarf follows the [Helm release lifecycle](https://helm.sh/docs/topics/charts_hooks/#hooks-and-the-release-lifecycle) + +::: + ### Timeout Settings The default timeout for Helm operations in Zarf is 15 minutes.