Bharat Kunwar 55fd12a47c [fix] Use default_ng_worker.node_count for patches ... At present, when a cluster is patched without node_count (e.g. when health_status and health_status_reason are patched), the node_count in the cluster_update invocation contains cluster.node_count instead of default_ng_worker.node_count which causes unexpected behaviour when a cluster has additional nodegroups (e.g. the default-worker size gets incremented by 1 if the additional nodegroup has 1 worker each time the cluster is patched). This PS fixes this issue by using default_ng_worker.node_count if path "/node_count" is not present in the patch object. Story: 2005266 Task: 39962 Change-Id: I0df5149860604f0adf52701df371e34a6e667b9d		2020-06-11 10:30:21 +00:00
..
v1	[fix] Use default_ng_worker.node_count for patches	2020-06-11 10:30:21 +00:00
__init__.py	Initial commit from github (squashed)	2014-11-18 09:23:37 -05:00
base.py	Rename Bay DB, Object, and internal usage to Cluster	2016-09-08 13:01:12 -07:00
link.py	Bay to Cluster api cleanup	2016-08-23 15:55:22 -07:00
root.py	Rename Bay to Cluster in api	2016-08-17 22:24:45 +00:00
versions.py	ng-11: API microversion 1.9	2019-10-16 11:53:44 +00:00