Skip to content

Add SP provider commands (Topic 11)#16

Merged
ygalblum merged 1 commit into
dcm-project:mainfrom
ygalblum:topic-11-sp-provider-plans
Mar 30, 2026
Merged

Add SP provider commands (Topic 11)#16
ygalblum merged 1 commit into
dcm-project:mainfrom
ygalblum:topic-11-sp-provider-plans

Conversation

@ygalblum

Copy link
Copy Markdown
Contributor

Implement read-only dcm sp provider list and dcm sp provider get commands for querying service providers via the generated SP Manager client (service-provider-manager/pkg/client).

Changes:

  • Add spec section 4.11 and test plan section 10a for SP provider commands
  • Implement list (with --type, --page-size, --page-token filters) and get
  • Add 12 Ginkgo test specs (TC-U139–TC-U147) covering all acceptance criteria
  • Register provider subcommand under dcm sp alongside resource
  • Table columns: ID, NAME, SERVICE TYPE, STATUS, HEALTH, CREATED

Implement read-only `dcm sp provider list` and `dcm sp provider get`
commands for querying service providers via the generated SP Manager
client (`service-provider-manager/pkg/client`).

Changes:
- Add spec section 4.11 and test plan section 10a for SP provider commands
- Implement list (with --type, --page-size, --page-token filters) and get
- Add 12 Ginkgo test specs (TC-U139–TC-U147) covering all acceptance criteria
- Register `provider` subcommand under `dcm sp` alongside `resource`
- Table columns: ID, NAME, SERVICE TYPE, STATUS, HEALTH, CREATED

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Signed-off-by: Ygal Blum <ygal.blum@gmail.com>

@gabriel-farache gabriel-farache left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 nitpick about REQ-SPP-020 as to how and where the "configured output format" is defined (then same comment on the matching AC and TC and tests)
Maybe it's already define somewhere else in the spec (for the REQ) but I still think the AC, TC and tests should mention the where and how.

Or maybe I misunderstood what "configured" implies here: for me, it means the user can specify a flag like -o yaml to have the output as yaml (or json or other)

Comment thread .ai/specs/dcm-cli.spec.md
| ID | Requirement | Priority | Notes |
|----|-------------|----------|-------|
| REQ-SPP-010 | `dcm sp provider list` MUST list SP providers with optional `--type`, `--page-size`, `--page-token` flags | MUST | |
| REQ-SPP-020 | `dcm sp provider list` MUST display SP providers in the configured output format | MUST | |

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in the configured output format

Is it format configured via optional flag? If that is the case, the flag must be listed in the previous REQ:

| REQ-SPP-010 | dcm sp provider list MUST list SP providers with optional --type, --page-size, --page-token flags | MUST | |

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same wording it used for all other commands. Output formatting has its own section: https://github.com/dcm-project/cli/blob/main/.ai/specs/dcm-cli.spec.md#43-output-formatting

Comment thread .ai/specs/dcm-cli.spec.md
@ygalblum ygalblum merged commit 0b71be9 into dcm-project:main Mar 30, 2026
4 checks passed
@ygalblum ygalblum deleted the topic-11-sp-provider-plans branch March 30, 2026 18:37
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.

4 participants