Directories
¶
| Path | Synopsis |
|---|---|
|
Package argo drives Argo CD entirely through the Kubernetes API: the dynamic client against the Application custom resource (argoproj.io/v1alpha1), never Argo's own REST/gRPC server and never an Argo API token (AGENTS.md §4.7, docs/repo-map.md's Kubernetes API row).
|
Package argo drives Argo CD entirely through the Kubernetes API: the dynamic client against the Application custom resource (argoproj.io/v1alpha1), never Argo's own REST/gRPC server and never an Argo API token (AGENTS.md §4.7, docs/repo-map.md's Kubernetes API row). |
|
Package forge is the code-host boundary (GitHub today; AGENTS.md §11 leaves GitLab as an interface with no adaptor until a GitLab repo needs one).
|
Package forge is the code-host boundary (GitHub today; AGENTS.md §11 leaves GitLab as an interface with no adaptor until a GitLab repo needs one). |
|
github
Package github implements pkg/forge.Forge against the real GitHub REST API, using github.com/cli/go-gh/v2 (AGENTS.md §4.7's one sanctioned new dependency for M3 — not google/go-github, not a hand-rolled REST client, not the full gh CLI as a library).
|
Package github implements pkg/forge.Forge against the real GitHub REST API, using github.com/cli/go-gh/v2 (AGENTS.md §4.7's one sanctioned new dependency for M3 — not google/go-github, not a hand-rolled REST client, not the full gh CLI as a library). |
|
Package git drives the git binary — never go-git (AGENTS.md §4.6) — so that a commit made on the user's behalf inherits the user's own signing configuration (gpg.format=ssh, user.signingkey, 1Password's gpg.ssh.program, includeIf) exactly as if the user had typed the command themselves.
|
Package git drives the git binary — never go-git (AGENTS.md §4.6) — so that a commit made on the user's behalf inherits the user's own signing configuration (gpg.format=ssh, user.signingkey, 1Password's gpg.ssh.program, includeIf) exactly as if the user had typed the command themselves. |
|
Package gitops reads an Argo CD GitOps repository and plans, applies and verifies byte-minimal image promotions between its environments.
|
Package gitops reads an Argo CD GitOps repository and plans, applies and verifies byte-minimal image promotions between its environments. |
|
Package image parses, prints and identifies container image references.
|
Package image parses, prints and identifies container image references. |
|
Package k8s reads what a namespace is running and, opt-in, one image pull secret.
|
Package k8s reads what a namespace is running and, opt-in, one image pull secret. |
|
Package migrate answers the question the confirm screens lead with: between the build an env is running and the build about to be written into it, which commits ship, and does any of them migrate the database (R-005 in docs/repo-map.md — on the target repo every Application auto-syncs and the app entrypoint runs db:prepare, so a merge can migrate production as a side effect).
|
Package migrate answers the question the confirm screens lead with: between the build an env is running and the build about to be written into it, which commits ship, and does any of them migrate the database (R-005 in docs/repo-map.md — on the target repo every Application auto-syncs and the app entrypoint runs db:prepare, so a merge can migrate production as a side effect). |
|
Package redact turns transport errors into messages that carry no address and no secret.
|
Package redact turns transport errors into messages that carry no address and no secret. |
|
Package registry resolves tags to digests and lists tags, behind an ordered, explicit credential chain.
|
Package registry resolves tags to digests and lists tags, behind an ordered, explicit credential chain. |
|
Package resolve turns the source env's image occurrences into the pinned references a promotion writes, from what the env is running first, then its manifests, then the registry — never a guess (AGENTS.md §4.2, principle 3).
|
Package resolve turns the source env's image occurrences into the pinned references a promotion writes, from what the env is running first, then its manifests, then the registry — never a guess (AGENTS.md §4.2, principle 3). |
|
Package rollout reads Deployment rollout completeness, and reports current Job/CronJob state, through the typed client-go clientset (k8s.io/api/apps/v1, k8s.io/api/batch/v1) — no dynamic client needed, since these are stable, already-vendored Go types — following the same client-go adaptor shape pkg/k8s established (cluster.go/kubeconfig.go/fake.go): a thin wrapper over kubernetes.Interface, redaction at every error boundary, a fake clientset for tests.
|
Package rollout reads Deployment rollout completeness, and reports current Job/CronJob state, through the typed client-go clientset (k8s.io/api/apps/v1, k8s.io/api/batch/v1) — no dynamic client needed, since these are stable, already-vendored Go types — following the same client-go adaptor shape pkg/k8s established (cluster.go/kubeconfig.go/fake.go): a thin wrapper over kubernetes.Interface, redaction at every error boundary, a fake clientset for tests. |
Click to show internal directories.
Click to hide internal directories.