codemie-sdk-python 0.1.615__tar.gz → 0.1.616__tar.gz

{codemie_sdk_python-0.1.615 → codemie_sdk_python-0.1.616}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: codemie-sdk-python
-Version: 0.1.615
+Version: 0.1.616
 Summary: CodeMie SDK for Python
 Author: Vadym Vlasenko
 Author-email: vadym_vlasenko@epam.com

{codemie_sdk_python-0.1.615 → codemie_sdk_python-0.1.616}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "codemie-sdk-python"
-version = "0.1.615"
+version = "0.1.616"
 description = "CodeMie SDK for Python"
 authors = [
     "Vadym Vlasenko <vadym_vlasenko@epam.com>",

{codemie_sdk_python-0.1.615 → codemie_sdk_python-0.1.616}/src/codemie_sdk/services/dynamic_config.py

@@ -19,17 +19,29 @@ class DynamicConfigService:
         """
         self._api = ApiRequestHandler(api_domain, token, verify_ssl)
 
-    def set(self, key: str, value: int) -> dict:
-        """Upsert a dynamic config integer value.
+    def set(self, key: str, value: int | float | bool | str) -> dict:
+        """Upsert a dynamic config value.
 
         Tries POST /v1/dynamic-config/ to create the key. If the key already
         exists (HTTP 409), falls back to PUT /v1/dynamic-config/{key} to update.
-        The value is serialised as a string with value_type 'int' as required by
-        the API.
+        ``value_type`` is inferred from the Python type of ``value``
+        (``bool`` before ``int`` since ``bool`` is an ``int`` subclass) and
+        sent alongside the string-serialised value, as required by the API.
+
+        A string value is stored as-is — no int/float/bool coercion is
+        applied server-side (DynamicConfigService.convert_value passes
+        ConfigValueType.STRING straight through). Unlike the declared
+        customer-config endpoint (``PUT /v1/config/declarations/{component_id}``,
+        wrapped by ``CustomerConfigService.save_setting``), this generic admin
+        endpoint does not validate the value against any field declaration —
+        it is the only way to write a raw value that a declaration's own
+        completeness check would reject, e.g. a customer-config override
+        JSON blob missing one of its currently-declared fields.
 
         Args:
             key: Config key name (e.g. "SKILL_MAX_CONTENT_LENGTH")
-            value: Integer value to set
+            value: Value to set — int, float, bool, or str (e.g. a
+                JSON-encoded override payload)
 
         Returns:
             Response dict from the admin endpoint
@@ -39,11 +51,20 @@ class DynamicConfigService:
         """
         if not key or "/" in key:
             raise ValueError(f"Invalid config key: {key!r}")
+        if isinstance(value, bool):
+            value_type = "bool"
+        elif isinstance(value, int):
+            value_type = "int"
+        elif isinstance(value, float):
+            value_type = "float"
+        else:
+            value_type = "string"
+        value_str = value if isinstance(value, str) else str(value)
         # Try to create first; use raw Response so we can inspect the status code
         response = self._api.post(
             "/v1/dynamic-config/",
             requests.Response,
-            json_data={"key": key, "value": str(value), "value_type": "int"},
+            json_data={"key": key, "value": value_str, "value_type": value_type},
             wrap_response=False,
             raise_on_error=False,
         )
@@ -52,7 +73,7 @@ class DynamicConfigService:
             return self._api.put(
                 f"/v1/dynamic-config/{key}",
                 dict,
-                json_data={"value": str(value)},
+                json_data={"value": value_str},
                 wrap_response=False,
             )
         response.raise_for_status()