3 Commits

Include renames

Author	SHA1	Message	Date
Livio SpringandGitHub	8c0d6c6817	chore: naming custom domain (#11383) ... # Which Problems Are Solved As part of the consistent naming effort, this PR focuses on "Custom Domains". # How the Problems Are Solved - All terms referring to a domain identifying an instance were changed to "Custom Domain" or "custom domain". - All placeholders were changed to `${CUSTOM_DOMAIN}` or `$CUSTOM_DOMAIN` (if escaping was not possible) - Some other placeholders were change to the same style. - One occurrence of custom domain was changed to organization domain to prevent misunderstandings. # Additional Changes None # Additional Context - closes #11296 - customer portal is fixed on https://github.com/zitadel/website/pull/1570 - angular example is updated on https://github.com/zitadel/zitadel-angular/pull/29	2026-01-20 10:26:57 +05:30
Livio SpringandGitHub	89221fa402	docs(api): set base uri for connectRPC endpoints (#10536) ... # Which Problems Are Solved connectRPC based endpoints were missing the baseURI leading to wrongly displayed endpoints in case you last visited anV1 API endpoint, e.g. after visiting Search Project Grants on the Management API, the endpoint for ListProjectGrants on the project service would be display as `https://$CUSTOM-DOMAIN/management/v1/zitadel.project.v2beta.ProjectService/ListProjectGrants ` instead of `https://$CUSTOM-DOMAIN/zitadel.project.v2beta.ProjectService/ListProjectGrants` # How the Problems Are Solved Set the base path / server for the connectRPC calls. # Additional Changes None # Additional Context - closes #10532	2025-08-22 12:58:15 +00:00
3 people	9ebf2316c6	feat: exchange gRPC server implementation to connectRPC (#10145) ... # Which Problems Are Solved The current maintained gRPC server in combination with a REST (grpc) gateway is getting harder and harder to maintain. Additionally, there have been and still are issues with supporting / displaying `oneOf`s correctly. We therefore decided to exchange the server implementation to connectRPC, which apart from supporting connect as protocol, also also "standard" gRCP clients as well as HTTP/1.1 / rest like clients, e.g. curl directly call the server without any additional gateway. # How the Problems Are Solved - All v2 services are moved to connectRPC implementation. (v1 services are still served as pure grpc servers) - All gRPC server interceptors were migrated / copied to a corresponding connectRPC interceptor. - API.ListGrpcServices and API. ListGrpcMethods were changed to include the connect services and endpoints. - gRPC server reflection was changed to a `StaticReflector` using the `ListGrpcServices` list. - The `grpc.Server` interfaces was split into different combinations to be able to handle the different cases (grpc server and prefixed gateway, connect server with grpc gateway, connect server only, ...) - Docs of services serving connectRPC only with no additional gateway (instance, webkey, project, app, org v2 beta) are changed to expose that - since the plugin is not yet available on buf, we download it using `postinstall` hook of the docs # Additional Changes - WebKey service is added as v2 service (in addition to the current v2beta) # Additional Context closes #9483 --------- Co-authored-by: Elio Bischof <[email protected]>	2025-07-04 14:06:20 +00:00