platform/orca-platform
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fix(manifests): tenant-registry port 8080 → 8090 #5

Merged
sharang merged 1 commits from fix/dev-port-collision into main 2026-05-19 09:47:36 +00:00
Conversation 0 Commits 1 Files Changed 3
+3 -3
sharang commented 2026-05-19 09:46:15 +00:00
Owner
Copy Link
Copy Source

What

Bumps the port field in manifests/{vm-control,stage}/tenant-registry.toml to 8090 and updates customer-portal.toml's TENANT_REGISTRY_URL env to match. Cosmetic alignment with the dev-stack port change — each Orca container has its own port namespace, so prod is functionally unchanged.

Why

Local dev wedge: Keycloak (:8080) and tenant-registry (:8080) couldn't coexist. Bumping tenant-registry to :8090 unblocks make dev across the three repos without changing the rest.

Test plan

  • Local smoke (CI re-runs after push)

Risk

Negligible. No prod traffic depends on these defaults yet.

Checklist

  • Docs updated
## What Bumps the `port` field in `manifests/{vm-control,stage}/tenant-registry.toml` to 8090 and updates `customer-portal.toml`'s `TENANT_REGISTRY_URL` env to match. Cosmetic alignment with the dev-stack port change — each Orca container has its own port namespace, so prod is functionally unchanged. ## Why Local dev wedge: Keycloak (`:8080`) and tenant-registry (`:8080`) couldn't coexist. Bumping tenant-registry to `:8090` unblocks `make dev` across the three repos without changing the rest. ## Test plan - [x] Local smoke (CI re-runs after push) ## Risk Negligible. No prod traffic depends on these defaults yet. ## Checklist - [x] Docs updated
sharang added 1 commit 2026-05-19 09:46:15 +00:00
fix(manifests): tenant-registry port 8080 → 8090 (match dev)
ci / shared (pull_request) Successful in 5s
Details
ci / validate (pull_request) Successful in 2s
Details
a3a1783b6c 
Local dev's Keycloak owns :8080 so tenant-registry shipped on :8090.
Bring the prod + stage manifest ports + the cross-service URL in
customer-portal.toml in line so dev↔prod stays consistent. In Orca
each service has its own port-namespace inside its container, so
this is a cosmetic alignment, not a load-bearing change.

Refs: M5.1
sharang merged commit f1c3fd14b9 into main 2026-05-19 09:47:36 +00:00
sharang deleted branch fix/dev-port-collision 2026-05-19 09:47:36 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
Benjamin_Boenisch sharang (Sharang Parnerkar)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: platform/orca-platform#5
Delete Branch "fix/dev-port-collision"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?