Skip to content

Make standalone_nexus_operation capability optional for field presence #831

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.

Sign up for GitHub

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

Closed
stephanos wants to merge 1 commit into from
Closed

Make standalone_nexus_operation capability optional for field presence #831

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion temporal/api/namespace/v1/message.proto
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ message NamespaceInfo {
// True if the namespace supports worker commands (server-to-worker communication via control queues).
bool worker_commands = 10;
// True if the namespace supports standalone Nexus operations.
bool standalone_nexus_operation = 11;
optional bool standalone_nexus_operation = 11;
// True if the namespace supports attaching callbacks on workflow updates
bool workflow_update_callbacks = 12;
// When true, workers should use poller autoscaling by default unless explicitly configured otherwise.
Expand Down
Loading