From ffbf184f116192b09e79d1bcf52eb387bf211011 Mon Sep 17 00:00:00 2001 From: Trent Mohay Date: Thu, 2 Apr 2026 15:07:24 +1100 Subject: [PATCH 1/3] Update Manifest Step to reference the new annotation --- .../docs/argo-cd/steps/update-application-manifests.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/src/pages/docs/argo-cd/steps/update-application-manifests.md b/src/pages/docs/argo-cd/steps/update-application-manifests.md index 3418d0bac3..c6c2721a39 100644 --- a/src/pages/docs/argo-cd/steps/update-application-manifests.md +++ b/src/pages/docs/argo-cd/steps/update-application-manifests.md @@ -12,6 +12,16 @@ a set of [Octostache](https://github.com/OctopusDeploy/Octostache) template file This step is agnostic of the application source repository content. Regardless of what's in the source repository, the step writes populated templates to the path specified in the Argo CD application source. +The directory structure in the input template source is maintained when the populated templates are copied into your Argo CD application's path. + +If the target application source is has a "path" field set, the template directory structure will be copied under this path. + +If the target application source is a "ref" source (without a path field), the template directory strcture will be copied into the root directory of the repository. + +If a source has both a "ref" and "path" field, the step will take no action, due to ambiguity around desired output path. + +If required, the output path to which the templates are copied can be overriden via the `argo.octopus.com/path.` annotation (where is the name defined in the source to be updated, or blank if the application has only a single source). If provided, it should specify the path, from the root of the repository, into which the manifest-step should copy the populated templates. + The following provides instructions on how to configure an Update Manifests step, constraints on its usage, and how it executes. From 42940bb72576d33fb5f065e47a2d1c4914475330 Mon Sep 17 00:00:00 2001 From: Trent Mohay Date: Thu, 2 Apr 2026 15:23:40 +1100 Subject: [PATCH 2/3] fix spellcheck --- src/pages/docs/argo-cd/steps/update-application-manifests.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/pages/docs/argo-cd/steps/update-application-manifests.md b/src/pages/docs/argo-cd/steps/update-application-manifests.md index c6c2721a39..d2fd0b41c9 100644 --- a/src/pages/docs/argo-cd/steps/update-application-manifests.md +++ b/src/pages/docs/argo-cd/steps/update-application-manifests.md @@ -16,11 +16,11 @@ The directory structure in the input template source is maintained when the popu If the target application source is has a "path" field set, the template directory structure will be copied under this path. -If the target application source is a "ref" source (without a path field), the template directory strcture will be copied into the root directory of the repository. +If the target application source is a "ref" source (without a path field), the template directory structure will be copied into the root directory of the repository. If a source has both a "ref" and "path" field, the step will take no action, due to ambiguity around desired output path. -If required, the output path to which the templates are copied can be overriden via the `argo.octopus.com/path.` annotation (where is the name defined in the source to be updated, or blank if the application has only a single source). If provided, it should specify the path, from the root of the repository, into which the manifest-step should copy the populated templates. +If required, the output path to which the templates are copied can be overridden via the `argo.octopus.com/path.` annotation (where is the name defined in the source to be updated, or blank if the application has only a single source). If provided, it should specify the path, from the root of the repository, into which the manifest-step should copy the populated templates. The following provides instructions on how to configure an Update Manifests step, constraints on its usage, and how it executes. From 2173ad8869f315000efb7384bb4577597d43cef8 Mon Sep 17 00:00:00 2001 From: Trent Mohay Date: Thu, 2 Apr 2026 15:36:08 +1100 Subject: [PATCH 3/3] remvoe strange newline --- src/pages/docs/argo-cd/steps/update-application-manifests.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/pages/docs/argo-cd/steps/update-application-manifests.md b/src/pages/docs/argo-cd/steps/update-application-manifests.md index d2fd0b41c9..fcde30c7d0 100644 --- a/src/pages/docs/argo-cd/steps/update-application-manifests.md +++ b/src/pages/docs/argo-cd/steps/update-application-manifests.md @@ -22,8 +22,7 @@ If a source has both a "ref" and "path" field, the step will take no action, due If required, the output path to which the templates are copied can be overridden via the `argo.octopus.com/path.` annotation (where is the name defined in the source to be updated, or blank if the application has only a single source). If provided, it should specify the path, from the root of the repository, into which the manifest-step should copy the populated templates. -The following provides instructions on how to configure an Update Manifests step, constraints on its usage, and -how it executes. +The following provides instructions on how to configure an Update Manifests step, constraints on its usage, and how it executes. ## Manifest Templates