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 support for API V2 or at least make it explicit which API version is being used #436

Open
wlinna opened this issue Aug 6, 2024 · 3 comments

Comments

@wlinna
Copy link

wlinna commented Aug 6, 2024

It is difficult to say what API version zitadel-node uses. It seems that the API is not versioned or anything. This also makes it difficult to ensure the correct behavior, because some endpoints work differently.

I tried to find V2 version of add human user from zitadel-node, but I couldn't. Perhaps V2 is not supported at all (?)

Could you please add support for V2 API (in addition to V1)? Or at least make it clear which API version is used.

@tafaust
Copy link
Contributor

tafaust commented Sep 29, 2024

@wlinna From what I've seen, the current version 2.0.35 is using the Zitadel API v2. Here is the trace:

  1. Types are generated from protobuf via npm run build:grpc
  2. The npm script in 1. clones the path proto/zitadel from the Zitadel repository on main branch.
  3. The proto/zitadel path contains the v2 and v2beta. Here is an example for the user resource. Here is an example for your inquiry (add human user).

However, it is unclear to me if "v2beta === v3 (preview)".
Maybe @eliobischof can give an informed answer here?

@wlinna
Copy link
Author

wlinna commented Sep 29, 2024

Hello, thanks for answering. We / I switched to the JSON-based API though (because of this issue and maybe others. I don't remember anymore).

Regardless, I think the information should be made explicit in the API and in the README, because the API versions sometimes behave differently.

@tafaust
Copy link
Contributor

tafaust commented Sep 30, 2024

@wlinna I think you can create something like this for yourself or PR to this repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants