Skip to content

Rename API gateway URL settings to control-plane - #22

Merged
gciavarrini merged 10 commits into
dcm-project:mainfrom
gciavarrini:fix-api-var
Jun 19, 2026
Merged

Rename API gateway URL settings to control-plane#22
gciavarrini merged 10 commits into
dcm-project:mainfrom
gciavarrini:fix-api-var

Conversation

@gciavarrini

Copy link
Copy Markdown
Contributor

Assisted-By: Claude (Anthropic)
Signed-off-by: Gloria Ciavarrini gciavarrini@redhat.com

Add control-plane-url flag, DCM_CONTROL_PLANE_URL, and :8080
default. Keep legacy api-gateway names as aliases.
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.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.

I see the .ai/specs were not updated with the change, could you either remove them or update them to avoid having discrepancies?

Note that if you remove the folder, the comment referencing them should also be deleted

Comment thread internal/config/config.go
Comment thread internal/config/config.go
Comment thread internal/config/config.go Outdated
Comment thread internal/config/config.go Outdated
Comment thread README.md Outdated
Comment thread README.md Outdated
Comment thread internal/config/config_test.go Outdated
Comment thread internal/config/config.go Outdated
Drop catalog-manager, policy-manager, and service-provider-manager.
Pin control-plane at e4374fc25292.
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Assisted-By: Claude (Anthropic)
Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
@gciavarrini

Copy link
Copy Markdown
Contributor Author

.ai

I totally forgot about them.
Updated in 4a3cb30 (specs + test-plans), 9cfa19d (checkpoints), f98549b (legacy alias cleanup in docs/specs).

@gabriel-farache

Copy link
Copy Markdown
Contributor

.ai

I totally forgot about them. Updated in 4a3cb30 (specs + test-plans), 9cfa19d (checkpoints), f98549b (legacy alias cleanup in docs/specs).

Thx.
I think the checkpoints are not really necessary at this point anymore as, AFAIK, they were used during the initial dev phase as a memory for the agent.
So we can keep them here but not alter them as they reflect the dev process

Comment thread .ai/specs/dcm-cli.spec.md Outdated
| REQ-SPP-030 | `dcm sp provider get` MUST accept a `PROVIDER_ID` positional argument and display the SP provider | MUST | |
| REQ-SPP-040 | Missing `PROVIDER_ID` argument for `get` MUST result in a usage error (exit code 2) | MUST | |
| REQ-SPP-050 | All SP provider commands MUST use the generated SP Manager client (`service-provider-manager/pkg/client`) | MUST | |
| REQ-SPP-050 | All SP provider commands MUST use the generated SP provider client (`github.com/dcm-project/control-plane/pkg/sp/client/provider`) | 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.

so we are changing the name of SP Resource Manager to SP Provider?
I just want to make sure this is intentional

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 Resource Manager is inside the SP Manager. Since it's in process I'm unsure TBH about the naming. I can revert it. WDYT?

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.

I think we are using SPRM in a lot of places so changing the name in this PR, in this repo, for the first time does not seem right

@gciavarrini gciavarrini Jun 18, 2026

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.

Ack. See a0608dd

@gciavarrini

Copy link
Copy Markdown
Contributor Author

.ai

I totally forgot about them. Updated in 4a3cb30 (specs + test-plans), 9cfa19d (checkpoints), f98549b (legacy alias cleanup in docs/specs).

Thx. I think the checkpoints are not really necessary at this point anymore as, AFAIK, they were used during the initial dev phase as a memory for the agent. So we can keep them here but not alter them as they reflect the dev process

Reverted 02e71f1

Comment thread .ai/specs/dcm-cli.spec.md Outdated
@gabriel-farache

Copy link
Copy Markdown
Contributor

@gciavarrini I think that once you cleaned the commit history you are good to merge :)

This reverts commit 9cfa19d.

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Assisted-By: Claude (Anthropic)

Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
Signed-off-by: Gloria Ciavarrini <gciavarrini@redhat.com>
@gciavarrini
gciavarrini merged commit 7b88b82 into dcm-project:main Jun 19, 2026
4 checks passed
@gciavarrini
gciavarrini deleted the fix-api-var branch June 19, 2026 08:02
chadcrum added a commit that referenced this pull request Jul 9, 2026
## Why

DCM service repos push `:main` and `:sha` container images to Quay on
every merge, but the CLI repo only produced binaries on `v*` tag pushes.
Merged-but-untagged changes (like the `--control-plane-url` rename in
#22) were unavailable to the E2E test harness until someone cut a
release.

This adds the CLI equivalent — two pre-releases on every push to main:
- **`main`** — rolling, replaced on every push (convenience pointer,
like `:main` image tag)
- **`<sha7>`** — immutable, accumulates (pinnable reference, like `:sha`
image tag)

## What changed

- Replaced `tag-release.yaml` + the old inline `release.yaml` with a
single unified workflow
- On push to main: GoReleaser snapshot build → uploads to both a rolling
`main` pre-release and an immutable `<sha7>` pre-release
- On `v*` tag push: formal GoReleaser release (same behavior as before)
- Added `snapshot.version_template` to `.goreleaser.yaml` for consistent
artifact naming (`0.3.2-next+c2365dd`)
- Added concurrency group keyed on `github.ref` so rapid main pushes
cancel stale runs (tag pushes are in a separate group and never get
cancelled)
- CI/lint gate restored as `needs:` dependencies on the release job —
`ci.yaml` and `lint.yaml` don't trigger on tag pushes, so without this a
tag release could ship broken binaries

## Verified

- GoReleaser snapshot builds all 6 platform archives + checksums locally
- Full end-to-end on fork:
- **Workflow run:**
https://github.com/chadcrum/cli/actions/runs/28459205036
- **Rolling release:** https://github.com/chadcrum/cli/releases/tag/main
- **SHA release:** https://github.com/chadcrum/cli/releases/tag/c2365dd
- Both pre-releases created with all 6 platform archives + checksums

## Related

- FLPATH-4426
- Companion: dcm-project/shared-workflows#26
(adds `cli` to `ALL_SERVICES` in `hack/tag-release.sh`)

Signed-off-by: Chad Crum <1462069+chadcrum@users.noreply.github.com>
Co-authored-by: Claude <noreply@anthropic.com>
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