zia_list_cloud_app_control_actions

Removed value: -false

Added value: +"Cloud Apps"

Previous value: -"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."New value: +"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records. IMPORTANT: field names are the keys of the returned records, which are usually snake_case (`custom_category`) even where the Zscaler API documents camelCase (`customCategory`) — guessing the spelling yields an empty list that looks like a real answer. If you have not already seen a record from this tool, call it once without `query` and read the keys off the response."

Added value: +"Query"

Added value: +"Rule Type"

Added value: +"zia_list_cloud_app_control_actionsArguments"

Added value: +false

Removed value: -{
-  "description": "The cloud application the user is asking about. Accepts the canonical ZIA enum (``AZURE_DEVOPS``, ``DROPBOX``, ``CHATGPT_AI``) **or** a friendly display name (``'Azure DevOps'``, ``'dropbox'``, ``'chatgpt'``). The tool resolves the input to its canonical form, looks up the app's category (= rule type), and returns the granular action vocabulary the API supports for Cloud App Control rules in that category. The action vocabulary is *surfaced* at the category level — every app in a category resolves to the same returned list — but the create endpoint validates per (rule_type, application, action) tuple and can still reject a category-level action when paired with a specific app. Treat the returned list as a superset; the create call is the only authoritative validator.",
-  "title": "Cloud App",
-  "type": "string"
-}

Added value: +{
+  "anyOf": [
+    {
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null
+}

Previous value: -"Optional JMESPath expression applied to the response. Useful for projecting just the actions list (``actions``) or filtering them (``actions[?contains(@, 'BLOCK')]``)."New value: +"Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Field names are exactly what the Zscaler API returns. Examples: \"[?enabled==`true`]\", \"[*].{name: name, id: id}\", \"length(@)\". Omit to get the full records."

Removed value: -"Query"

Removed value: -[
-  {
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]

Removed value: -null

Removed value: -"Optional override for the rule-type category. By default the tool infers the rule type from ``cloud_app``'s ``parent`` field in the policy catalog. Only set this when you want to force a specific category (e.g. when ZIA classifies an app under one category but you want actions for a different one). Must be one of the canonical category enums (``AI_ML``, ``WEBMAIL``, ``FILE_SHARE``, ``SYSTEM_AND_DEVELOPMENT``, ``STREAMING_MEDIA``, ``SOCIAL_NETWORKING``, ``INSTANT_MESSAGING``, ``BUSINESS_PRODUCTIVITY``, ``ENTERPRISE_COLLABORATION``, ``SALES_AND_MARKETING``, ``CONSUMER``, ``HOSTING_PROVIDER``, ``IT_SERVICES``, ``HUMAN_RESOURCES``, ``LEGAL``, ``HEALTH_CARE``, ``FINANCE``, ``DNS_OVER_HTTPS``, ``CUSTOM_CAPP``)."

Removed value: -"Rule Type"

Added value: +"string"

Removed value: -{
-  "default": "zia",
-  "description": "The service to use.",
-  "title": "Service",
-  "type": "string"
-}

Previous value: -[
-  "cloud_app"
-]New value: +[
+  "rule_type"
+]

Removed value: -"zia_list_cloud_app_control_actionsArguments"