enable the system callback url #924
Conversation
| // Enable the system callback URL for worker targets. | ||
| // NOTE that the URL scheme is fixed to HTTP since the dev server doesn't support TLS at the time of writing. | ||
| // The callback URL template is used as a fallback for external targets. | ||
| dynConf[nexusoperations.UseSystemCallbackURL.Key()] = true |
There was a problem hiding this comment.
I am curious about these Nexus dyn configs in general. Why can't a user be asked to configure these dynamic configs the same way they would if configuring any other self-hosted server? Why does other self-hosted environment not have these defaults and why must this self-hosted environment uniquely have these defaults here?
The caching and RPC limit updates make sense for local dev server, but feature defaults to not IMO. Our self-hosted dyn config requirements should be the same regardless of whether it's dev server self-hosted, docker self-hosted, binary self-hosted, etc.
There was a problem hiding this comment.
OSS server v1.31 will have this toggle enabled by default and we can remove the URL templates here.
After v1.31 no dc overrides are required for nexus.
There was a problem hiding this comment.
I just removed 2 other DCs.
2 participants
What was changed
Why?
temporalio/temporal#8308
Checklist
Closes
How was this tested: