vsphere-automation-cis 0.1.0

data/docs/TasksApi.md

@@ -0,0 +1,159 @@
+# VSphereAutomation::CIS::TasksApi
+
+All URIs are relative to *https://<vcenter>/rest*
+
+Method | HTTP request | Description
+------------- | ------------- | -------------
+[**cancel**](TasksApi.md#cancel) | **POST** /cis/tasks/{task}?action=cancel | Cancel a running operation associated with the task. This is the best effort attempt. Operation may not be cancelled anymore once it reaches certain stage.
+[**get**](TasksApi.md#get) | **GET** /cis/tasks/{task} | Returns information about a task.
+[**list**](TasksApi.md#list) | **GET** /cis/tasks | Returns information about at most 1000 visible (subject to permission checks) tasks matching the Tasks.FilterSpec. All tasks must be in the same provider.
+
+
+# **cancel**
+> cancel(task)
+
+Cancel a running operation associated with the task. This is the best effort attempt. Operation may not be cancelled anymore once it reaches certain stage.
+
+### Example
+```ruby
+# load the gem
+require 'vsphere-automation-cis'
+
+api_instance = VSphereAutomation::CIS::TasksApi.new
+task = 'task_example' # String | Task identifier. The parameter must be an identifier for the resource type: cis.task.
+
+begin
+  #Cancel a running operation associated with the task. This is the best effort attempt. Operation may not be cancelled anymore once it reaches certain stage.
+  api_instance.cancel(task)
+rescue VSphereAutomation::ApiError => e
+  puts "Exception when calling TasksApi->cancel: #{e}"
+end
+```
+
+### Parameters
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+ **task** | **String**| Task identifier. The parameter must be an identifier for the resource type: cis.task. | 
+
+### Return type
+
+nil (empty response body)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+ - **Content-Type**: Not defined
+ - **Accept**: */*
+
+
+
+# **get**
+> CisTasksResult get(task, opts)
+
+Returns information about a task.
+
+### Example
+```ruby
+# load the gem
+require 'vsphere-automation-cis'
+
+api_instance = VSphereAutomation::CIS::TasksApi.new
+task = 'task_example' # String | Task identifier. The parameter must be an identifier for the resource type: cis.task.
+opts = {
+  spec_return_all: true, # BOOLEAN | If true, all data, including operation-specific data, will be returned, otherwise only the data described in Info will be returned. If unset, only the data described in Info will be returned.
+  spec_exclude_result: true # BOOLEAN | If true, the result will not be included in the task information, otherwise it will be included. If unset, the result of the operation will be included in the task information.
+}
+
+begin
+  #Returns information about a task.
+  result = api_instance.get(task, opts)
+  p result
+rescue VSphereAutomation::ApiError => e
+  puts "Exception when calling TasksApi->get: #{e}"
+end
+```
+
+### Parameters
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+ **task** | **String**| Task identifier. The parameter must be an identifier for the resource type: cis.task. | 
+ **spec_return_all** | **BOOLEAN**| If true, all data, including operation-specific data, will be returned, otherwise only the data described in Info will be returned. If unset, only the data described in Info will be returned. | [optional] 
+ **spec_exclude_result** | **BOOLEAN**| If true, the result will not be included in the task information, otherwise it will be included. If unset, the result of the operation will be included in the task information. | [optional] 
+
+### Return type
+
+[**CisTasksResult**](CisTasksResult.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+ - **Content-Type**: Not defined
+ - **Accept**: */*
+
+
+
+# **list**
+> CisTasksListResult list(opts)
+
+Returns information about at most 1000 visible (subject to permission checks) tasks matching the Tasks.FilterSpec. All tasks must be in the same provider.
+
+### Example
+```ruby
+# load the gem
+require 'vsphere-automation-cis'
+
+api_instance = VSphereAutomation::CIS::TasksApi.new
+opts = {
+  filter_spec_tasks: ['filter_spec_tasks_example'], # Array<String> | Identifiers of tasks that can match the filter. This field may be unset if Tasks.FilterSpec.services is specified. Currently all tasks must be from the same provider. If unset or empty, tasks with any identifier will match the filter. When clients pass a value of this structure as a parameter, the field must contain identifiers for the resource type: cis.task. When operations return a value of this structure as a result, the field will contain identifiers for the resource type: cis.task.
+  result_spec_return_all: true, # BOOLEAN | If true, all data, including operation-specific data, will be returned, otherwise only the data described in Info will be returned. If unset, only the data described in Info will be returned.
+  result_spec_exclude_result: true, # BOOLEAN | If true, the result will not be included in the task information, otherwise it will be included. If unset, the result of the operation will be included in the task information.
+  filter_spec_services: ['filter_spec_services_example'], # Array<String> | Identifiers of services. Tasks created by operations in these services match the filter (see CommonInfo.service). This field may be unset if Tasks.FilterSpec.tasks is specified. Currently all services must be from the same provider. If this field is unset or empty, tasks for all services will match the filter. When clients pass a value of this structure as a parameter, the field must contain identifiers for the resource type: vapi.service. When operations return a value of this structure as a result, the field will contain identifiers for the resource type: vapi.service.
+  filter_spec_status: ['filter_spec_status_example'], # Array<String> | Status that a task must have to match the filter (see CommonInfo.status). If unset or empty, tasks with any status match the filter.
+  filter_spec_targets: nil, # Array<Object> | Identifiers of the targets the operation for the associated task created or was performed on (see CommonInfo.target). If unset or empty, tasks associated with operations on any target match the filter.
+  filter_spec_users: ['filter_spec_users_example'] # Array<String> | Users who must have initiated the operation for the associated task to match the filter (see CommonInfo.user). If unset or empty, tasks associated with operations initiated by any user match the filter.
+}
+
+begin
+  #Returns information about at most 1000 visible (subject to permission checks) tasks matching the Tasks.FilterSpec. All tasks must be in the same provider.
+  result = api_instance.list(opts)
+  p result
+rescue VSphereAutomation::ApiError => e
+  puts "Exception when calling TasksApi->list: #{e}"
+end
+```
+
+### Parameters
+
+Name | Type | Description  | Notes
+------------- | ------------- | ------------- | -------------
+ **filter_spec_tasks** | [**Array&lt;String&gt;**](String.md)| Identifiers of tasks that can match the filter. This field may be unset if Tasks.FilterSpec.services is specified. Currently all tasks must be from the same provider. If unset or empty, tasks with any identifier will match the filter. When clients pass a value of this structure as a parameter, the field must contain identifiers for the resource type: cis.task. When operations return a value of this structure as a result, the field will contain identifiers for the resource type: cis.task. | [optional] 
+ **result_spec_return_all** | **BOOLEAN**| If true, all data, including operation-specific data, will be returned, otherwise only the data described in Info will be returned. If unset, only the data described in Info will be returned. | [optional] 
+ **result_spec_exclude_result** | **BOOLEAN**| If true, the result will not be included in the task information, otherwise it will be included. If unset, the result of the operation will be included in the task information. | [optional] 
+ **filter_spec_services** | [**Array&lt;String&gt;**](String.md)| Identifiers of services. Tasks created by operations in these services match the filter (see CommonInfo.service). This field may be unset if Tasks.FilterSpec.tasks is specified. Currently all services must be from the same provider. If this field is unset or empty, tasks for all services will match the filter. When clients pass a value of this structure as a parameter, the field must contain identifiers for the resource type: vapi.service. When operations return a value of this structure as a result, the field will contain identifiers for the resource type: vapi.service. | [optional] 
+ **filter_spec_status** | [**Array&lt;String&gt;**](String.md)| Status that a task must have to match the filter (see CommonInfo.status). If unset or empty, tasks with any status match the filter. | [optional] 
+ **filter_spec_targets** | [**Array&lt;Object&gt;**](Object.md)| Identifiers of the targets the operation for the associated task created or was performed on (see CommonInfo.target). If unset or empty, tasks associated with operations on any target match the filter. | [optional] 
+ **filter_spec_users** | [**Array&lt;String&gt;**](String.md)| Users who must have initiated the operation for the associated task to match the filter (see CommonInfo.user). If unset or empty, tasks associated with operations initiated by any user match the filter. | [optional] 
+
+### Return type
+
+[**CisTasksListResult**](CisTasksListResult.md)
+
+### Authorization
+
+No authorization required
+
+### HTTP request headers
+
+ - **Content-Type**: Not defined
+ - **Accept**: */*
+
+
+

data/docs/VapiStdDynamicID.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdDynamicID
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** | The type of resource being identified (for example {@code com.acme.Person}). <p> {@term Services} that contain {@term operations} for creating and deleting resources typically contain a {@term constant} specifying the resource type for the resources being created and deleted. The API metamodel metadata {@term services} include a {@term service} that allows retrieving all the known resource types. | 
+**id** | **String** | The identifier for a resource whose type is specified by {@link #type}. | 
+
+

data/docs/VapiStdErrorsAlreadyExists.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsAlreadyExists
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsAlreadyExistsError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsAlreadyExistsError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsAlreadyExists**](VapiStdErrorsAlreadyExists.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsErrorError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsErrorError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsError**](VapiStdErrorsError.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsInvalidArgument.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsInvalidArgument
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsInvalidArgumentError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsInvalidArgumentError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsInvalidArgument**](VapiStdErrorsInvalidArgument.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsNotAllowedInCurrentState.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsNotAllowedInCurrentState
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsNotAllowedInCurrentStateError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsNotAllowedInCurrentStateError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsNotAllowedInCurrentState**](VapiStdErrorsNotAllowedInCurrentState.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsNotFound.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsNotFound
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsNotFoundError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsNotFoundError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsNotFound**](VapiStdErrorsNotFound.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsResourceInaccessible.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsResourceInaccessible
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsResourceInaccessibleError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsResourceInaccessibleError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsResourceInaccessible**](VapiStdErrorsResourceInaccessible.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsServiceUnavailable.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsServiceUnavailable
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsServiceUnavailableError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsServiceUnavailableError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsServiceUnavailable**](VapiStdErrorsServiceUnavailable.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsUnauthenticated.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsUnauthenticated
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsUnauthenticatedError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsUnauthenticatedError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsUnauthenticated**](VapiStdErrorsUnauthenticated.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsUnauthorized.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsUnauthorized
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsUnauthorizedError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsUnauthorizedError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsUnauthorized**](VapiStdErrorsUnauthorized.md) |  | [optional] 
+
+

data/docs/VapiStdErrorsUnsupported.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsUnsupported
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**messages** | [**Array<VapiStdLocalizableMessage>**](VapiStdLocalizableMessage.md) | Stack of one or more localizable messages for human {@term error} consumers. <p> The message at the top of the stack (first in the list) describes the {@term error} from the perspective of the {@term operation} the client invoked. Each subsequent message in the stack describes the \"cause\" of the prior message. | 
+**data** | [**Object**](.md) | Data to facilitate clients responding to the {@term operation} reporting a standard {@term error} to indicating that it was unable to complete successfully. <p> {@term Operations} may provide data that clients can use when responding to {@term errors}.  Since the data that clients need may be specific to the context of the {@term operation} reporting the {@term error}, different {@term operations} that report the same {@term error} may provide different data in the {@term error}.  The documentation for each each {@term operation} will describe what, if any, data it provides for each {@term error} it reports. The {@link ArgumentLocations}, {@link FileLocations}, and {@link TransientIndication} {@term structures} are intended as possible values for this {@term field}.  {@link vapi.std.DynamicID} may also be useful as a value for this {@term field} (although that is not its primary purpose).  Some {@term services} may provide their own specific {@term structures} for use as the value of this {@term field} when reporting {@term errors} from their {@term operations}. | [optional] 
+
+

data/docs/VapiStdErrorsUnsupportedError.md

@@ -0,0 +1,9 @@
+# VSphereAutomation::CIS::VapiStdErrorsUnsupportedError
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**type** | **String** |  | [optional] 
+**value** | [**VapiStdErrorsUnsupported**](VapiStdErrorsUnsupported.md) |  | [optional] 
+
+

data/docs/VapiStdLocalizableMessage.md

@@ -0,0 +1,10 @@
+# VSphereAutomation::CIS::VapiStdLocalizableMessage
+
+## Properties
+Name | Type | Description | Notes
+------------ | ------------- | ------------- | -------------
+**id** | **String** | Unique identifier of the localizable string or message template. <p> This identifier is typically used to retrieve a locale-specific string or message template from a message catalog. | 
+**default_message** | **String** | The value of this localizable string or message template in the {@code en_US} (English) locale.  If {@link #id} refers to a message template, the default message will contain the substituted arguments. This value can be used by clients that do not need to display strings and messages in the native language of the user.  It could also be used as a fallback if a client is unable to access the appropriate message catalog. | 
+**args** | **Array<String>** | Arguments to be substituted into a message template. | 
+
+

data/git_push.sh

@@ -0,0 +1,55 @@
+#!/bin/sh
+#
+# Generated by: https://openapi-generator.tech
+#
+# ref: https://help.github.com/articles/adding-an-existing-project-to-github-using-the-command-line/
+#
+# Usage example: /bin/sh ./git_push.sh wing328 openapi-pestore-perl "minor update"
+
+git_user_id=$1
+git_repo_id=$2
+release_note=$3
+
+if [ "$git_user_id" = "" ]; then
+    git_user_id="GIT_USER_ID"
+    echo "[INFO] No command line input provided. Set \$git_user_id to $git_user_id"
+fi
+
+if [ "$git_repo_id" = "" ]; then
+    git_repo_id="GIT_REPO_ID"
+    echo "[INFO] No command line input provided. Set \$git_repo_id to $git_repo_id"
+fi
+
+if [ "$release_note" = "" ]; then
+    release_note="Minor update"
+    echo "[INFO] No command line input provided. Set \$release_note to $release_note"
+fi
+
+# Initialize the local directory as a Git repository
+git init
+
+# Adds the files in the local repository and stages them for commit.
+git add .
+
+# Commits the tracked changes and prepares them to be pushed to a remote repository.
+git commit -m "$release_note"
+
+# Sets the new remote
+git_remote=`git remote`
+if [ "$git_remote" = "" ]; then # git remote not defined
+
+    if [ "$GIT_TOKEN" = "" ]; then
+        echo "[INFO] \$GIT_TOKEN (environment variable) is not set. Using the git credential in your environment."
+        git remote add origin https://github.com/${git_user_id}/${git_repo_id}.git
+    else
+        git remote add origin https://${git_user_id}:${GIT_TOKEN}@github.com/${git_user_id}/${git_repo_id}.git
+    fi
+
+fi
+
+git pull origin master
+
+# Pushes (Forces) the changes in the local repository up to the remote repository
+echo "Git pushing to https://github.com/${git_user_id}/${git_repo_id}.git"
+git push origin master 2>&1 | grep -v 'To https'
+