Skip to content

Extract images from PodSpec using Cue (& Central Registry) - #29

Closed
MPV wants to merge 4 commits into
masterfrom
cue-with-cursor-central-registry
Closed

Extract images from PodSpec using Cue (& Central Registry)#29
MPV wants to merge 4 commits into
masterfrom
cue-with-cursor-central-registry

Conversation

@MPV

@MPV MPV commented Apr 15, 2025

Copy link
Copy Markdown
Owner

But also with:

  • Only use CUE Central Registry (no local schema fallback)

@MPV MPV self-assigned this Apr 15, 2025

MPV commented Aug 9, 2026

Copy link
Copy Markdown
Owner Author

Superseded by #83, which adopts CUE on current master.

This one sourced schemas from the CUE Central Registry only, with no local fallback. #83 deliberately goes the other way: cue get go k8s.io/api/core/v1 (make schema) generates the definitions from the vendored module and checks them in.

Same official types, arrived at differently — worth stating the trade since this PR is the reason it was a choice at all:

  • No network dependency at build or run time, and nothing to fetch in CI or in the release build.
  • The schema version is pinned to the k8s.io/api already in go.mod, so a Renovate bump moves both together rather than leaving them to drift apart.
  • The cost is 45 generated .cue files (~712 KB) checked in, and a make schema step to re-run on a k8s.io/api bump — which the registry approach would not need.

Closing as superseded rather than rejected — the cue-with-cursor-central-registry branch is untouched, and if the checked-in generated tree turns out to be the objection to #83, this is the alternative to revive. #83 is one of four candidates for #26 (#81 #82 #83 #84).


Generated by Claude Code

@MPV MPV closed this Aug 9, 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.

1 participant