A module is told the name it is served under (hq 122) #149

2026-09-29T22:47:24Z

mesh-admin commented

2026-09-29 22:47:24 +00:00

A module contributes a label; the mesh joins it with the node's domains and
the provider serves the result — and the module itself was never told.
Software that must know its own address (a login redirect, a canonical URL,
an issuer) had it written into the manifest as a literal: a domain in a
definition, wrong on every other machine (ADR 0112). Found converting
grafana's keycloak login for ace, where it forced GF_SERVER_ROOT_URL and
keycloak's issuer back into manifests.

The binding for a requirement a module contributes to now carries name
and internal-name (or names by local name for several contributions),
and ${bound:<requirement>:name} / :internal-name (:name-<local>) fill
files from it. Both come from the one function the provider's received
file is composed by, so the proxy and the module cannot disagree about the
name. Absent when nothing was composed, so a file asking for a name on a
node with no public domain is refused, not rendered empty.

Also: ${bound:…} could not name a requirement answered by a node-scoped
provider on the same machine — its binding file was written (from here)
but the placeholders only looked at the mesh's needs. Filled from the same
answer now.

A module contributes a label; the mesh joins it with the node's domains and the provider serves the result — and the module itself was never told. Software that must know its own address (a login redirect, a canonical URL, an issuer) had it written into the manifest as a literal: a domain in a definition, wrong on every other machine (ADR 0112). Found converting grafana's keycloak login for ace, where it forced GF_SERVER_ROOT_URL and keycloak's issuer back into manifests. The binding for a requirement a module contributes to now carries `name` and `internal-name` (or `names` by local name for several contributions), and `${bound:<requirement>:name}` / `:internal-name` (`:name-<local>`) fill files from it. Both come from the one function the provider's received file is composed by, so the proxy and the module cannot disagree about the name. Absent when nothing was composed, so a file asking for a name on a node with no public domain is refused, not rendered empty. Also: `${bound:…}` could not name a requirement answered by a node-scoped provider on the same machine — its binding file was written (from `here`) but the placeholders only looked at the mesh's needs. Filled from the same answer now.

jschoubben force-pushed fix/122-a-module-is-told-its-own-name from 22845a5296 to d075c63ddb

2026-09-30 09:33:13 +00:00

Compare

jschoubben added 1 commit 2026-09-30 15:08:46 +00:00

A module is told the name it is served under (hq 122) 0a17a9a2eb

A module contributes a label; the mesh joins it with the node's domains and
the provider serves the result — and the module itself was never told.
Software that must know its own address (a login redirect, a canonical URL,
an issuer) had it written into the manifest as a literal: a domain in a
definition, wrong on every other machine (ADR 0112). Found converting
grafana's keycloak login for ace, where it forced GF_SERVER_ROOT_URL and
keycloak's issuer back into manifests.

The binding for a requirement a module contributes to now carries `name`
and `internal-name` (or `names` by local name for several contributions),
and `${bound:<requirement>:name}` / `:internal-name` (`:name-<local>`) fill
files from it. Both come from the one function the provider's received
file is composed by, so the proxy and the module cannot disagree about the
name. Absent when nothing was composed, so a file asking for a name on a
node with no public domain is refused, not rendered empty.

Also: `${bound:…}` could not name a requirement answered by a node-scoped
provider on the same machine — its binding file was written (from `here`)
but the placeholders only looked at the mesh's needs. Filled from the same
answer now.

jschoubben force-pushed fix/122-a-module-is-told-its-own-name from d075c63ddb to 0a17a9a2eb

2026-09-30 15:08:46 +00:00

Compare

mesh-admin merged commit 990ef27cd2 into main

2026-09-30 15:13:54 +00:00

mesh-admin deleted branch fix/122-a-module-is-told-its-own-name

2026-09-30 15:13:54 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-controller#149