Skip to content

Update Manifest Step to reference the new annotation #3083

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rain-on wants to merge 3 commits into
base: main
Choose a base branch
from
Open

Update Manifest Step to reference the new annotation #3083

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ffbf184
Update Manifest Step to reference the new annotation
rain-on Apr 2, 2026
42940bb
fix spellcheck
rain-on Apr 2, 2026
2173ad8
remvoe strange newline
rain-on Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
13 changes: 11 additions & 2 deletions src/pages/docs/argo-cd/steps/update-application-manifests.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,8 +12,17 @@ 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 following provides instructions on how to configure an Update Manifests step, constraints on its usage, and
how it executes.
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 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 overridden via the `argo.octopus.com/path.<name>` annotation (where <name> 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.

## Manifest Templates

Expand Down
Loading