(fix): Bump control-plane for multi-resource catalog - #32
jenniferubah wants to merge 8 commits into
Conversation
PR Summary by QodoSupport multi-resource catalog payloads
AI Description
Diagram
High-Level Assessment
Files changed (4)
|
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
8fc8dd6 to
5f5d685
Compare
Code Review by Qodo
1.
|
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
| require ( | ||
| github.com/coreos/go-oidc/v3 v3.20.0 | ||
| github.com/dcm-project/control-plane v0.0.0-20260814135831-7c173134e932 | ||
| github.com/dcm-project/control-plane v0.0.0-20260805143143-76ca1d7a6639 |
There was a problem hiding this comment.
This change downgrades github.com/dcm-project/control-plane from the base branch’s 2026-08-14 commit to the older 2026-08-05 commit. The intervening history includes pagination, Helm credential/RBAC, and runtime-output changes, so this is not a dependency bump and may regress behavior already present on main. Please pin the current or a newer control-plane version.
There was a problem hiding this comment.
Updated it to 2026-08-17 commit (ef5cf90) and not the latest version because the provider API is removed. That will be fixed in another PR
There was a problem hiding this comment.
That will be fixed in another PR
another PR? Could you include it in this PR? At this point we should be mindful to reduce PRs and not expand. As of today I've calculated still open around 48 PRs across all dcm repos. Each PR require 2 engineers to review and approve plus address the changes (if found).
| Repository | Open PRs | PR numbers |
|---|---|---|
| cli | 1 | #32 |
| cnpg-database-service-provider | 2 | #2, #3 |
| control-plane | 8 | #61, #62, #63, #64, #65, #66, #68, #70 |
| dcm | 9 | #109–#117 |
| dcm-project.github.io | 2 | #8, #22 |
| enhancements | 10 | #43, #57, #58, #60, #94, #99, #104, #106, #107, #108 |
| environment-agent | 7 | #34–#40 |
| k8s-network-service-provider | 2 | #2, #3 |
| k8s-storage-service-provider | 2 | #8, #9 |
| shared-workflows | 1 | #37 |
| utilities | 4 | #37, #44, #45, #49 |
| Total | 48 |
There was a problem hiding this comment.
Okay, I can expand the scope of this PR. Will update it.
From your PR list, I don't think these repos should not be included:
- dcm (used and managed by Chris)
- k8s-network-service-provider - embedded, in-flight
- k8s-storage-service-provider - embedded
- cnpg-database-service-provider - embedded
Either way, I agree, we have a lot
There was a problem hiding this comment.
So I checked the changes involved to update it to the latest and replace the provider API with the agent. It is a lot of changes that touches a lot of files which will slow down the review of this bugfix and block QE. So I'd rather do the changes in another PR, I won't create ithe PR right now as it is non blocking, while we reduce our PR backlog. Opened a jira ticket to track this: https://redhat.atlassian.net/browse/FLPATH-4895
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
jordigilh
left a comment
There was a problem hiding this comment.
Second review summary
Substantive findings are posted inline below. The existing approval targets an older commit and does not establish approval of the current head. No direct cross-PR conflict was identified; the control-plane dependency and CLI examples must be validated together.
Verdict: Not GA-ready
| ``` | ||
| ID UID DISPLAY NAME CREATED | ||
| my-catalog-item b2c3d4e5-f6a7-8901-bcde-f12345678901 Small Container 2026-03-09T10:00:00Z | ||
| ID UID DISPLAY NAME CREATED |
There was a problem hiding this comment.
The documented catalog-item table includes an ID column, but catalog_item.go emits UID, DISPLAY NAME, and CREATED without ID. Please update the example to match the actual CLI output or change the formatter and add an output-contract test.
| Expect(body["display_name"]).To(Equal("Small Container")) | ||
| spec, ok := body["spec"].(map[string]any) | ||
| Expect(ok).To(BeTrue(), "request body must include spec") | ||
| resources, ok := spec["resources"].([]any) |
There was a problem hiding this comment.
This new test asserts exactly one resource, so a regression that drops additional resources or resource-specific values can still pass. Please add a two-resource case with distinct values.
There was a problem hiding this comment.
+1
and the catalog item example in the README already defines two resources (app, db), so the test can mirror that
| - path: memory.size | ||
| display_name: "Memory (GB)" | ||
| type: string | ||
| pattern: '^[1-9][0-9]*m?$' |
There was a problem hiding this comment.
The current diff contains trailing whitespace on this line, so git diff --check fails. Please remove it before merge.
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
Assisted-By: Cursor AI Signed-off-by: Jennifer Ubah <[email protected]>
|
@jordigilh, @gciavarrini please can you take a look |
Summary
Fixes:
https://redhat.atlassian.net/browse/FLPATH-4853
https://redhat.atlassian.net/browse/FLPATH-4854
Assisted-By: Cursor AI