Documentation
¶
Overview ¶
Package notificationartifacts embeds notification's module-contract artifacts that a Go binary needs at compile time (the registry's install path needs the module's authz.fragment.json bytes to seed authz.model_fragment, and cmd/registry's container has no filesystem access to modules/ at runtime). Co-located with the artifact file itself so there is exactly one copy — go:embed can't reach outside its own package directory, which is why this small package exists here rather than a hand-copy under cmd/registry.
Index ¶
Constants ¶
This section is empty.
Variables ¶
var AuthzFragmentJSON []byte
var ManifestJSON []byte
ManifestJSON is the module's module.manifest.json bytes, embedded for the same reason as AuthzFragmentJSON above: cmd/registry's container has no filesystem access to modules/ at runtime, and the registry's builtinModules literal must not hand-copy version/metadata that can drift from the manifest; sourcing from this embed makes that drift structurally impossible instead of relying on a human to keep two literals in sync.
Functions ¶
This section is empty.
Types ¶
This section is empty.
Directories
¶
| Path | Synopsis |
|---|---|
|
notification's per-operation authorization goes through authz's real effective-access decision (POST /internal/authz/effective-access/can), with the fragment's own object-relation leg (step 7 of the ordered decision) for the two tiers that need it.
|
notification's per-operation authorization goes through authz's real effective-access decision (POST /internal/authz/effective-access/can), with the fragment's own object-relation leg (step 7 of the ordered decision) for the two tiers that need it. |
|
cmd
command
Command notification runs kiban-notification: the notification module service — channels/subscriptions/messages/inbox HTTP API plus the leased delivery worker, in one process (the module manifest names one service.port; the worker is an in-process background loop, not a second binary).
|
Command notification runs kiban-notification: the notification module service — channels/subscriptions/messages/inbox HTTP API plus the leased delivery worker, in one process (the module manifest names one service.port; the worker is an in-process background loop, not a second binary). |