swarm-nats-auth: grant every hive the shared hive-notices stream subjects
This commit is contained in:
parent
044e4020fa
commit
81adf2b6b4
3 changed files with 111 additions and 11 deletions
|
|
@ -22,11 +22,12 @@ serde.workspace = true
|
|||
serde_json.workspace = true
|
||||
# The jti digest: base32hex(sha256(claims)) over every JWT this crate signs.
|
||||
sha2.workspace = true
|
||||
# For `status::BUCKET` alone - the subjects a hive may publish to are derived
|
||||
# from the bucket name, and the reader, the writer and this responder must
|
||||
# name the same one. Deliberately WITHOUT the `kv` feature: this crate derives
|
||||
# subject strings, it never opens the bucket.
|
||||
swarm-queue-client.workspace = true
|
||||
# For `status::BUCKET` and `notices::STREAM` - the subjects a hive may
|
||||
# publish to are derived from these names, and every end that touches them
|
||||
# must agree on the same one. Deliberately WITHOUT the `kv` feature: this
|
||||
# crate derives subject strings, it never opens the bucket. `notices`
|
||||
# is name-only too (no `jetstream`/`kv` surface), same reason.
|
||||
swarm-queue-client = { workspace = true, features = ["notices"] }
|
||||
tokio.workspace = true
|
||||
tracing.workspace = true
|
||||
tracing-subscriber.workspace = true
|
||||
|
|
|
|||
Loading…
Reference in a new issue