jschoubben
78fedabeb1
ADR 0593 §1: buscompose's engine moves from mesh-sdk into mesh-grants/internal/buscompose, its golden user lists unchanged; the controller's raise and assert code is left behind, and the merged switch test runs inside the part's whole integration test. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
79 lines
4.3 KiB
Go
79 lines
4.3 KiB
Go
package buscompose
|
|
|
|
import (
|
|
"time"
|
|
|
|
"git.novox.be/novox/mesh-sdk/go/declaration"
|
|
)
|
|
|
|
// The object buckets a declaration's large files travel in (novox/hq ADR 0486, issues 1696 and 1697): **one bucket for each
|
|
// node**, `declaration-files-<node>`.
|
|
//
|
|
// **The controller alone writes them, and a node-engine reads an object by its name from its own bucket** (ADR 0486 §2): its
|
|
// account may neither list the bucket nor write it, no account may touch another node's, and no other account has any access.
|
|
// Why a bucket each: a subject pattern cannot tell a name from a wildcard. A grant of `...M.*` matches a publish to the literal
|
|
// subject `...M.*` too (probed on nats-server 2.11.17 by the review of this issue: a node created a consumer filtered on
|
|
// `$O.<bucket>.C.*` and read every object of the bucket), so in one shared bucket a node could read every other node's files.
|
|
// With a bucket each, the same trick reads only the node's own files, which are the files of its own declaration.
|
|
//
|
|
// A bucket of the bus's object store is a stream, OBJ_<bucket>, whose messages are the objects' metadata
|
|
// (`$O.<bucket>.M.<base64 of the name>`) and chunks (`$O.<bucket>.C.<nuid>`).
|
|
|
|
// DeclarationFilesBucket is the prefix of the buckets' names, which mesh-sdk fixes for the node-engine and the controller alike.
|
|
const DeclarationFilesBucket = declaration.FileBucketPrefix
|
|
|
|
// DeclarationFilesBucketOf is the bucket a node's files are in: mesh-sdk's FileBucketFor, the one place the name is composed. A
|
|
// node name it refuses (one that could carry a subject wildcard or separator into a grant) is an error, never a bucket.
|
|
func DeclarationFilesBucketOf(node string) (string, error) { return declaration.FileBucketFor(node) }
|
|
|
|
// DeclarationFilesStreamOf is the stream under a node's bucket: mesh-sdk's FileStreamFor.
|
|
func DeclarationFilesStreamOf(node string) (string, error) { return declaration.FileStreamFor(node) }
|
|
|
|
// DeclarationFilesMaxBytes is a bucket's size: the objects are immutable and regenerable, and one node's hold well under a hundred
|
|
// megabytes.
|
|
const DeclarationFilesMaxBytes = 1 << 30
|
|
|
|
// DeclarationFilesKeptFor is how long an object stays after no node's latest declaration names it (ADR 0486 §3).
|
|
const DeclarationFilesKeptFor = 24 * time.Hour
|
|
|
|
// DeclarationFilesWrites is the one pattern the controller may publish to write a node's bucket: every object's metadata and
|
|
// chunks. The server's API for the stream is the controller's `$JS.API.>`.
|
|
func DeclarationFilesWrites(node string) (string, error) {
|
|
bucket, err := DeclarationFilesBucketOf(node)
|
|
if err != nil {
|
|
return "", err
|
|
}
|
|
return "$O." + bucket + ".>", nil
|
|
}
|
|
|
|
// DeclarationFilesReads is what a node-engine's account may publish to read an object of its own bucket by its name, and nothing
|
|
// more. The set is the one node-engine's own call (mesh-host internal/link FileObject) makes, for B the node's bucket and S its
|
|
// stream (issue 1697, notes 4 and 5):
|
|
//
|
|
// - the object's metadata, by a direct get of the last message of the one subject that names it. **Only the suffixed
|
|
// form**: the bare `$JS.API.DIRECT.GET.S` takes a sequence number and would read any message of the stream.
|
|
// - the ordered consumer on that object's chunks: `$JS.API.CONSUMER.CREATE.S.<name>.$O.B.C.<nuid>`. **Not `S.>`**:
|
|
// a consumer filtered on `$O.B.M.>` would read every object's name.
|
|
// - the flow-control replies of that consumer, without which a large object stalls at the flow-control window.
|
|
// - the consumer's deletion, best effort: the consumer's inactivity threshold removes it if this is refused.
|
|
//
|
|
// **Never granted:** STREAM.INFO (a `subjects_filter` of `>` lists every name), STREAM.MSG.GET (any message by its sequence), a
|
|
// publish to `$O.B.>` (a write), and any subject of another node's stream. A literal `*` in a subject matches the grant's `*`: it
|
|
// reaches the objects of this node's own bucket and no other (above).
|
|
func DeclarationFilesReads(node string) ([]string, error) {
|
|
bucket, err := DeclarationFilesBucketOf(node)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
stream, err := DeclarationFilesStreamOf(node)
|
|
if err != nil {
|
|
return nil, err
|
|
}
|
|
return []string{
|
|
"$JS.API.DIRECT.GET." + stream + ".$O." + bucket + ".M.*",
|
|
"$JS.API.CONSUMER.CREATE." + stream + ".*.$O." + bucket + ".C.*",
|
|
"$JS.API.CONSUMER.DELETE." + stream + ".*",
|
|
"$JS.FC." + stream + ".>",
|
|
}, nil
|
|
}
|