Add .argocd-source-* to .gitignore to prevent Image Updater ghost overrides #90
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
ldraney/pal-e-api#90
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Plan
plan-2026-02-26-tf-modularize-postgres-- Phase 5 deployment blockerRepo
forgejo_admin/pal-e-docsUser Story
As a platform operator
I want
.argocd-source-*files excluded from the repo via.gitignoreSo that ArgoCD Image Updater git write-back cannot create ghost overrides that block deployments
Context
ArgoCD Image Updater was configured with git write-back on pal-e-docs. Even after removing the Image Updater annotations from the ArgoCD Application resource, the
.argocd-source-*parameter override files can persist in the repo and override the image tag specified in the Helm values. Adding this pattern to.gitignoreensures any existing or future.argocd-source-*files are ignored and cannot be committed.This is a deployment blocker for Phase 5 (tsvector search) -- the Image Updater was reverting the image tag to an older build.
File Targets
Files the agent should modify or create:
.gitignore-- addk8s/.argocd-source-*patternFiles the agent should NOT touch:
k8s/-- Helm/ArgoCD manifests are not changed in this PRAcceptance Criteria
.gitignorecontainsk8s/.argocd-source-*.argocd-source-*files are tracked in gitTest Expectations
git check-ignore k8s/.argocd-source-pal-e-docs.yamlreturns a matchgit check-ignore k8s/.argocd-source-pal-e-docs.yamlConstraints
.gitignore, do not rewrite itChecklist
Related