Feature 57 (config and provisioning): modules declare config and provisions, their files rendered from templates; synced with main (issues of feature 57, 874)
This commit is contained in:
@@ -171,3 +171,11 @@ rather than skipped: the predecessor already served its own registry name this w
|
||||
not a whole positive number of bytes takes the route with it — written without the limit, the
|
||||
predecessor would carry exactly what the module said not to carry, and this module would report
|
||||
success doing it.
|
||||
|
||||
## Handed to the provisioner (issue 792)
|
||||
|
||||
The module is marked `moved`, and a small Go program beside the TypeScript adapter (`cmd/route-provider`) runs the SDK's
|
||||
provider helper for `route`, with no credential. A consumer of a route whose templates name `${bound:route:name-web}`
|
||||
(a handed gitea's origins file) is filled by its machine's client from this module's entry for it. The entry's values are
|
||||
the names the controller composed for that consumer, carried in its plan and copied unchanged: the public domain is
|
||||
placement, so only the controller can join a label to it. The adapter still writes the predecessor proxy's files.
|
||||
|
||||
Reference in New Issue
Block a user