Repository navigation
Conversation
|
|
|
|
mani-j9
force-pushed
the
mani/ha-serverless-api
branch
from
October 2, 2026 03:55
e90d50c to
f34df79
Compare
mani-j9
marked this pull request as ready for review
October 2, 2026 03:55
mani-j9
force-pushed
the
mani/ha-serverless-api
branch
from
October 5, 2026 19:52
f34df79 to
c1147dd
Compare
mani-j9
force-pushed
the
mani/ha-serverless-api
branch
2 times, most recently
from
October 5, 2026 20:12
0a15c1d to
c1147dd
Compare
02strich
reviewed
Oct 6, 2026
| }, | ||
| "description": "Optional. The set of task queue types this scaling group serves.\nIf not provided, this scaling group serves all not otherwise defined\ntask types." | ||
| }, | ||
| "regionId": { |
Contributor
There was a problem hiding this comment.
should this be a list just be on the safe side?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed?
Adds an optional
region_idfield toComputeConfigScalingGroup. When set, the scaling group is used only while the namespace is active in that region. When empty, the scaling group is used as the default, so existing configurations behave exactly as before.Why?
This is to let users configure region specific compute on a Worker Deployment Version. The Worker Controller Instance can then invoke the compute that is set for the namespace's active region, so serverless workers follow the namespace through a failover.
Breaking changes
none
Server PR
none