Repository navigation
ci: add one-off workflow to repair missing helm index entries - #29794
Merged
Merged
Conversation
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a manually dispatched
Helm index repairworkflow to re-add chart entries that were dropped fromhttps://helm.coder.com/v2/index.yamlby the release race described in #29793. The 2.36.6 tarballs (and likely 2.36.2) are already in the bucket, on ghcr.io, and attached to the GitHub release; only the index entry is missing, so the repair is a merge and upload ofindex.yaml.Inputs
version: chart version to re-add, for example2.36.6(a leadingvis stripped).dry_run(defaulttrue): do everything except the upload, and print the exactgsutilcommand that would run.What it does
coder_helm_<v>.tgz,provisioner_helm_<v>.tgz,ai-gateway_helm_<v>.tgzexist in the bucket. Missing ones are warned about (older versions predate the AI gateway chart); if none exist it fails. Tarballs are taken from the bucket, never rebuilt, so the digests written to the index match what is served.index.yaml, pinned to a GCS generation (fails if the object changes during the download, which means a release is mid-publish).helm repo index --merge, then diffs thechart versionlist before and after. Refuses to continue if any existing entry would be removed. Exits cleanly if the entries are already present.index.yaml.x-goog-if-generation-matchso it cannot clobber a concurrent write.Gated behind the same maintainer/admin check as
release.yaml, uses the same GCP workload identity,permissions: {}at the top level with onlyid-token: writeon the repair job, and a workflow-level concurrency group so two repairs cannot race each other.Verification
actionlint,shellcheck, andzizmorpass.gsutilbacked by a directory: dry run leaves the bucket untouched and prints the command; real run addscoder 2.36.6andprovisioner 2.36.6while keeping the existing entry and bumping the generation; re-running is a no-op; a version with no tarballs fails.dry_run: truedispatch for2.36.6to confirm the tarballs are found and the diff looks right.Generated by Coder Agents on behalf of @f0ssel.