Skip to content

feat: say when Argo CD manages an AnsibleForms found on Kubernetes - #13

Merged
blaipr merged 1 commit into
mainfrom
feat/argocd-found
Oct 19, 2026
Merged

blaipr merged 1 commit into
mainfrom
feat/argocd-found

Conversation

@blaipr

@blaipr blaipr commented Oct 19, 2026

Copy link
Copy Markdown
Member

What this changes

An AnsibleForms on Kubernetes that an Argo CD Application manages is listed as managed by Argo CD (Application ), instead of "not a release of the ansibleforms Helm chart". The installer does nothing with it, explains that it is upgraded in Argo CD by changing the Application's chart version, and offers the usual choices: install a new one beside it, or stop.

Argo CD is recognised by its tracking-id annotation or its argocd.argoproj.io/instance label, and, with Argo CD's default label tracking, by the chart's labels (managed-by Helm) on workloads that have no Helm release (Argo CD renders the chart itself).

Checklist

  • Branch is named <type>/<description> and the title is a Conventional Commit
  • gofmt -l . prints nothing, and go vet ./... and go test ./... pass (a new test for both ways Argo CD marks its workloads)
  • Tried the changed flow with the built binary on a test machine, or the change does not affect it
  • New or changed texts are in every language under internal/i18n/locales

Workloads an Argo CD Application manages (its tracking annotation or instance label, or the chart's labels without a Helm release) are listed as managed by Argo CD, with the Application's name. The installer leaves them alone and offers a new installation or to stop.
@blaipr
blaipr merged commit efbf5bd into main Oct 19, 2026
4 checks passed
@blaipr
blaipr deleted the feat/argocd-found branch October 19, 2026 00:54
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.

1 participant