https://ba-preview-registry.fly.dev/debug/packages
This includes a record policy which currently allows only me to publish lann:*
It is backed by a postgres database but currently any uploaded content is stored in /tmp
Configuration for :point_up: is now in a branch: https://github.com/bytecodealliance/registry/tree/preview-registry
Registry maintainers who would like to test against this instance can generate a key, use warg key id <host>
to compute its key ID, and open a PR updating the authorized_keys.toml
with a self-named namespace. For now I will deploy manually, but I'd like to get CD working as well.
Finally managed to get durable storage attached to the preview registry instance.
Additionally, I have a PR that adds per-package authorized keys to enable narrowly-scoped CD signing keys: https://github.com/bytecodealliance/registry/pull/166
I have pushed the preview1 adapters to the preview registry. There is a regression in warg update
fixed here, after which you can do this:
$ rm -rf ~/.cache/warg/registries/preview-registry.bytecodealliance.org
$ warg update
updating package logs to the latest available versions...
$ warg download wasi:preview1-reactor-adapter
downloading package `wasi:preview1-reactor-adapter`...
downloaded version 11.0.1 of package `wasi:preview1-reactor-adapter` (sha256:710f0a4788e911af702d1c2f2c7d4d2e2cb4c917c0849c370d26f91ccc5bb228)
https://github.com/bytecodealliance/registry/pull/174 implements a debug package state endpoint
https://preview-registry.bytecodealliance.org/debug/package/wasi:preview1-command-adapter
{
"packageId": "wasi:preview1-command-adapter",
"logId": "sha256:a6172d4c339dc2ee52180d3d7582d1998c7c84a1a9a531f1829f1ec2baaaa86b",
"records": [
{
"recordId": "sha256:c20d6cbcdf6b21fe66ebbaa443fd29a3dd11dd51f6628e81c6109e6abdbcfed8",
"timestamp": 1690234391,
"entries": [
{
"kind": "init",
"key": "ecdsa-p256:A5jEmzt5dbR+lc9ya1tD/F4SB9CaRNtryYzybZU33A+Z"
}
]
},
{
"recordId": "sha256:9b04fe42fd030d2de95f9db632bb96847fffc82f933905eb342b9cb2012b8679",
"timestamp": 1690234462,
"entries": [
{
"kind": "release",
"version": "11.0.1",
"content": "sha256:78604d2a36cbfe7a3839bd2c7f40ee65b388c399b261250be9a8c35e7c0cfa5a"
}
]
}
],
"releases": [
{
"recordId": "sha256:9b04fe42fd030d2de95f9db632bb96847fffc82f933905eb342b9cb2012b8679",
"version": "11.0.1",
"by": "sha256:da355a8d3ede4cc1e35811dd098c134b213e281d45fda2a5d0deb3037af20d35",
"timestamp": "1690234462.193459520",
"state": {
"status": "released",
"content": "sha256:78604d2a36cbfe7a3839bd2c7f40ee65b388c399b261250be9a8c35e7c0cfa5a"
}
}
]
}
Sorry I haven't been able to deploy your keys; some of the requisite files are on my mysteriously-inaccessible desktop across the ocean. I may be able to handle it tomorrow or Monday at the latest.
No rush on my end, thanks Lann and safe travels home.
Should be deployed now
...where by "now" I mean now
I will be redeploying the preview registry shortly. This includes breaking changes to the warg protocol so you'll need to update clients. Additionally, if you've used the warg
cli with the preview registry before you will likely need to clear cache manually, e.g. rm -rf ~/.cache/warg/registries/preview-registry.bytecodealliance.org/
I'll update cargo-component
as well; I assume no more protocol changes coming?
Yes, protocol at least should be frozen through next week
re: the wasi
namespace on the registry, who has that key? (we should probably annotate with comments that very thing)
i was going to help out with getting wasi packages populated once we've locked down WASI (for wasmcon)
oh I think that's one of your keys originally for publishing the PoC adapter packages
Yeah I have that key. Happy to set it up differently
I'll just add mine to the wasi keys for now
and good point re: commenting on key owners
I also verified that delegation works for the ctw:
namespace, e.g.
warg publish grant --id ctw:grant-test ecdsa-p256:AnytMww6o4aUqh5S59hU0TWEnKVxmFyp1J9PYYiLHDm5
very nice!
Last updated: Dec 23 2024 at 12:05 UTC