feat(PL-6288): add reconcile status to joy resources - #294
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
📝 WalkthroughWalkthroughThe v1alpha1 API adds shared resource status primitives, status accessors to Catalog, Environment, and Release, and exported GroupVersionResource identifiers for Environment, Project, Release, and Catalog. ChangesResource status API
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Add a shared ResourceStatus (observedGeneration + conditions) and a StatusObject[T] constraint in api/v1alpha1, exposed as a Status field with GetStatus() on Catalog, Environment and Release, plus GroupVersionResource identifiers in the scheme. The joy-operator populates this status so reconcile outcomes can surface as Argo CD health. The json/yaml tag split (omitzero for encoding/json, omitempty for yaml.v3) keeps an unset status out of the catalog git repo while still serializing to the Kubernetes API. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
silphid
force-pushed
the
feat/PL-6288/expose-resource-statuses
branch
from
July 30, 2026 13:31
acfba73 to
8f97c72
Compare
silphid
marked this pull request as ready for review
July 30, 2026 14:17
silphid
requested review from
alexstojda,
ayahajar,
davidmdm,
j-martin and
riclima
as code owners
July 30, 2026 14:17
greiko
approved these changes
Jul 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Related PRs — PL-6288
One of 3 coordinated PRs:
joy(API/type layer) — feat(PL-6288): add reconcile status to joy resources #294joy-operator(status subresource + reconciler wiring) — feat(PL-6288): surface reconcile status on joy resources joy-operator#34infra(joy.nesto.ca/*Argo CD health check) — nestoca/infra#4872Merge order: merge
joy→ cut a joy release → re-pinjoy-operatorgo.modto the tag → mergejoy-operator.infracan merge any time (no-ops until resources carry conditions).What
This PR adds the API/type layer.
api/v1alpha1/status.go:ResourceStatus(observedGeneration+[]metav1.Condition) — the shared status shape.StatusObject[T]constraint so the operator can drive status updates for all resource kinds through one generic helper.Statusfield +GetStatus()on Catalog, Environment, Release.GroupVersionResourceidentifiers (catalogs/environments/releases/projects) inscheme.go.Why the
json:"...,omitzero" yaml:"...,omitempty"tag splitMatches the existing convention in this package (e.g.
Chart,Spec,metadata). For a non-pointer struct field the two codecs differ:encoding/json:omitemptyis a no-op on a zero struct;omitzero(Go 1.24+) drops it.gopkg.in/yaml.v3:omitemptydrops a zero struct;omitzerois unsupported.Both spellings omit an unset status, so no
status: {}lands in the catalog git repo, while a populated status (written by the operator) still serializes to the Kubernetes API. The joy CLI never sets status.Testing
go build ./...,go vet ./api/...clean.go test ./api/... ./pkg/catalog/...pass.go test ./...clean exceptTestReleaseRender/diff*, which fails identically onmaster(git worktree fixture requires refs not present locally) — unrelated to this change.🤖 Generated with Claude Code
Summary by CodeRabbit