Fix #811: Initialize Temporal configuration on server boot

[venkatankkundavaram-dev]

Summary

Initialize the Temporal client configuration as part of the Rails initializer so server processes have the configured host, port, namespace, and task queue before scheduling syncs.

Problem addressed

Issue #811 reports scheduled syncs failing with a gRPC hostname error even though the TEMPORAL_* environment variables are present. server/config/initializers/temporal.rb defined TemporalService.setup but did not invoke it during normal Rails initialization; setup was only invoked from Puma's worker boot callback and Temporal CLI paths.

Technical approach

• Invoke TemporalService.setup at the end of the existing Temporal Rails initializer.
• Add a focused initializer spec asserting that Temporal's runtime configuration reflects the server environment after Rails boots.
• Keep the existing Puma and CLI setup calls unchanged to avoid unrelated lifecycle refactoring.

Files changed

• server/config/initializers/temporal.rb — initialize Temporal during Rails boot.
• server/spec/initializers/temporal_spec.rb — regression coverage for host, port, namespace, and task queue configuration.

Tests performed and results

• Static review of the focused diff: only the Temporal initializer and its regression spec are changed.
• Automated local RSpec/RuboCop execution could not be performed in this ChatGPT environment because the required GitHub CLI/local repository toolchain is unavailable. The PR is intentionally opened as a draft so repository CI can validate the change before it is marked ready or merged.

Backward compatibility impact

Low. This uses the existing TemporalService.setup implementation and existing environment-variable defaults. It changes initialization timing so the same configuration is available to Rails server code immediately after boot.

Related issue

Fixes #811

Limitations / follow-up work

Repository CI should confirm the initializer spec and server suite. If repeated setup during Puma worker boot proves undesirable, deduplicating the later setup call can be considered separately rather than expanding this bug fix's scope.

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: da1dd8ba-a6c6-482e-b4f2-6d886d4f2dbf

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}