feat: add new postgres minor release images#279
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughUpdates test data to bump a minor upgrade scenario to 18.3, registers new PgEdge/Spock image mappings (16.13, 17.9, 18.3) in the orchestrator, and applies a two-line change to Changes
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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 |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
server/internal/orchestrator/swarm/images.go (1)
38-40: Track mutable-tag cleanup explicitly to avoid silent version drift.These new mappings are valid, but since they key a fixed minor version to mutable tags, adding a short TODO/issue marker beside each entry will make replacement with immutable tags auditable and reduce long-term ambiguity.
Suggested minimal diff
versions.addImage(host.MustPgEdgeVersion("16.13", "5"), &Images{ + // TODO(PLAT-449): replace with immutable 16.13 image tag once published. PgEdgeImage: imageTag(cfg, "16-spock5-standard"), }) @@ versions.addImage(host.MustPgEdgeVersion("17.9", "5"), &Images{ + // TODO(PLAT-449): replace with immutable 17.9 image tag once published. PgEdgeImage: imageTag(cfg, "17-spock5-standard"), }) @@ versions.addImage(host.MustPgEdgeVersion("18.3", "5"), &Images{ + // TODO(PLAT-449): replace with immutable 18.3 image tag once published. PgEdgeImage: imageTag(cfg, "18-spock5-standard"), })Also applies to: 52-54, 66-68
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@server/internal/orchestrator/swarm/images.go` around lines 38 - 40, The mapping entries using versions.addImage with host.MustPgEdgeVersion and mutable image tags (e.g., the Images struct's PgEdgeImage set via imageTag(cfg, "16-spock5-standard")) need an explicit TODO/issue marker to track future replacement with immutable tags; update each affected entry (including the ones referenced around lines 52–54 and 66–68) by adding a short comment like "TODO: replace mutable tag with immutable digest (issue #...)" adjacent to the versions.addImage call so the mutable-tag cleanup is auditable and discoverable.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@server/internal/orchestrator/swarm/images.go`:
- Around line 38-40: The mapping entries using versions.addImage with
host.MustPgEdgeVersion and mutable image tags (e.g., the Images struct's
PgEdgeImage set via imageTag(cfg, "16-spock5-standard")) need an explicit
TODO/issue marker to track future replacement with immutable tags; update each
affected entry (including the ones referenced around lines 52–54 and 66–68) by
adding a short comment like "TODO: replace mutable tag with immutable digest
(issue #...)" adjacent to the versions.addImage call so the mutable-tag cleanup
is auditable and discoverable.
Summary
Update Control Plane’s Postgres image/version mapping to include PG 16.13, 17.9, and 18.3 for upcoming minor releases, while using mutable image tags for the new minors until immutable tags are published.
Changes
Checklist