-
Notifications
You must be signed in to change notification settings - Fork 92
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
feat: Managed Autoscalar feature #1038
Conversation
Here is the summary of changes. You are about to add 1 region tag.
This comment is generated by snippet-bot.
|
"autoscaling_config", | ||
] | ||
if self._autoscaling_config is not None: | ||
# When switching from non-autoscalar to autoscalar instance, |
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.
nit: set paths in a if else condition
@@ -291,6 +298,49 @@ def test_create_with_processing_units(self): | |||
self.assertEqual(instance.labels, self.LABELS) | |||
self.assertEqual(metadata, [("google-cloud-resource-prefix", instance.name)]) | |||
|
|||
def test_create_with_autoscaling_config(self): |
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.
Update any existing test eg: test_create_with_processing_units
and add autoscaling_config
with a comment that autoscaling_config
should always be set irrespective of processing_unit
or node_count
Closing this because of #1111 |
[DO NOT MERGE]
This PR adds code changes for Managed Autoscalar feature.
Add the ability to create / update an instance with autoscaling config. Note that now user can only specify one of the node_count, processing_units or autoscaling_config as the compute capacity for an instance.
Add the ability to see autoscaling config with an instance