Skip to content

fix: honor per-service defaultUUID for fallback hostnames - #237

Merged
vigneshrajsb merged 2 commits into
mainfrom
vb/lfc-defaultuuid-bug-511dba
Aug 19, 2026
Merged

fix: honor per-service defaultUUID for fallback hostnames#237
vigneshrajsb merged 2 commits into
mainfrom
vb/lfc-defaultuuid-bug-511dba

Conversation

@vigneshrajsb

Copy link
Copy Markdown
Contributor

Description

  • A service's own defaultUUID (set in lifecycle.yaml) was ignored when building its fallback public URL, internal hostname, and gRPC host — those always fell back to the global default UUID instead.
  • getPublicUrl() and the hostname fallback in DeployableService now resolve through the existing getUUID() helper, which already honored the per-service override.
  • No behavior change for services that don't set defaultUUID — they still fall back to the global default as before.

Verifying Changes

  • Added unit tests covering the per-service override for public URL, internal hostname, and gRPC host.
  • Ran the affected Jest suites and full lint/typecheck — no new failures introduced.

getPublicUrl() and the internal hostname/grpc host fallback in
DeployableService always used the global default UUID, ignoring a
service's own defaultUUID override in lifecycle.yaml. Both now resolve
through getUUID(), which already respected the per-service value.

Adds unit test coverage for the override.
Adds coverage for the case where the NO_DEFAULT_ENV_RESOLVE feature
flag takes priority over a service-level defaultUUID override, for
both getPublicUrl() and the deployable hostname/URL fallbacks.
@vigneshrajsb
vigneshrajsb marked this pull request as ready for review August 19, 2026 05:36
@vigneshrajsb
vigneshrajsb requested a review from a team as a code owner August 19, 2026 05:36
@vigneshrajsb
vigneshrajsb merged commit eac654f into main Aug 19, 2026
5 checks passed
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.

1 participant