Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add documentation on how to zed #280

Open
leafty opened this issue Jun 21, 2024 · 0 comments
Open

Add documentation on how to zed #280

leafty opened this issue Jun 21, 2024 · 0 comments

Comments

@leafty
Copy link
Member

leafty commented Jun 21, 2024

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 is renku-ci-ds-xyz:

Setup port forwarding:

kubectl -n renku-ci-ds-xyz port-forward svc/renku-ci-ds-xyz-authz 50051:50051

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:

# 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant