Report native backend blockers
This commit is contained in:
parent
ee80ff780c
commit
d9150024dd
7 changed files with 103 additions and 13 deletions
|
|
@ -197,7 +197,13 @@ has `cas.fetch` on `resource:cas:local`, and the caller verifies that the bytes
|
|||
hash to the requested BLAKE3 CAS hash before storing them locally. Successful
|
||||
fetches record the serving peer as a local provider, visible with
|
||||
`geth cas providers <hash>`. This is the bootstrap transfer path; future work
|
||||
will move provider/fetch behavior to `iroh-blobs`.
|
||||
will move provider/fetch behavior to `iroh-blobs`. `geth status` currently
|
||||
reports the native backend blocker for CAS, KV, and pubsub: the daemon endpoint
|
||||
is pinned to `iroh 0.90.0`, while the Rust-1.85-compatible backend crates
|
||||
resolved from crates.io are `iroh-blobs 0.97.0`, `iroh-docs 0.95.0`, and
|
||||
`iroh-gossip 0.95.0`, all of which require `iroh 0.95`. These cannot be wired
|
||||
to the daemon-owned endpoint until the endpoint wrapper is upgraded in one
|
||||
coordinated step.
|
||||
Remote resource commands that accept `--bearer-secret` can also authorize with a
|
||||
resource-scoped bearer proof generated from the private bearer token returned at
|
||||
creation time. The persisted auth log stores a public bearer id and token
|
||||
|
|
|
|||
Loading…
Reference in a new issue