Skip to content
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

Add target_ prefix for CreateOrUpdateNexusIncomingServiceRequest fields #365

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

bergundy
Copy link
Member

@bergundy bergundy commented Mar 11, 2024

What changed?

See title.

Why?

Server considers requests with a namespace field as being scoped to that namespace which this request should be cluster scoped.

Breaking changes

Yes

@bergundy bergundy requested review from a team as code owners March 11, 2024 19:12
Copy link
Member

@cretz cretz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM assuming open source only. Would like to set a general suggestion of namespace of all requests being field 1 for compat assistance for edge proxies, but since this is open source only it's not a big deal.

Can you confirm all workflowservice calls for Nexus are string namespace = 1?

@bergundy bergundy merged commit 6606687 into temporalio:master Mar 11, 2024
3 checks passed
@bergundy bergundy deleted the nexus-namespace-prefix branch March 11, 2024 20:19
@bergundy
Copy link
Member Author

LGTM assuming open source only. Would like to set a general suggestion of namespace of all requests being field 1 for compat assistance for edge proxies, but since this is open source only it's not a big deal.

Can you confirm all workflowservice calls for Nexus are string namespace = 1?

I didn't add any more workflowservice RPCs, but the operatorservice outgoing registry RPCs all include a string namespace = 1:

https://github.com/temporalio/api/pull/363/files#diff-43cdd5e82c4820416a2f6b04aa800be6229b4790d74e71f9873e608a3382c442R188

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants