kc-sdk-python 5.3.1__tar.gz → 5.3.2__tar.gz

{kc_sdk_python-5.3.1/kc_sdk_python.egg-info → kc_sdk_python-5.3.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kc-sdk-python
-Version: 5.3.1
+Version: 5.3.2
 Summary: Kvindo Cloud Python SDK — typed client for managing Kvindo Cloud infrastructure (VMs, S3, Kubernetes, load balancers, VPCs, PostgreSQL) via the REST API
 Author: Kvindo
 License-Expression: MIT

{kc_sdk_python-5.3.1 → kc_sdk_python-5.3.2}/kc_api.py

@@ -569,9 +569,8 @@ class KcResourceClient:
         """Poll a change request once per second until it finishes or times out.
 
         Returns as soon as the request succeeds (`succeeded == True`) or fails
-        (both `errorMessage` and `errorCode` set). On timeout it returns the last
-        (still-pending) status rather than raising — inspect `succeeded` to tell
-        the cases apart.
+        (`errorCode` set). On timeout it returns the last (still-pending) status
+        rather than raising — inspect `succeeded` to tell the cases apart.
 
         Args:
             request_id: the `requestId` to poll.
@@ -583,7 +582,21 @@ class KcResourceClient:
         result = self.read_request(request_id)
 
         i = 0
-        while result.succeeded == False and result.errorMessage == None:
+        # Keep polling past a non-None errorMessage as long as errorCode is still None - the
+        # reconciler routinely stamps a benign, expected "please wait" errorMessage (e.g.
+        # "Temporary error. Waiting for all changes to finish first.") on EVERY throttled/gated
+        # retry tick while a resource is still legitimately in progress (see the various
+        # CloudCancelReconciliationException call sites across avant.cloud's reconcilers) -
+        # errorCode is what actually distinguishes a terminal failure. The old condition here
+        # (`result.errorMessage == None`) stopped polling and returned `succeeded=False` the
+        # moment ANY transient message appeared, without checking errorCode at all. Confirmed
+        # live via ES logs 2026-09-21 (Kubernetes E2E SDK test): the loop exited on
+        # `{"succeeded":false,"errorMessage":"Temporary error. Waiting for all changes to finish
+        # first.","errorCode":null}` mid-reconcile, and the caller (DocGuideExamples' Kubernetes
+        # example, and any real caller that doesn't separately check `.succeeded`) proceeded to
+        # read a resource that hadn't actually finished yet - e.g. status.kubeconfig was still
+        # None, crashing `f.write(kubeconfig)`.
+        while result.succeeded == False and result.errorCode == None:
             i = i + 1
             if i > timeout_seconds:
                 return result  # timed out while still pending
@@ -593,7 +606,7 @@ class KcResourceClient:
 
             if result.succeeded == True:
                 return result  # applied successfully
-            if result.errorMessage != None and result.errorCode != None:
+            if result.errorCode != None:
                 return result  # failed terminally
 
         return result

{kc_sdk_python-5.3.1 → kc_sdk_python-5.3.2/kc_sdk_python.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: kc-sdk-python
-Version: 5.3.1
+Version: 5.3.2
 Summary: Kvindo Cloud Python SDK — typed client for managing Kvindo Cloud infrastructure (VMs, S3, Kubernetes, load balancers, VPCs, PostgreSQL) via the REST API
 Author: Kvindo
 License-Expression: MIT

{kc_sdk_python-5.3.1 → kc_sdk_python-5.3.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "kc-sdk-python"
-version = "5.3.1"
+version = "5.3.2"
 description = "Kvindo Cloud Python SDK — typed client for managing Kvindo Cloud infrastructure (VMs, S3, Kubernetes, load balancers, VPCs, PostgreSQL) via the REST API"
 readme = "README.md"
 requires-python = ">=3.8"