Skip to content

Route Ruby worker startup through an app registry#391

Draft
THardy98 wants to merge 1 commit into
mainfrom
feat/ruby-worker-app-registry
Draft

Route Ruby worker startup through an app registry#391
THardy98 wants to merge 1 commit into
mainfrom
feat/ruby-worker-app-registry

Conversation

@THardy98
Copy link
Copy Markdown
Contributor

The Ruby worker now follows the app registry shape used by the other reorganized workers. The default worker app remains the kitchen sink worker, while startup goes through a small registry that can dispatch future app entrypoints.

The Ruby worker now follows the app registry shape used by the other reorganized workers. The default worker app remains the kitchen sink worker, while startup goes through a small registry that can dispatch future app entrypoints.

Constraint: Keep generated Ruby proto files in their existing location to avoid proto churn.

Constraint: Preserve the existing Ruby worker image and sdkbuild entrypoint contracts.

Rejected: Add lambda support in this change | the requested scope is app registry plumbing only.

Confidence: high

Scope-risk: moderate

Tested: ruby -c workers/ruby/apps/registry.rb && ruby -c workers/ruby/apps/worker/app.rb && ruby -c workers/ruby/runner.rb

Tested: mise exec -- go run ./cmd/dev test ruby

Tested: mise exec -- go run ./cmd run-scenario-with-worker --scenario workflow_with_single_noop_activity --log-level debug --language ruby --app worker --embedded-server --iterations 1

Tested: mise exec -- go run ./cmd/dev lint-and-format ruby

Tested: go test ./workers ./cmd ./cmd/cli ./cmd/clioptions

Tested: git diff --check
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant