From 931ca6f01e699d08574ee7748d4b13291e96cfb3 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 4 Sep 2026 01:53:23 +0200 Subject: [PATCH] cli: module issue seals the node and module into the credential So the runtime knows the identity the account was scoped to, without a manifest naming the node. Claude-Session: https://claude.ai/code/session_01LrgweAeERJYBg88c5cKDzF --- cmd/mesh-control/modules.go | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/cmd/mesh-control/modules.go b/cmd/mesh-control/modules.go index 743a192..3d10bd7 100644 --- a/cmd/mesh-control/modules.go +++ b/cmd/mesh-control/modules.go @@ -260,9 +260,15 @@ func moduleCommand(ctx context.Context, args []string) error { held, err := json.Marshal(struct { URL string `json:"url"` Fingerprint string `json:"fingerprint,omitempty"` + Node string `json:"node"` + Module string `json:"module"` }{ URL: fmt.Sprintf("amqps://%s:%s@%s/", account, password, known.Address), Fingerprint: known.Fingerprint, + // The node and module the account is for, so the runtime names its queue as the mesh + // scoped it (..events) without a manifest having to interpolate a node. + Node: *forNode, + Module: module, }) if err != nil { return err