You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the devcontainer, zed is already installed and setup to access the local authorization service. You may need to run migrations before being able to issue queries.
zed schema read
/!\ Outstanding issue: it seems that sometimes the authz database is empty but alembic is at heads.
In development deployments
Follow the instructions from authzed/zed to install the zed cli.
Assuming the kubectl tool is configured and the deployment namespace is renku-ci-ds-xyz:
telepresence quit # disconnect from another k8s namespace
telepresence connect -n renku-ci-ds-xyz
Get the zed token:
kubectl -n renku-ci-ds-xyz get secret renku-ci-ds-xyz-authz -oyaml
# Token key is "SPICEDB_GRPC_PRESHARED_KEY"
Setup zed context:
# If port forwarding
zed context set renku-ci-ds-xyz localhost:50051 <DECODED_TOKEN># If using telepresence
zed context set renku-ci-ds-xyz renku-ci-ds-xyz-authz:50051 <DECODED_TOKEN
Self-signed certificates are used, so we need to ignore TLS when issuing commands:
zed --no-verify-ca schema read
The text was updated successfully, but these errors were encountered:
Some notes:
In the devcontainer
In the devcontainer,
zed
is already installed and setup to access the local authorization service. You may need to run migrations before being able to issue queries.zed schema read
/!\ Outstanding issue: it seems that sometimes the authz database is empty but alembic is at
heads
.In development deployments
Follow the instructions from authzed/zed to install the
zed
cli.Assuming the
kubectl
tool is configured and the deployment namespace isrenku-ci-ds-xyz
:Setup port forwarding:
Alternatively setup
telepresence
:telepresence quit # disconnect from another k8s namespace telepresence connect -n renku-ci-ds-xyz
Get the
zed
token:kubectl -n renku-ci-ds-xyz get secret renku-ci-ds-xyz-authz -oyaml # Token key is "SPICEDB_GRPC_PRESHARED_KEY"
Setup
zed context
:Self-signed certificates are used, so we need to ignore TLS when issuing commands:
zed --no-verify-ca schema read
The text was updated successfully, but these errors were encountered: