Skip to content

Docs/argocd update image tags helm replacement path#3179

Merged
steve-fenton-octopus merged 4 commits into
OctopusDeploy:sf/test-fork-issuefrom
vlussenburg:docs/argocd-update-image-tags-helm-replacement-path
May 27, 2026
Merged

Docs/argocd update image tags helm replacement path#3179
steve-fenton-octopus merged 4 commits into
OctopusDeploy:sf/test-fork-issuefrom
vlussenburg:docs/argocd-update-image-tags-helm-replacement-path

Conversation

@steve-fenton-octopus
Copy link
Copy Markdown
Contributor

No description provided.

vlussenburg and others added 4 commits May 11, 2026 16:39
…behaviour

Two related gaps in the Update Argo CD Application Image Tags doc that
trip up Config-as-Code users:

1. **OCL property name is undocumented.** The page describes the
   "Helm image tag path" UI field but never names the OCL/HCL key it
   serialises to. Users editing deployment_process.ocl directly have to
   read Calamari source (PackageVariables.HelmReplacementPath) to find
   that the field is `HelmReplacementPath` on the package reference and
   the resolved variable is `Octopus.Action.Package[<ref>].HelmReplacementPath`.
   Octopus silently strips unrecognised property names from saved OCL,
   so guessing (`HelmImageTagPath`, `Octopus.Action.ArgoCD.HelmImageTagPath`,
   etc.) yields no error — the step just stays a no-op at runtime, which
   is hard to diagnose. Added an OCL-focused info block with a complete
   package block example.

2. **"Helm charts" section understates what the step writes to.** The
   page says "matching image tags in the values.yaml are replaced",
   which reads as if only the chart's default values.yaml is touched.
   In practice, when `HelmReplacementPath` is set, the step ALSO writes
   to every file listed in the Application's spec.source.helm.valueFiles
   (verified against
   Calamari/source/Calamari/ArgoCD/Conventions/UpdateImageTag/HelmUpdater.cs
   `ProcessHelmSourceUsingStepVariables`). This is the behaviour any
   real per-env Helm-on-Argo setup depends on. Conversely, inline
   `spec.source.helm.valuesObject` is NOT written — also worth calling
   out so people don't go hunting.

   Rewrote the section to spell out both paths (step-configured vs
   annotation-driven) and the valuesObject limitation explicitly.
@steve-fenton-octopus steve-fenton-octopus merged commit 775787d into OctopusDeploy:sf/test-fork-issue May 27, 2026
6 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants