ci: adding optional fields

splunk · May 28, 2024 · d018bb1 · d018bb1
1 parent c3d991d
commit d018bb1
Show file tree

Hide file tree

Showing 2 changed files with 20 additions and 0 deletions.
diff --git a/pytest_splunk_addon/standard_lib/data_models/Authentication.json b/pytest_splunk_addon/standard_lib/data_models/Authentication.json
@@ -33,6 +33,21 @@
           "type": "required",
           "comment": "The target involved in the authentication. You can alias this from more specific fields, such as dest_host, dest_ip, or dest_nt_host."
         },
+        {
+          "name": "src_user_type",
+          "type": "optional",
+          "comment": "The type of the user who initiated the privilege escalation."
+        },
+        {
+        "name": "user_type",
+          "type": "optional",
+          "comment": "The type of the user involved in the event or who initiated the event.\nIAMUser, Admin, or System."
+        },
+        {
+          "name": "src_user_role",
+          "type": "optional",
+          "comment": "The role of the user who initiated the privilege escalation."
+        },
         {
           "name": "duration",
           "type": "optional",

diff --git a/pytest_splunk_addon/standard_lib/data_models/Change.json b/pytest_splunk_addon/standard_lib/data_models/Change.json
@@ -116,6 +116,11 @@
           "type": "optional",
           "comment": "The account that manages the user that initiated the request. The account represents the organization, or a Cloud customer or a Cloud account."
         },
+        {
+          "name": "user_type",
+          "type": "optional",
+          "comment": "The type of the user involved in the event or who initiated the event, such as IAMUser, Admin, or System. For account management events, this should represent the type of the user changed by the request.."
+        },
         {
           "name": "vendor_product",
           "type": "required",