-
Notifications
You must be signed in to change notification settings - Fork 205
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
[feat][DTC-5411] updated jobs runner to be able to use temporal #204
[feat][DTC-5411] updated jobs runner to be able to use temporal #204
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM - any docs changes that should be paired with this?
docker-compose.yml
Outdated
- WORKFLOW_TEMPORAL_CLUSTER_FRONTEND_HOST=temporal | ||
- WORKFLOW_TEMPORAL_CLUSTER_FRONTEND_PORT=7233 | ||
- WORKFLOW_BACKEND_HOST=http://api:3000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this included here? i think the comments from L17 to L25 should be pasted into the jobs-runner service definition?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and then jobs-runner should also be part of workflows network?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good catch, updated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we making these changes? I think we need to align with the rest of DTC on what the plan is here and why we're making these changes.
I also don't think we should "convert" jobs runner into a temporal worker. I like @roberto-retool 's suggestion here about adding source control to the temporal worker.
I don't see why we would update the public on-premise
repo until we've validated our new setup with a customer
Updating env vars for retool onpremise to allow jobs runner to access temporal and turn into a internal onprem temporal worker.
https://linear.app/retool/issue/DTC-5411/update-docker-images-with-new-jobs-runner-env-vars