2024-04-09 19:21:21 +02:00
|
|
|
package action
|
2024-02-15 06:39:10 +01:00
|
|
|
|
|
|
|
import (
|
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 <elio@zitadel.com>
2025-07-04 10:06:20 -04:00
|
|
|
"net/http"
|
|
|
|
|
|
|
|
"connectrpc.com/connect"
|
|
|
|
"google.golang.org/protobuf/reflect/protoreflect"
|
2024-02-15 06:39:10 +01:00
|
|
|
|
|
|
|
"github.com/zitadel/zitadel/internal/api/authz"
|
|
|
|
"github.com/zitadel/zitadel/internal/api/grpc/server"
|
|
|
|
"github.com/zitadel/zitadel/internal/command"
|
2024-08-12 22:32:01 +02:00
|
|
|
"github.com/zitadel/zitadel/internal/config/systemdefaults"
|
2024-02-15 06:39:10 +01:00
|
|
|
"github.com/zitadel/zitadel/internal/query"
|
2025-04-02 16:53:06 +02:00
|
|
|
action "github.com/zitadel/zitadel/pkg/grpc/action/v2beta"
|
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 <elio@zitadel.com>
2025-07-04 10:06:20 -04:00
|
|
|
"github.com/zitadel/zitadel/pkg/grpc/action/v2beta/actionconnect"
|
2024-02-15 06:39:10 +01:00
|
|
|
)
|
|
|
|
|
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 <elio@zitadel.com>
2025-07-04 10:06:20 -04:00
|
|
|
var _ actionconnect.ActionServiceHandler = (*Server)(nil)
|
2024-02-15 06:39:10 +01:00
|
|
|
|
|
|
|
type Server struct {
|
2024-08-12 22:32:01 +02:00
|
|
|
systemDefaults systemdefaults.SystemDefaults
|
2024-02-26 11:49:43 +01:00
|
|
|
command *command.Commands
|
|
|
|
query *query.Queries
|
|
|
|
ListActionFunctions func() []string
|
|
|
|
ListGRPCMethods func() []string
|
|
|
|
ListGRPCServices func() []string
|
2024-02-15 06:39:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
type Config struct{}
|
|
|
|
|
|
|
|
func CreateServer(
|
2024-08-12 22:32:01 +02:00
|
|
|
systemDefaults systemdefaults.SystemDefaults,
|
2024-02-15 06:39:10 +01:00
|
|
|
command *command.Commands,
|
|
|
|
query *query.Queries,
|
2024-02-26 11:49:43 +01:00
|
|
|
listActionFunctions func() []string,
|
|
|
|
listGRPCMethods func() []string,
|
|
|
|
listGRPCServices func() []string,
|
2024-02-15 06:39:10 +01:00
|
|
|
) *Server {
|
|
|
|
return &Server{
|
2024-08-12 22:32:01 +02:00
|
|
|
systemDefaults: systemDefaults,
|
2024-02-26 11:49:43 +01:00
|
|
|
command: command,
|
|
|
|
query: query,
|
|
|
|
ListActionFunctions: listActionFunctions,
|
|
|
|
ListGRPCMethods: listGRPCMethods,
|
|
|
|
ListGRPCServices: listGRPCServices,
|
2024-02-15 06:39:10 +01:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
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 <elio@zitadel.com>
2025-07-04 10:06:20 -04:00
|
|
|
func (s *Server) RegisterConnectServer(interceptors ...connect.Interceptor) (string, http.Handler) {
|
|
|
|
return actionconnect.NewActionServiceHandler(s, connect.WithInterceptors(interceptors...))
|
|
|
|
}
|
|
|
|
|
|
|
|
func (s *Server) FileDescriptor() protoreflect.FileDescriptor {
|
|
|
|
return action.File_zitadel_action_v2beta_action_service_proto
|
2024-02-15 06:39:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
func (s *Server) AppName() string {
|
2025-04-02 16:53:06 +02:00
|
|
|
return action.ActionService_ServiceDesc.ServiceName
|
2024-02-15 06:39:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
func (s *Server) MethodPrefix() string {
|
2025-04-02 16:53:06 +02:00
|
|
|
return action.ActionService_ServiceDesc.ServiceName
|
2024-02-15 06:39:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
func (s *Server) AuthMethods() authz.MethodMapping {
|
2025-04-02 16:53:06 +02:00
|
|
|
return action.ActionService_AuthMethods
|
2024-02-15 06:39:10 +01:00
|
|
|
}
|
|
|
|
|
|
|
|
func (s *Server) RegisterGateway() server.RegisterGatewayFunc {
|
2025-04-02 16:53:06 +02:00
|
|
|
return action.RegisterActionServiceHandler
|
2024-04-09 19:21:21 +02:00
|
|
|
}
|