A provider declares what it serves: mail's domain, the identity provider's issuer (issue 173) #196
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: novox/mesh-catalog#196
Reference in New Issue
Block a user
novox/hq issue 173. Consumers read
${bound:smtp:domain}and${bound:oidc-client:issuer}; both keys reached them only because a module's settings were laid over everything it served. The controller stops that (mesh-controllerfeat/the-mesh-places-its-own-files: a setting overrides a key a served fact declares and adds none), so the two providers declare the keys their consumers read, as the operator's value.Merge first. Under the running controller this is the same value (the setting still overrides the declared key). The controller PR must not roll out before mailu and keycloak are rebuilt and registered from this.
Consumers read `${bound:smtp:domain}` and `${bound:oidc-client:issuer}`, and both keys reached them only because a module's settings were laid over everything it served. Issue 173 stops that: a setting overrides a key a served fact declares and adds none. So the two providers declare the keys their consumers read, as the operator's value (`${setting:…}`, ADR 0155), and the setting that already carries each fills it. Nothing a consumer reads changes. Merges first: under the controller that still merges settings over served facts this is the same value, and the controller that stops merging (mesh-controller, feat/the-mesh-places-its-own-files) needs these declared before it rolls out.