3 Commits

Include renames

Author	SHA1	Message	Date
Admin Bot	c6cd41fd4b	feat: implement WorkflowAdapter with namespace pass-down support ... Enable X-Service: workflow routing to Temporal via ServiceAdapter. Users can now specify namespace/domain in request payload for multi-tenant workflow access. Changes: - Implement WorkflowAdapter in serviceadapter/workflow_adapter.go * Defines 10 workflow resources: start, describe, list, history, terminate, cancel, signal, query, reset, update * Each resource validates namespace parameter in payload * Forwards requests to Temporal gRPC handler - Add GetWorkflowSpec() to define ServiceAdapter spec with: * Upstream: grpc://temporal:7233 * Auth requirements per operation (execute, read, signal, query) * Request/response schemas for validation - Wire WorkflowAdapter into main.go: * Register workflow adapter in serviceadapter registry * Initialize with temporal handler for gRPC forwarding - Remove old empty WorkflowAdapter stub from adapters.go Usage: curl -X POST https://api.riotpiao.com/ \ -H 'X-Service: workflow' \ -H 'X-Resource: start' \ -H 'Authorization: Bearer TOKEN' \ -d '{ "namespace": "default", "workflow_id": "my-workflow", "workflow_type": "MyWorkflow", "task_queue": "default" }' Namespace is required in all workflow operations and must be specified by the client in the request payload. This enables multi-tenant support where different teams access their own Temporal namespaces.	2026-09-14 08:21:49 +09:00
Admin Bot	951a4399d6	feat: unblock 8.9 memory adapter extended (all 33 tasks GREEN)	2026-08-26 13:54:23 -07:00
Admin Bot	425611ec42	feat: phase 8 serviceadapter crd rollout (32/33 tasks)	2026-08-26 13:47:36 -07:00