-
Notifications
You must be signed in to change notification settings - Fork 758
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
Clean up dynamic configs #2877
Clean up dynamic configs #2877
Conversation
system.advancedVisibilityWritingMode: | ||
- value: "off" | ||
constraints: {} | ||
#frontend.enableClientVersionCheck: |
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.
This might be a good time to include some sort of link to docs as a comment?
Instead of a structure that might go stale?
But maybe just for docker-compose repo?
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.
This is for server developers only. They know where to look (code).
config/development_active.yaml
Outdated
@@ -117,5 +117,5 @@ publicClient: | |||
hostPort: "localhost:7233" | |||
|
|||
dynamicConfigClient: | |||
filepath: "config/dynamicconfig/development_es.yaml" | |||
filepath: "config/dynamicconfig/development_cass.yaml" | |||
pollInterval: "10s" |
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.
this might be a good time to fix this by adding a newline
What changed?
Clean up dynamic configs.
Why?
Previous values were similar to defaults and there is no reason to set them explicitly in dynamic configs. Default values for advanced visibility are also auto configured based on static configs.
docker.yaml
is an empty file for default docker configuration.Related PRs:
temporalio/docker-builds#50
temporalio/docker-compose#108
How did you test it?
Run different configurations locally. Build docker image locally and run it with
docker-compose
.Potential risks
No risks. All configs in this repo are just for server developers.
Is hotfix candidate?
No.