Skip to content

new(argocd): github.com/argoproj/argo-cd recipe#13042

Closed
tannevaled wants to merge 1 commit into
pkgxdev:mainfrom
tannevaled:new/argocd
Closed

new(argocd): github.com/argoproj/argo-cd recipe#13042
tannevaled wants to merge 1 commit into
pkgxdev:mainfrom
tannevaled:new/argocd

Conversation

@tannevaled
Copy link
Copy Markdown
Contributor

Closes a mainstream package coverage gap (see pkgxdev/pantry overall package coverage discussion). Draft until CI confirms green.

See commit message for design choices.

Just the `argocd` CLI built from source via the Go toolchain.

The Argo CD *server* runs in-cluster as container images; users
consume it via `kubectl apply` of upstream manifests, not via pkgx.

Build approach: `go build -o argocd ./cmd` with -ldflags embedding
the version. Upstream's `make cli-local` target does this but also
builds in-tree dev tooling we don't ship (argocd-server,
argocd-repo-server, …). Going directly to `go build` keeps the
recipe focused on just the user-facing CLI.

CGO_ENABLED=0 → fully static binary, no runtime libc dep.

Build dep: go.dev. No vendored binaries; full source compile.

Test: `argocd version --client --short` returns "argocd: vX.Y.Z+…".
@jhheider
Copy link
Copy Markdown
Contributor

@tannevaled is this different from argoproj.github.io/cd?

@tannevaled
Copy link
Copy Markdown
Contributor Author

@tannevaled is this different from argoproj.github.io/cd?

hum, seems not, the Claude autoscan for missing important packages have failed :(. same for dex and zot, we already done together.

@tannevaled
Copy link
Copy Markdown
Contributor Author

Closing — duplicate of argoproj.github.io/cd which already exists on upstream main (per @jhheider's comment above). My autoscan for missing Top-300 packages missed this. Same pattern as #13051 (dex) and #13052 (zot).

@tannevaled tannevaled closed this May 30, 2026
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