crimson-falcon 0.4.1 → 0.5.0

data/spec/api/filevantage_api_spec.rb

@@ -49,13 +49,13 @@ describe 'FilevantageApi' do
     end
   end
 
-  # unit tests for create_policies
+  # unit tests for create_policies_0
   # Creates a new policy of the specified type. New policies are always added at the end of the precedence list for the provided policy type.
   # After they are created, host and rule groups can be assigned, scheduled exclusions can be defined, and policy precedence can be set.
   # @param body Create a new policy.   * `name` must be between 1 and 100 characters.   * `description` can be between 0 and 500 characters.   * `platform` must be one of `Windows`, `Linux`, or `Mac`   Rule and host group assignment and policy precedence setting is performed via their respective patch end-points.
   # @param [Hash] opts the optional parameters
   # @return [PoliciesResponse]
-  describe 'create_policies test' do
+  describe 'create_policies_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
@@ -76,7 +76,7 @@ describe 'FilevantageApi' do
   # unit tests for create_rules
   # Creates a new rule configuration within the specified rule group.
   # Creates a new rule configuration within the specified rule group.
-  # @param body Create a new rule configuration for the specified rule group.   * `id` is not supported for creation of a rule, the new id of the created rule will be included in the response.   * `rule_group_id` to add the new rule configuration.   * `description` can be between 0 and 500 characters.   * `path` representing the file system or registry path to monitor.     * must be between 1 and 250 characters.      * All paths must end with the path separator, e.g. c:\\windows\\ /usr/bin/    * `severity` to categorize change events produced by this rule; must be one of: `Low`, `Medium`, `High` or `Critical`   * `depth` below the base path to monitor; must be one of: `1`, `2`, `3`, `4`, `5` or `ANY`   * `precedence` - is not supported for creation of a rule, new rules will be added last in precedence order.  Falcon GLOB syntax is supported for the following 6 properties. Allowed rule group configuration is based on the type of rule group the rule group is added to.   * `include` represents the files, directories, registry keys, or registry values that will be monitored.    * `exclude` represents the files, directories, registry keys, or registry values that will `NOT` be monitored.    * `include_users` represents the changes performed by specific users that will be monitored.   * `exclude_users` represents the changes performed by specific users that will `NOT` be monitored.   * `include_processes` represents the changes performed by specific processes that will be monitored.   * `exclude_processes` represents the changes performed by specific processes that will be `NOT` monitored.   * `content_files` represents the files whose content will be monitored. Listed files must match the file include pattern and not match the file exclude pattern   * `content_registry_values` represents the registry values whose content will be monitored. Listed registry values must match the registry include pattern and not match the registry exclude pattern   * `enable_content_capture`  File system directory monitoring:   * `watch_delete_directory_changes`   * `watch_create_directory_changes`   * `watch_rename_directory_changes`   * `watch_attributes_directory_changes` (`macOS` is not supported at this time)   * `watch_permissions_directory_changes` (`macOS` is not supported at this time)  File system file monitoring:   * `watch_rename_file_changes`   * `watch_write_file_changes`   * `watch_create_file_changes`   * `watch_delete_file_changes`   * `watch_attributes_file_changes` (`macOS` is not supported at this time)   * `watch_permissions_file_changes` (`macOS` is not supported at this time)  Windows registry key and value monitoring:    * `watch_create_key_changes`   * `watch_delete_key_changes`   * `watch_rename_key_changes`   * `watch_set_value_changes`   * `watch_delete_value_changes`   * `watch_create_file_changes`
+  # @param body Create a new rule configuration for the specified rule group.   * `id` is not supported for creation of a rule, the new id of the created rule will be included in the response.   * `rule_group_id` to add the new rule configuration.   * `description` can be between 0 and 500 characters.   * `path` representing the file system or registry path to monitor.     * must be between 1 and 250 characters.      * All paths must end with the path separator, e.g. c:\\windows\\ /usr/bin/    * `severity` to categorize change events produced by this rule; must be one of: `Low`, `Medium`, `High` or `Critical`   * `depth` below the base path to monitor; must be one of: `1`, `2`, `3`, `4`, `5` or `ANY`   * `precedence` - is not supported for creation of a rule, new rules will be added last in precedence order.  Falcon GLOB syntax is supported for the following 6 properties. Allowed rule group configuration is based on the type of rule group the rule group is added to.   * `include` represents the files, directories, registry keys, or registry values that will be monitored.    * `exclude` represents the files, directories, registry keys, or registry values that will `NOT` be monitored.    * `include_users` represents the changes performed by specific users that will be monitored.   * `exclude_users` represents the changes performed by specific users that will `NOT` be monitored.   * `include_processes` represents the changes performed by specific processes that will be monitored.   * `exclude_processes` represents the changes performed by specific processes that will be `NOT` monitored.   * `content_files` represents the files whose content will be monitored. Listed files must match the file include pattern and not match the file exclude pattern   * `content_registry_values` represents the registry values whose content will be monitored. Listed registry values must match the registry include pattern and not match the registry exclude pattern   * `enable_content_capture`   * `enable_hash_capture`  File system directory monitoring:   * `watch_delete_directory_changes`   * `watch_create_directory_changes`   * `watch_rename_directory_changes`   * `watch_attributes_directory_changes` (`macOS` is not supported at this time)   * `watch_permissions_directory_changes` (`macOS` is not supported at this time)  File system file monitoring:   * `watch_rename_file_changes`   * `watch_write_file_changes`   * `watch_create_file_changes`   * `watch_delete_file_changes`   * `watch_attributes_file_changes` (`macOS` is not supported at this time)   * `watch_permissions_file_changes` (`macOS` is not supported at this time)  Windows registry key and value monitoring:    * `watch_create_key_changes`   * `watch_delete_key_changes`   * `watch_rename_key_changes`   * `watch_set_value_changes`   * `watch_permissions_key_changes`   * `watch_delete_value_changes`   * `watch_create_file_changes`
   # @param [Hash] opts the optional parameters
   # @return [RulegroupsRulesResponse]
   describe 'create_rules test' do
@@ -147,18 +147,43 @@ describe 'FilevantageApi' do
     end
   end
 
+  # unit tests for get_actions_mixin0
+  # Retrieves the processing results for 1 or more actions.
+  # The processing results of each action that match the provided ids will be returned.
+  # @param ids One or more actions ids in the form of `ids=ID1&ids=ID2`
+  # @param [Hash] opts the optional parameters
+  # @return [ActionsGetActionResponse]
+  describe 'get_actions_mixin0 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for get_changes
   # Retrieve information on changes
   # Retrieve key attributes of Falcon FileVantage changes for the specified ids.
   # @param ids One or more change ids in the form of `ids=ID1&ids=ID2`. The maximum number of ids that can be requested at once is `500`.
   # @param [Hash] opts the optional parameters
-  # @return [ChangesGetChangesResponse]
+  # @return [PublicGetChangesResponse]
   describe 'get_changes test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
+  # unit tests for get_contents
+  # Retrieves the content captured for the provided change id
+  # Retrieves the before and after change content for the provided change id.
+  # @param id ID of the change in the form of id=ID1
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :accept_encoding Providing the value of `gzip` compresses the response, otherwise the content is returned uncompressed.
+  # @return [ContentchangesChangeContentsResponse]
+  describe 'get_contents test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for get_policies
   # Retrieves the configuration for 1 or more policies.
   # The configuration of each policy that match the provided id will be returned.
@@ -211,7 +236,7 @@ describe 'FilevantageApi' do
 
   # unit tests for high_volume_query_changes
   # Returns 1 or more change ids
-  # Returns a list of Falcon FileVantage change IDs filtered, sorted and limited by the query parameters provided. It can retrieve an unlimited number of results using multiple requests.
+  # Returns a list of Falcon FileVantage change ids filtered, sorted and limited by the query parameters provided. It can retrieve an unlimited number of results using multiple requests.
   # @param [Hash] opts the optional parameters
   # @option opts [String] :after A pagination token used with the `limit` parameter to manage pagination of results. On your first request don't provide a value for the `after` token. On subsequent requests provide the `after` token value from the previous response to continue pagination from where you left. If the response returns an empty `after` token it means there are no more results to return.
   # @option opts [Integer] :limit The maximum number of ids to return. Defaults to `100` if not specified. The maximum number of results that can be returned in a single call is `5000`.
@@ -224,9 +249,24 @@ describe 'FilevantageApi' do
     end
   end
 
+  # unit tests for query_actions_mixin0
+  # Returns one or more action ids
+  # Returns the list of action ids filtered, sorted, and limited to the query parameters provided.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :offset The first action index to return in the response. If not provided it will default to '0'. Use with the `limit` parameter to manage pagination of results.
+  # @option opts [Integer] :limit The maximum number of actions to return in the response (default: 100; max: 500). Use with the `offset` parameter to manage pagination of results
+  # @option opts [String] :sort The sort expression that should be used to sort the results (e.g. created_date|desc)
+  # @option opts [String] :filter Filter changes using a query in Falcon Query Language (FQL).   Common filter options include:   - `status`  - `operation_type`   The full list of allowed filter parameters can be reviewed in our API documentation.
+  # @return [MsaspecQueryResponse]
+  describe 'query_actions_mixin0 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for query_changes
   # Returns 1 or more change ids
-  # Returns a list of Falcon FileVantage change IDs filtered, sorted and limited by the query parameters provided. Using this endpoint you can retrieve up to `10000` results by using pagination with multiple requests. If you need to retrieve more than `10000` results consider using the `/queries/changes/v3` endpoint
+  # Returns a list of Falcon FileVantage change ids filtered, sorted and limited by the query parameters provided. Using this endpoint you can retrieve up to `10000` results by using pagination with multiple requests. If you need to retrieve more than `10000` results consider using the `/queries/changes/v3` endpoint
   # @param [Hash] opts the optional parameters
   # @option opts [Integer] :offset The offset to start retrieving records from. Defaults to `0` if not specified.
   # @option opts [Integer] :limit The maximum number of ids to return. Defaults to `100` if not specified. The maximum number of results that can be returned in a single call is `500`.
@@ -281,13 +321,37 @@ describe 'FilevantageApi' do
     end
   end
 
-  # unit tests for update_policies
+  # unit tests for signal_changes_external
+  # Initiates workflows for the provided change ids
+  # Provides the ability to initiate workflows for the specified change ids. Only 100 change ids can be provided per workflow request.
+  # @param body Change ids to initiate the workflows; limited to 100 per request.
+  # @param [Hash] opts the optional parameters
+  # @return [WorkflowResponse]
+  describe 'signal_changes_external test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for start_actions
+  # Initiates the specified action on the provided change ids
+  # Initiates the suppression, unsuppression, or purging of the provided change ids. Note that only 1 action may be initiated and active at a time.
+  # @param body Create a new action.   * `operation` must be one of the `suppress`, `unsuppress`, or `purge`   * `change_ids` represent the ids of the changes the operation will perform; limited to 100 ids per action   * `comment` optional comment to describe the reason for the action
+  # @param [Hash] opts the optional parameters
+  # @return [ActionsActionResponse]
+  describe 'start_actions test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for update_policies_0
   # Updates the general information of the provided policy.
   # Only name, description, and enabled status of the policy is allowed to be update. Rule and host group assignment is performed via their respective patch end points.
   # @param body Enables updates to the following fields for an existing policy.    * `id` of the policy to update.   * `name` must be between 1 and 100 characters.   * `description` can be between 0 and 500 characters.   * `platform` may not be modified after the policy is created.   * `enabled` must be one of `true` or `false`.   Rule and host group assignment and policy precedence setting is performed via their respective patch end-points.
   # @param [Hash] opts the optional parameters
   # @return [PoliciesResponse]
-  describe 'update_policies test' do
+  describe 'update_policies_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
@@ -307,14 +371,14 @@ describe 'FilevantageApi' do
     end
   end
 
-  # unit tests for update_policy_precedence
+  # unit tests for update_policy_precedence_0
   # Updates the policy precedence for all policies of a specific type.
   # Requests that do not represent all ids of the provided policy type will not be processed.
   # @param ids Precedence of the policies for the provided type in the form of `ids=ID1&ids=ID2`
   # @param type The policy type for which to set the precedence order, must be one of `Windows`, `Linux` or `Mac`.
   # @param [Hash] opts the optional parameters
   # @return [PoliciesPrecedenceResponse]
-  describe 'update_policy_precedence test' do
+  describe 'update_policy_precedence_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
@@ -362,7 +426,7 @@ describe 'FilevantageApi' do
   # unit tests for update_rules
   # Updates the provided rule configuration within the specified rule group.
   # The rule must currently exist within the specified rule group.
-  # @param body Update the rule configuration for the specified rule ID and group.   * `id` of the rule to update.   * `rule_group_id` that contains the rule configuration.   * `description` can be between 0 and 500 characters.   * `path` representing the file system or registry path to monitor.     * must be between 1 and 250 characters.      * All paths must end with the path separator, e.g. c:\\windows\\ /usr/bin/    * `severity` to categorize change events produced by this rule; must be one of: `Low`, `Medium`, `High` or `Critical`   * `depth` below the base path to monitor; must be one of: `1`, `2`, `3`, `4`, `5` or `ANY`   * `precedence` is the order in which rules will be evaluated starting with 1. Specifying a precedence value that is already set for another rule in the group will result this rule being placed before that existing rule.  Falcon GLOB syntax is supported for the following 6 properties. Allowed rule group configuration is based on the type of rule group the rule group is added to.   * `include` represents the files, directories, registry keys, or registry values that will be monitored.    * `exclude` represents the files, directories, registry keys, or registry values that will `NOT` be monitored.    * `include_users` represents the changes performed by specific users that will be monitored.   * `exclude_users` represents the changes performed by specific users that will `NOT` be monitored.   * `include_processes` represents the changes performed by specific processes that will be monitored.   * `exclude_processes` represents the changes performed by specific processes that will be `NOT` monitored.   * `content_files` represents the files that will be monitored. Listed files must match the file include pattern and not match the file exclude pattern   * `content_registry_values` represents the registry values whose content will be monitored. Listed registry values must match the registry include pattern and not match the registry exclude pattern   * `enable_content_capture`  File system directory monitoring:   * `watch_delete_directory_changes`   * `watch_create_directory_changes`   * `watch_rename_directory_changes`   * `watch_attributes_directory_changes` (`macOS` is not supported at this time)   * `watch_permissions_directory_changes` (`macOS` is not supported at this time)  File system file monitoring:   * `watch_rename_file_changes`   * `watch_write_file_changes`   * `watch_create_file_changes`   * `watch_delete_file_changes`   * `watch_attributes_file_changes` (`macOS` is not supported at this time)   * `watch_permissions_file_changes` (`macOS` is not supported at this time)  Windows registry key and value monitoring:    * `watch_create_key_changes`   * `watch_delete_key_changes`   * `watch_rename_key_changes`   * `watch_set_value_changes`   * `watch_delete_value_changes`   * `watch_create_file_changes`
+  # @param body Update the rule configuration for the specified rule ID and group.   * `id` of the rule to update.   * `rule_group_id` that contains the rule configuration.   * `description` can be between 0 and 500 characters.   * `path` representing the file system or registry path to monitor.     * must be between 1 and 250 characters.      * All paths must end with the path separator, e.g. c:\\windows\\ /usr/bin/    * `severity` to categorize change events produced by this rule; must be one of: `Low`, `Medium`, `High` or `Critical`   * `depth` below the base path to monitor; must be one of: `1`, `2`, `3`, `4`, `5` or `ANY`   * `precedence` is the order in which rules will be evaluated starting with 1. Specifying a precedence value that is already set for another rule in the group will result this rule being placed before that existing rule.  Falcon GLOB syntax is supported for the following 6 properties. Allowed rule group configuration is based on the type of rule group the rule group is added to.   * `include` represents the files, directories, registry keys, or registry values that will be monitored.    * `exclude` represents the files, directories, registry keys, or registry values that will `NOT` be monitored.    * `include_users` represents the changes performed by specific users that will be monitored.   * `exclude_users` represents the changes performed by specific users that will `NOT` be monitored.   * `include_processes` represents the changes performed by specific processes that will be monitored.   * `exclude_processes` represents the changes performed by specific processes that will be `NOT` monitored.   * `content_files` represents the files that will be monitored. Listed files must match the file include pattern and not match the file exclude pattern   * `content_registry_values` represents the registry values whose content will be monitored. Listed registry values must match the registry include pattern and not match the registry exclude pattern   * `enable_content_capture`   * `enable_hash_capture`  File system directory monitoring:   * `watch_delete_directory_changes`   * `watch_create_directory_changes`   * `watch_rename_directory_changes`   * `watch_attributes_directory_changes` (`macOS` is not supported at this time)   * `watch_permissions_directory_changes` (`macOS` is not supported at this time)  File system file monitoring:   * `watch_rename_file_changes`   * `watch_write_file_changes`   * `watch_create_file_changes`   * `watch_delete_file_changes`   * `watch_attributes_file_changes` (`macOS` is not supported at this time)   * `watch_permissions_file_changes` (`macOS` is not supported at this time)  Windows registry key and value monitoring:    * `watch_create_key_changes`   * `watch_delete_key_changes`   * `watch_rename_key_changes`   * `watch_set_value_changes`   * `watch_delete_value_changes`   * `watch_create_file_changes`
   # @param [Hash] opts the optional parameters
   # @return [RulegroupsRulesResponse]
   describe 'update_rules test' do

data/spec/api/firewall_management_api_spec.rb

@@ -146,13 +146,13 @@ describe 'FirewallManagementApi' do
     end
   end
 
-  # unit tests for delete_rule_groups
+  # unit tests for delete_rule_groups_0
   # Delete rule group entities by ID
   # @param ids The IDs of the rule groups to be deleted
   # @param [Hash] opts the optional parameters
   # @option opts [String] :comment Audit log comment for this action
   # @return [FwmgrApiQueryResponse]
-  describe 'delete_rule_groups test' do
+  describe 'delete_rule_groups_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
@@ -226,23 +226,23 @@ describe 'FirewallManagementApi' do
     end
   end
 
-  # unit tests for get_rule_groups
+  # unit tests for get_rule_groups_0
   # Get rule group entities by ID. These groups do not contain their rule entites, just the rule IDs in precedence order.
   # @param ids The IDs of the rule groups to retrieve
   # @param [Hash] opts the optional parameters
   # @return [FwmgrApiRuleGroupsResponse]
-  describe 'get_rule_groups test' do
+  describe 'get_rule_groups_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
   end
 
-  # unit tests for get_rules
+  # unit tests for get_rules_0
   # Get rule entities by ID (64-bit unsigned int as decimal string) or Family ID (32-character hexadecimal string)
   # @param ids The rules to retrieve, identified by ID
   # @param [Hash] opts the optional parameters
   # @return [FwmgrApiRulesResponse]
-  describe 'get_rules test' do
+  describe 'get_rules_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end
@@ -322,7 +322,7 @@ describe 'FirewallManagementApi' do
     end
   end
 
-  # unit tests for query_rule_groups
+  # unit tests for query_rule_groups_0
   # Find all rule group IDs matching the query with filter
   # @param [Hash] opts the optional parameters
   # @option opts [String] :sort Possible order by fields:
@@ -332,7 +332,7 @@ describe 'FirewallManagementApi' do
   # @option opts [String] :after A pagination token used with the `limit` parameter to manage pagination of results. On your first request, don't provide an `after` token. On subsequent requests, provide the `after` token from the previous response to continue from that place in the results.
   # @option opts [Integer] :limit Number of ids to return.
   # @return [FwmgrApiQueryResponse]
-  describe 'query_rule_groups test' do
+  describe 'query_rule_groups_0 test' do
     it 'should work' do
       # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
     end

data/spec/api/foundry_logscale_api_spec.rb

@@ -56,8 +56,11 @@ describe 'FoundryLogscaleApi' do
   # @option opts [String] :app_id Application ID.
   # @option opts [Boolean] :include_schema_generation Include generated schemas in the response
   # @option opts [Boolean] :include_test_data Include test data when executing searches
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
+  # @option opts [Boolean] :match_response_schema Whether to validate search results against their schema
   # @option opts [Boolean] :metadata Whether to include metadata in the response
   # @option opts [String] :mode Mode to execute the query under.
+  # @option opts [String] :x_cs_useruuid Requester UUID.
   # @return [ApidomainQueryResponseWrapperV1]
   describe 'create_saved_searches_dynamic_execute_alt_v1 test' do
     it 'should work' do
@@ -72,8 +75,11 @@ describe 'FoundryLogscaleApi' do
   # @option opts [String] :app_id Application ID.
   # @option opts [Boolean] :include_schema_generation Include generated schemas in the response
   # @option opts [Boolean] :include_test_data Include test data when executing searches
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
+  # @option opts [Boolean] :match_response_schema Whether to validate search results against their schema
   # @option opts [Boolean] :metadata Whether to include metadata in the response
   # @option opts [String] :mode Mode to execute the query under.
+  # @option opts [String] :x_cs_useruuid Requester UUID.
   # @return [ApidomainQueryResponseWrapperV1]
   describe 'create_saved_searches_dynamic_execute_v1 test' do
     it 'should work' do
@@ -88,7 +94,10 @@ describe 'FoundryLogscaleApi' do
   # @option opts [String] :app_id Application ID.
   # @option opts [Boolean] :detailed Whether to include search field details
   # @option opts [Boolean] :include_test_data Include test data when executing searches
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
+  # @option opts [Boolean] :match_response_schema Whether to validate search results against their schema
   # @option opts [Boolean] :metadata Whether to include metadata in the response
+  # @option opts [String] :x_cs_useruuid Requester UUID.
   # @return [ApidomainQueryResponseWrapperV1]
   describe 'create_saved_searches_execute_alt_v1 test' do
     it 'should work' do
@@ -103,7 +112,10 @@ describe 'FoundryLogscaleApi' do
   # @option opts [String] :app_id Application ID.
   # @option opts [Boolean] :detailed Whether to include search field details
   # @option opts [Boolean] :include_test_data Include test data when executing searches
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
+  # @option opts [Boolean] :match_response_schema Whether to validate search results against their schema
   # @option opts [Boolean] :metadata Whether to include metadata in the response
+  # @option opts [String] :x_cs_useruuid Requester UUID.
   # @return [ApidomainQueryResponseWrapperV1]
   describe 'create_saved_searches_execute_v1 test' do
     it 'should work' do
@@ -138,9 +150,13 @@ describe 'FoundryLogscaleApi' do
   # @param job_id Job ID for a previously executed async query
   # @param [Hash] opts the optional parameters
   # @option opts [String] :app_id Application ID.
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
+  # @option opts [Boolean] :job_status_only If set to true, result rows are dropped from the response and only the job status is returned
   # @option opts [String] :limit Maximum number of records to return.
+  # @option opts [Boolean] :match_response_schema Whether to validate search results against their schema
   # @option opts [Boolean] :metadata Whether to include metadata in the response
   # @option opts [String] :offset Starting pagination offset of records to return.
+  # @option opts [String] :x_cs_useruuid Requester UUID.
   # @return [ApidomainQueryResponseWrapperV1]
   describe 'get_saved_searches_execute_alt_v1 test' do
     it 'should work' do
@@ -153,9 +169,13 @@ describe 'FoundryLogscaleApi' do
   # @param job_id Job ID for a previously executed async query
   # @param [Hash] opts the optional parameters
   # @option opts [String] :app_id Application ID.
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
+  # @option opts [Boolean] :job_status_only If set to true, result rows are dropped from the response and only the job status is returned
   # @option opts [String] :limit Maximum number of records to return.
+  # @option opts [Boolean] :match_response_schema Whether to validate search results against their schema
   # @option opts [Boolean] :metadata Whether to include metadata in the response
   # @option opts [String] :offset Starting pagination offset of records to return.
+  # @option opts [String] :x_cs_useruuid Requester UUID.
   # @return [ApidomainQueryResponseWrapperV1]
   describe 'get_saved_searches_execute_v1 test' do
     it 'should work' do
@@ -167,6 +187,7 @@ describe 'FoundryLogscaleApi' do
   # Get the results of a saved search as a file
   # @param job_id Job ID for a previously executed async query
   # @param [Hash] opts the optional parameters
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
   # @option opts [String] :result_format Result Format
   # @return [File]
   describe 'get_saved_searches_job_results_download_alt_v1 test' do
@@ -179,6 +200,7 @@ describe 'FoundryLogscaleApi' do
   # Get the results of a saved search as a file
   # @param job_id Job ID for a previously executed async query
   # @param [Hash] opts the optional parameters
+  # @option opts [Boolean] :infer_json_types Whether to try to infer data types in json event response instead of returning map[string]string
   # @option opts [String] :result_format Result Format
   # @return [File]
   describe 'get_saved_searches_job_results_download_v1 test' do
@@ -187,10 +209,27 @@ describe 'FoundryLogscaleApi' do
     end
   end
 
+  # unit tests for ingest_data_async_v1
+  # Asynchronously ingest data into the application repository
+  # @param [Hash] opts the optional parameters
+  # @option opts [String] :data_content JSON data to ingest
+  # @option opts [File] :data_file Data file to ingest
+  # @option opts [String] :repo Repository name if not part of a foundry app
+  # @option opts [Array<String>] :tag Custom tag for ingested data in the form tag:value
+  # @option opts [String] :tag_source Tag the data with the specified source
+  # @option opts [Boolean] :test_data Tag the data with test-ingest
+  # @return [ClientDataIngestResponseWrapperV1]
+  describe 'ingest_data_async_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
   # unit tests for ingest_data_v1
-  # Ingest data into the application repository
-  # @param data_file Data file to ingest
+  # Synchronously ingest data into the application repository
   # @param [Hash] opts the optional parameters
+  # @option opts [String] :data_content JSON data to ingest
+  # @option opts [File] :data_file Data file to ingest
   # @option opts [Array<String>] :tag Custom tag for ingested data in the form tag:value
   # @option opts [String] :tag_source Tag the data with the specified source
   # @option opts [Boolean] :test_data Tag the data with test-ingest

data/spec/api/handle_api_spec.rb

@@ -0,0 +1,62 @@
+=begin
+Crimson Falcon - Ruby Client SDK
+
+Code auto-generated by OpenAPI Generator; DO NOT EDIT.
+
+MIT License
+
+Copyright (c) 2023 Crowdstrike
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Falcon::HandleApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'HandleApi' do
+  before do
+    # run before each test
+    @api_instance = Falcon::HandleApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of HandleApi' do
+    it 'should create an instance of HandleApi' do
+      expect(@api_instance).to be_instance_of(Falcon::HandleApi)
+    end
+  end
+
+  # unit tests for handle
+  # - Handle is responsible for producing the input message into the corresponded Kafka Topic
+  # @param [Hash] opts the optional parameters
+  # @return [Hash<String, String>]
+  describe 'handle test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end

data/spec/api/host_migration_api_spec.rb

@@ -0,0 +1,180 @@
+=begin
+Crimson Falcon - Ruby Client SDK
+
+Code auto-generated by OpenAPI Generator; DO NOT EDIT.
+
+MIT License
+
+Copyright (c) 2023 Crowdstrike
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
+
+=end
+
+require 'spec_helper'
+require 'json'
+
+# Unit tests for Falcon::HostMigrationApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'HostMigrationApi' do
+  before do
+    # run before each test
+    @api_instance = Falcon::HostMigrationApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of HostMigrationApi' do
+    it 'should create an instance of HostMigrationApi' do
+      expect(@api_instance).to be_instance_of(Falcon::HostMigrationApi)
+    end
+  end
+
+  # unit tests for create_migration_v1
+  # Create a device migration job.
+  # `device_ids` and `filter` are mutually exclusive. Filter takes precedence.
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [ApiCreateMigrationResponseV1]
+  describe 'create_migration_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_host_migration_ids_v1
+  # Query host migration IDs.
+  # Query host migration IDs.
+  # @param id The migration job to query
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :offset The offset to start retrieving records from
+  # @option opts [Integer] :limit The maximum records to return. [1-10000]
+  # @option opts [String] :sort The property to sort by.
+  # @option opts [String] :filter The filter expression that should be used to limit the results. Valid fields: hostname, status, source_cid, id, created_time, groups, hostgroups, static_host_groups, target_cid, migration_id, host_migration_id
+  # @return [MsaspecQueryResponse]
+  describe 'get_host_migration_ids_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_host_migrations_v1
+  # Get host migration details.
+  # # Events   The `events` field describes actions that have occurred to the host migration entity. Each object is defined by the `action` field. When `user` is present, it is the user who performed the action. `time` is when the action occurred.  ## Event actions  ### added  This action is emitted when the host migration is created.  ``` { \"action\": \"added\", \"user\": \"example@example.com\", \"time\": \"2024-01-01T00:00:00Z\" } ```  ### assigned_static_host_groups  This action is emitted when a user assigns static host groups to a host migration. `ids` are the ids of the new host groups that have been assigned.  ``` { \"action\": \"assigned_static_host_groups\", \"ids\": [\"foo\", \"bar\"],  \"user\": \"example@example.com\", \"time\": \"2024-01-01T00:00:00Z\" } ```  ### removed_static_host_groups  This action is emitted when a user removes static host groups from a host migration. `ids` are the ids of the host groups that have been removed.  ``` { \"action\": \"removed_static_host_groups\", \"ids\": [\"foo\", \"bar\"],  \"user\": \"example@example.com\", \"time\": \"2024-01-01T00:00:00Z\" } ```  ### queued  This action is emitted when the migration is started.  ``` { \"action\": \"queued\", \"user\": \"example@example.com\", \"time\": \"2024-01-01T00:00:00Z\" } ```  ### failed  This action is emitted when the host migration fails. `reason` is the reason for failure. `reason` can be `unsupported_sensor_version`, `unsupported_sensor_platform`, `host_missing`, `migration_expired`, or `internal_error`.  ``` { \"action\": \"failed\", \"reason\": \"unsupported_sensor_version\", \"time\": \"2024-01-01T00:00:00Z\" } ```  ### cancelled  This action is emitted when the migration has been cancelled.  ``` { \"action\": \"cancelled\", \"user\": \"example@example.com\", \"time\": \"2024-01-01T00:00:00Z\" } ```  ### completed  This action is emitted when the host has successfully migrated.  ``` { \"action\": \"completed\", \"time\": \"2024-01-01T00:00:00Z\" } ```  # Status Details  The `status_details` field is an optional field that provides some more details about the status of a failed host migration. It may be omitted or empty from a response.  ### internal_error  This status detail is provided when an internal occurs during a host migration.  ### canceled_by_user  This status detail is provided when a migration has been canceled by a user.  ### host_missing  This status detail is provided when a host migration is canceled because the source host can no longer be found.  ### migration_expired  This status detail is provided when a host migration is expired because the migration is too old.  ### migration_already_in_progress  This status detail is provided when attempting to start a host migration on a host that is already in progress in another migration.  ### source_host_unsupported_version  This status detail is provided when attempting to create or start a host migration when the sensor is on an unsupported version.  ### source_host_unsupported_platform  This status detail is provided when attempting to create or start a host migration when the sensor is an unsupported platform.
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [ApiGetHostMigrationResponseV1]
+  describe 'get_host_migrations_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_migration_destinations_v1
+  # Get destinations for a migration.
+  # `device_ids` and `filter` are mutually exclusive.
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [ApiGetMigrationDestinationsResponseV1]
+  describe 'get_migration_destinations_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_migration_ids_v1
+  # Query migration jobs.
+  # @param [Hash] opts the optional parameters
+  # @option opts [Integer] :offset The offset to start retrieving records from
+  # @option opts [Integer] :limit The maximum records to return. [1-10000]
+  # @option opts [String] :sort The property to sort by.
+  # @option opts [String] :filter The filter expression that should be used to limit the results. Valid fields: status, migration_status, created_by, created_time, name, id, migration_id, target_cid
+  # @return [MsaspecQueryResponse]
+  describe 'get_migration_ids_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for get_migrations_v1
+  # Get migration job details.
+  # @param ids The migration jobs of interest.
+  # @param [Hash] opts the optional parameters
+  # @return [ApiGetMigrationsResponseV1]
+  describe 'get_migrations_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for host_migration_aggregates_v1
+  # Get host migration aggregates as specified via json in request body.
+  # Get host migration aggregates as specified via json in request body.  # Supported Types  Both types support the following FQL filter properties: `groups`, `hostgroups`, `static_host_groups`, `hostname`, `status`, `target_cid`, `source_cid`, `migration_id`, `id`, `host_migration_id`, `created_time`.  The values `groups` and `hostgroups` are aliases for `static_host_groups`.  The value `host_migration_id` is an alias for `id`  ## Terms `\"type\": \"terms\"`  Supported `field` values: `groups`, `hostgroups`, `static_host_groups`, `hostname`, `status`, `target_cid`, `source_cid`, `migration_id`, `id`, `host_migration_id`.  `sort` must be done on the same value as `field` and include a direction (`asc` or `desc`). Supports all FQL fields except for `groups`, `hostgroups`, or `static_host_groups`.  Examples sort value: `status|asc` or `created_by|desc`   ## Date Range `\"type\": \"date_range\"`  Supported `field` fields: `created_time`.  Does not support `sort`, `size`, or `from`.
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [MsaAggregatesResponse]
+  describe 'host_migration_aggregates_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for host_migrations_actions_v1
+  # Perform an action on host migrations.
+  # The available actions are `add_host_groups`, `remove_host_groups`, and `remove_hosts`.  FQL filter supports the following fields: `groups`, `hostgroups`, `static_host_groups`, `hostname`, `status`, `target_cid`, `source_cid`, `migration_id`, `id`, `host_migration_id`, `created_time`.  These actions only works if the migration has not started.  `add_host_groups` adds static host groups to the selected hosts in a migration. This action accepts the following action parameter: `{ \"name\": \"host_group\": \"value\": \"$host_group_id\" }`. Action parameters can be repeated to add multiple static host groups in a single request.  `remove_host_groups` removes static host groups from the selected hosts in a migration. This action accepts the following action parameter: `{ \"name\": \"host_group\": \"value\": \"$host_group_id\" }`. Action parameters can be repeated to remove multiple static host groups in a single request.  `remove_hosts` removes the selected hosts from a migration. This action does not accept any action parameters.
+  # @param id The migration job to perform actions on
+  # @param action_name The action to perform
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [MsaspecQueryResponse]
+  describe 'host_migrations_actions_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for migration_aggregates_v1
+  # Get migration aggregates as specified via json in request body.
+  # Get migration aggregates as specified via json in request body.  # Supported Types  Both types support the following FQL filter props: `name`, `id`, `migration_id`, `target_cid`, `status`, `migration_status`, `created_by`, `created_time`.  The value `migration_status` is an alias for `status`.  The value `migration_id` is an alias for `id`.  ## Terms `\"type\": \"terms\"`  Supported `field` values: `name`, `id`, `migration_id,` `target_cid`, `status`, `migration_status`, `created_by`.  `sort` on `terms` type must be done on the same value as `field` and include a direction (`asc` or `desc`). Supports all supported FQL fields.  Examples sort value: `status|asc` or `created_by|desc`.   ## Date Range `\"type\": \"date_range\"`  Supported `field` fields: `created_time`.  Does not support `sort`, `size`, or `from`.
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [MsaAggregatesResponse]
+  describe 'migration_aggregates_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+  # unit tests for migrations_actions_v1
+  # Perform an action on a migration job.
+  # The available actions are `start_migration`, `cancel_migration`, `rename_migration`, and `delete_migration`.  `start_migration` starts the selected migrations. This action only works if the migration has not started. This action does not accept any action parameters. Only one migration may be started per request.  `cancel_migration` cancels the selected migrations. This actions only works if the migration has started and not completed. This action does not accept any action parameters.  `rename_migration` renames the selected migrations. This action can be called at any time. Only 1 action parameter may be supplied. Action parameters take the form of `{\"name\": \"migration_name\": \"value\": \"$new_migration_name\"}`.  `delete_migration` deletes the selected migrations. This action only works if the migration has not started. This action does not accept any action parameters.
+  # @param action_name The action to perform
+  # @param body
+  # @param [Hash] opts the optional parameters
+  # @return [MsaspecQueryResponse]
+  describe 'migrations_actions_v1 test' do
+    it 'should work' do
+      # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
+    end
+  end
+
+end