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
When one edits a schema in the playground then imports it back into a permissions system via the "import" button, the playground automatically prepends the permission system's prefix to each reference in the schema.
However, that rewrite doesn't happen on zed import operations, making it difficult to share a common schema file with multiple permission systems; each reference in the schema has to be manually modified to include the prefix for the destination permission system.
This is a request to either:
fetch the prefix from the destination permissions system and then automatically prepend the prefix to each reference, just like the playground (ideal)
pass in the prefix via a command line option (not as ideal)
The text was updated successfully, but these errors were encountered:
I've actually raised this in the past, so I'm glad to see that my failure to create an issue was accounted for, haha.
We've discussed having a button to help rewrite prefixes in the playground, which is another "non-ideal" way to handle the prefixes.
One downside with looking up the the prefix for the given credential is that if there is ever a future where Authzed.com users can share/bridge their schemas with each other, this could lead to some very subtle bugs.
Following this change, `zed import` now supports two modes for handling prefixes:
1) A new CLI flag `--schema-definition-prefix` which will automatically rewrite the schema and test relationships with that prefix
2) If not specified, `zed import` will first call `ReadSchema` for the permissions system and, if a prefix is found, use that prefix automatically
Fixesauthzed#81
Following this change, `zed import` now supports two modes for handling prefixes:
1) A new CLI flag `--schema-definition-prefix` which will automatically rewrite the schema and test relationships with that prefix
2) If not specified, `zed import` will first call `ReadSchema` for the permissions system and, if a prefix is found, use that prefix automatically
Fixesauthzed#81
When one edits a schema in the playground then imports it back into a permissions system via the "import" button, the playground automatically prepends the permission system's prefix to each reference in the schema.
However, that rewrite doesn't happen on
zed import
operations, making it difficult to share a common schema file with multiple permission systems; each reference in the schema has to be manually modified to include the prefix for the destination permission system.This is a request to either:
The text was updated successfully, but these errors were encountered: