SchemaWrite Request gives TenantId value length error about permify HOT 7 CLOSED

Just an update on this. I've removed the double quotes from the schema attribute and still see the same issue.

export const will only work if it is a mjs file. I've since converted it to a cjs file so you'd need to remove the export for that.

from permify.

I wasn't able to figure out why permify-node has issues around the tenantId getting passed into schema write. My guess is more research and fixes will need to be applied to permify-node to move past these issues. It has possibly something to do with nice-grpc or grpc js and whatever "invalid argument" gets passed into these packages.

I don't have time to dig that deep so hopefully you can find this in your code.

For now to work around this we've since moved to posting directly to WriteDB over http POST to deploy the schema.perm file script. My hope is that the permify-node permission check still works with GRPC so we can rely on the bit nicer dx around that rather than http/rest but we haven't gotten that far yet to test.

from permify.

@EgeAytin I have confirmed that this fixed the issue, thanks!

from permify.

This is also with the brew method of running Permify. I ran into issues with the docker method which I'll work with you on separately.

from permify.

Some additional details:

computer: Macbook Pro 2021 M1 Max (Apple Silicon)
OS: Ventura 13.1 (22C65)
Postgres version: 15.1 (via docker-compose)

Node version: 16.18.0
permify-node version: 0.3.1
permify version via brew: 0.3.0
communication method: GRPC. Curl seems to return a schema_version response so I believe that is working.

from permify.

I did try downgrading permify-node to 0.2.0 but still had no success with that.

from permify.

Hi @brandensilva we solved the issue!! Could you install the latest version of permify-node (0.3.2) and test it. We can close this issue afterwards.

from permify.