temporalio / temporalio/temporal
for enabling SSL in temporal engine will below properties are sufficent
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
In config_template.yml
tls:
enabled: {{ default .Env.SQL_TLS_ENABLED "true" }}
caFile: {{ default .Env.SQL_CA "" }}
certFile: {{ default .Env.SQL_CERT "" }}
keyFile: {{ default .Env.SQL_CERT_KEY "" }}
enableHostVerification: {{ default .Env.SQL_HOST_VERIFICATION "true" }}
serverName: {{ default .Env.SQL_HOST_NAME "" }}
Before both default .Env.SQL_TLS_ENABLED and .Env.SQL_HOST_VERIFICATION are false and i changed it to true and in
docker-compose.yml
i added
environment:
- SSL=true
- SQL_TLS=true
- SQL_TLS_ENABLED=true
- SQL_TLS_DISABLE_HOST_VERIFICATION=true
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the TLS block in config_template.yml with the environment entries in docker-compose.yml, checking which variable names each file actually uses. Verify the intended SSL and host-verification configuration for the Temporal engine; the work is done when the required properties and environment names are validated and the configuration behaves as expected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, go
- Domain
- distributed-systems, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100