GRPC client generation or legacy sdks?
āļøāš„APIsāQuestionāUnsolved
Hey all. I'm starting a new project with zitadel and am enjoying the switch from v2 to v4 already.
I'm working on a script (which was missing from my previous usage) to populate zitadel with a default set up so new devs can clone the project, run compose up, run this script, and have a working zitadel set up. As the nodesdk is still WIP and not recommended I decided to try generating a zitadel client using the grpc protobufs so that in the future we can automatically regenerate the zitadel interface as it adapts and changes.
All very cool! However part of my script is to create a new machine user. There doesn't appear to be an implementation of https://zitadel.com/docs/reference/api/user/zitadel.user.v2.UserService.CreateUser for grpc. I see a "AddHumanUser".
Is this because the grpc interface is still being actively developed and does not have feature parity yet? Would you recommend users not use the protobufs to generate a client for now and instead stick with one of the legacy sdks?
I'm working on a script (which was missing from my previous usage) to populate zitadel with a default set up so new devs can clone the project, run compose up, run this script, and have a working zitadel set up. As the nodesdk is still WIP and not recommended I decided to try generating a zitadel client using the grpc protobufs so that in the future we can automatically regenerate the zitadel interface as it adapts and changes.
All very cool! However part of my script is to create a new machine user. There doesn't appear to be an implementation of https://zitadel.com/docs/reference/api/user/zitadel.user.v2.UserService.CreateUser for grpc. I see a "AddHumanUser".
Is this because the grpc interface is still being actively developed and does not have feature parity yet? Would you recommend users not use the protobufs to generate a client for now and instead stick with one of the legacy sdks?
Create a User: Create a new user or service account in the specified organization. Required permission:
