vsphere-automation-appliance 0.1.0 → 0.2.0

data/docs/NetworkingFirewallInboundApi.md

@@ -5,7 +5,7 @@ All URIs are relative to *https://<vcenter>/rest*
 Method | HTTP request | Description
 ------------- | ------------- | -------------
 [**get**](NetworkingFirewallInboundApi.md#get) | **GET** /appliance/networking/firewall/inbound | Get the ordered list of firewall rules. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
-[**set**](NetworkingFirewallInboundApi.md#set) | **PUT** /appliance/networking/firewall/inbound | Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows: <ol> <li> \"address\": \"10.112.0.1\", \"prefix\": 0, \"interface_name\": \"*\",\"policy\": \"REJECT\"<br> \"address\": \"10.112.0.1\", \"prefix\": 0, \"interface_name\": \"nic0\",\"policy\": \"ACCEPT\"<br> </li> </ol> In the above example, the first rule drops all packets originating from 10.112.0.1 and<br> the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
+[**set**](NetworkingFirewallInboundApi.md#set) | **PUT** /appliance/networking/firewall/inbound | Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows: <table> <tr> <th>Address</th><th>Prefix</th><th>Interface Name</th><th>Policy</th> </tr> <tr> <td>10.112.0.1</td><td>0</td><td>*</td><td>REJECT</td> </tr> <tr> <td>10.112.0.1</td><td>0</td><td>nic0</td><td>ACCEPT</td> </tr> </table> In the above example, the first rule drops all packets originating from 10.112.0.1 and<br> the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
 
 
 # **get**
@@ -17,6 +17,13 @@ Get the ordered list of firewall rules. Within the list of traffic rules, rules
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingFirewallInboundApi.new
 
@@ -38,31 +45,38 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **set**
-> set(appliance_networking_firewall_inbound_set)
+> set(request_body)
 
-Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows: <ol> <li> \"address\": \"10.112.0.1\", \"prefix\": 0, \"interface_name\": \"*\",\"policy\": \"REJECT\"<br> \"address\": \"10.112.0.1\", \"prefix\": 0, \"interface_name\": \"nic0\",\"policy\": \"ACCEPT\"<br> </li> </ol> In the above example, the first rule drops all packets originating from 10.112.0.1 and<br> the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
+Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows: <table> <tr> <th>Address</th><th>Prefix</th><th>Interface Name</th><th>Policy</th> </tr> <tr> <td>10.112.0.1</td><td>0</td><td>*</td><td>REJECT</td> </tr> <tr> <td>10.112.0.1</td><td>0</td><td>nic0</td><td>ACCEPT</td> </tr> </table> In the above example, the first rule drops all packets originating from 10.112.0.1 and<br> the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
 
 ### Example
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingFirewallInboundApi.new
-appliance_networking_firewall_inbound_set = VSphereAutomation::ApplianceNetworkingFirewallInboundSet.new # ApplianceNetworkingFirewallInboundSet | 
+request_body = Appliance::ApplianceNetworkingFirewallInboundSet.new # ApplianceNetworkingFirewallInboundSet | 
 
 begin
-  #Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows: <ol> <li> \"address\": \"10.112.0.1\", \"prefix\": 0, \"interface_name\": \"*\",\"policy\": \"REJECT\"<br> \"address\": \"10.112.0.1\", \"prefix\": 0, \"interface_name\": \"nic0\",\"policy\": \"ACCEPT\"<br> </li> </ol> In the above example, the first rule drops all packets originating from 10.112.0.1 and<br> the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
-  api_instance.set(appliance_networking_firewall_inbound_set)
+  #Set the ordered list of firewall rules to allow or deny traffic from one or more incoming IP addresses. This overwrites the existing firewall rules and creates a new rule list. Within the list of traffic rules, rules are processed in order of appearance, from top to bottom. For example, the list of rules can be as follows: <table> <tr> <th>Address</th><th>Prefix</th><th>Interface Name</th><th>Policy</th> </tr> <tr> <td>10.112.0.1</td><td>0</td><td>*</td><td>REJECT</td> </tr> <tr> <td>10.112.0.1</td><td>0</td><td>nic0</td><td>ACCEPT</td> </tr> </table> In the above example, the first rule drops all packets originating from 10.112.0.1 and<br> the second rule accepts all packets originating from 10.112.0.1 only on nic0. In effect, the second rule is always ignored which is not desired, hence the order has to be swapped. When a connection matches a firewall rule, further processing for the connection stops, and the appliance ignores any additional firewall rules you have set.
+  api_instance.set(request_body)
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling NetworkingFirewallInboundApi->set: #{e}"
 end
@@ -72,7 +86,7 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **appliance_networking_firewall_inbound_set** | [**ApplianceNetworkingFirewallInboundSet**](ApplianceNetworkingFirewallInboundSet.md)|  | 
+ **request_body** | [**ApplianceNetworkingFirewallInboundSet**](ApplianceNetworkingFirewallInboundSet.md)|  | 
 
 ### Return type
 
@@ -80,12 +94,12 @@ nil (empty response body)
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/NetworkingInterfacesApi.md

@@ -17,6 +17,13 @@ Get information about a particular network interface.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingInterfacesApi.new
 interface_name = 'interface_name_example' # String | Network interface, for example, \"nic0\".
@@ -42,12 +49,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
@@ -60,6 +67,13 @@ Get list of available network interfaces, including those that are not yet confi
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingInterfacesApi.new
 
@@ -81,12 +95,12 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/NetworkingInterfacesIpv4Api.md

@@ -17,6 +17,13 @@ Get IPv4 network configuration for specific NIC.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingInterfacesIpv4Api.new
 interface_name = 'interface_name_example' # String | The Network interface to query, for example, \"nic0\".
@@ -42,17 +49,17 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **set**
-> set(interface_name, appliance_networking_interfaces_ipv4_set)
+> set(interface_name, request_body)
 
 Set IPv4 network configuration for specific network interface.
 
@@ -60,14 +67,21 @@ Set IPv4 network configuration for specific network interface.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingInterfacesIpv4Api.new
 interface_name = 'interface_name_example' # String | Network interface to update, for example, \"nic0\".
-appliance_networking_interfaces_ipv4_set = VSphereAutomation::ApplianceNetworkingInterfacesIpv4Set.new # ApplianceNetworkingInterfacesIpv4Set | 
+request_body = Appliance::ApplianceNetworkingInterfacesIpv4Set.new # ApplianceNetworkingInterfacesIpv4Set | 
 
 begin
   #Set IPv4 network configuration for specific network interface.
-  api_instance.set(interface_name, appliance_networking_interfaces_ipv4_set)
+  api_instance.set(interface_name, request_body)
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling NetworkingInterfacesIpv4Api->set: #{e}"
 end
@@ -78,7 +92,7 @@ end
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **interface_name** | **String**| Network interface to update, for example, \"nic0\". | 
- **appliance_networking_interfaces_ipv4_set** | [**ApplianceNetworkingInterfacesIpv4Set**](ApplianceNetworkingInterfacesIpv4Set.md)|  | 
+ **request_body** | [**ApplianceNetworkingInterfacesIpv4Set**](ApplianceNetworkingInterfacesIpv4Set.md)|  | 
 
 ### Return type
 
@@ -86,12 +100,12 @@ nil (empty response body)
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/NetworkingInterfacesIpv6Api.md

@@ -17,6 +17,13 @@ Get IPv6 network configuration for specific interface.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingInterfacesIpv6Api.new
 interface_name = 'interface_name_example' # String | Network interface to query, for example, \"nic0\".
@@ -42,17 +49,17 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **set**
-> set(interface_name, appliance_networking_interfaces_ipv6_set)
+> set(interface_name, request_body)
 
 Set IPv6 network configuration for specific interface.
 
@@ -60,14 +67,21 @@ Set IPv6 network configuration for specific interface.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingInterfacesIpv6Api.new
 interface_name = 'interface_name_example' # String | Network interface to update, for example, \"nic0\".
-appliance_networking_interfaces_ipv6_set = VSphereAutomation::ApplianceNetworkingInterfacesIpv6Set.new # ApplianceNetworkingInterfacesIpv6Set | 
+request_body = Appliance::ApplianceNetworkingInterfacesIpv6Set.new # ApplianceNetworkingInterfacesIpv6Set | 
 
 begin
   #Set IPv6 network configuration for specific interface.
-  api_instance.set(interface_name, appliance_networking_interfaces_ipv6_set)
+  api_instance.set(interface_name, request_body)
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling NetworkingInterfacesIpv6Api->set: #{e}"
 end
@@ -78,7 +92,7 @@ end
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **interface_name** | **String**| Network interface to update, for example, \"nic0\". | 
- **appliance_networking_interfaces_ipv6_set** | [**ApplianceNetworkingInterfacesIpv6Set**](ApplianceNetworkingInterfacesIpv6Set.md)|  | 
+ **request_body** | [**ApplianceNetworkingInterfacesIpv6Set**](ApplianceNetworkingInterfacesIpv6Set.md)|  | 
 
 ### Return type
 
@@ -86,12 +100,12 @@ nil (empty response body)
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/NetworkingNoProxyApi.md

@@ -17,6 +17,13 @@ Returns servers for which no proxy configuration will be applied.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingNoProxyApi.new
 
@@ -38,17 +45,17 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **set**
-> set(appliance_networking_no_proxy_set)
+> set(request_body)
 
 Sets servers for which no proxy configuration should be applied. This operation sets environment variables. In order for this operation to take effect, a logout from appliance or a service restart is required. If IPv4 is enabled, \"127.0.0.1\" and \"localhost\" will always bypass the proxy (even if they are not explicitly configured).
 
@@ -56,13 +63,20 @@ Sets servers for which no proxy configuration should be applied. This operation
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingNoProxyApi.new
-appliance_networking_no_proxy_set = VSphereAutomation::ApplianceNetworkingNoProxySet.new # ApplianceNetworkingNoProxySet | 
+request_body = Appliance::ApplianceNetworkingNoProxySet.new # ApplianceNetworkingNoProxySet | 
 
 begin
   #Sets servers for which no proxy configuration should be applied. This operation sets environment variables. In order for this operation to take effect, a logout from appliance or a service restart is required. If IPv4 is enabled, \"127.0.0.1\" and \"localhost\" will always bypass the proxy (even if they are not explicitly configured).
-  api_instance.set(appliance_networking_no_proxy_set)
+  api_instance.set(request_body)
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling NetworkingNoProxyApi->set: #{e}"
 end
@@ -72,7 +86,7 @@ end
 
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
- **appliance_networking_no_proxy_set** | [**ApplianceNetworkingNoProxySet**](ApplianceNetworkingNoProxySet.md)|  | 
+ **request_body** | [**ApplianceNetworkingNoProxySet**](ApplianceNetworkingNoProxySet.md)|  | 
 
 ### Return type
 
@@ -80,12 +94,12 @@ nil (empty response body)
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 

data/docs/NetworkingProxyApi.md

@@ -8,7 +8,7 @@ Method | HTTP request | Description
 [**get**](NetworkingProxyApi.md#get) | **GET** /appliance/networking/proxy/{protocol} | Gets the proxy configuration for a specific protocol.
 [**list**](NetworkingProxyApi.md#list) | **GET** /appliance/networking/proxy | Gets proxy configuration for all configured protocols.
 [**set**](NetworkingProxyApi.md#set) | **PUT** /appliance/networking/proxy/{protocol} | Configures which proxy server to use for the specified protocol. This operation sets environment variables for using proxy. In order for this configuration to take effect a logout / service restart is required.
-[**test**](NetworkingProxyApi.md#test) | **POST** /appliance/networking/proxy/{protocol}?action=test | Tests a proxy configuration by testing the connection to the proxy server and test host.
+[**test**](NetworkingProxyApi.md#test) | **POST** /appliance/networking/proxy/{protocol} | Tests a proxy configuration by testing the connection to the proxy server and test host.
 
 
 # **delete**
@@ -20,6 +20,13 @@ Deletes a proxy configuration for a specific protocol.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingProxyApi.new
 protocol = 'protocol_example' # String | ID whose proxy is to be deleted.
@@ -44,12 +51,12 @@ nil (empty response body)
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
@@ -62,6 +69,13 @@ Gets the proxy configuration for a specific protocol.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingProxyApi.new
 protocol = 'protocol_example' # String | The protocol whose proxy configuration is requested.
@@ -87,12 +101,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
@@ -105,6 +119,13 @@ Gets proxy configuration for all configured protocols.
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingProxyApi.new
 
@@ -126,17 +147,17 @@ This endpoint does not need any parameter.
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: Not defined
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **set**
-> set(protocol, appliance_networking_proxy_set)
+> set(protocol, request_body)
 
 Configures which proxy server to use for the specified protocol. This operation sets environment variables for using proxy. In order for this configuration to take effect a logout / service restart is required.
 
@@ -144,14 +165,21 @@ Configures which proxy server to use for the specified protocol. This operation
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingProxyApi.new
 protocol = 'protocol_example' # String | The protocol for which proxy should be set.
-appliance_networking_proxy_set = VSphereAutomation::ApplianceNetworkingProxySet.new # ApplianceNetworkingProxySet | 
+request_body = Appliance::ApplianceNetworkingProxySet.new # ApplianceNetworkingProxySet | 
 
 begin
   #Configures which proxy server to use for the specified protocol. This operation sets environment variables for using proxy. In order for this configuration to take effect a logout / service restart is required.
-  api_instance.set(protocol, appliance_networking_proxy_set)
+  api_instance.set(protocol, request_body)
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling NetworkingProxyApi->set: #{e}"
 end
@@ -162,7 +190,7 @@ end
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **protocol** | **String**| The protocol for which proxy should be set. | 
- **appliance_networking_proxy_set** | [**ApplianceNetworkingProxySet**](ApplianceNetworkingProxySet.md)|  | 
+ **request_body** | [**ApplianceNetworkingProxySet**](ApplianceNetworkingProxySet.md)|  | 
 
 ### Return type
 
@@ -170,17 +198,17 @@ nil (empty response body)
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json
 
 
 
 # **test**
-> ApplianceNetworkingProxyTestResult test(protocol, appliance_networking_proxy_test)
+> ApplianceNetworkingProxyTestResult test(protocol, action, request_body)
 
 Tests a proxy configuration by testing the connection to the proxy server and test host.
 
@@ -188,14 +216,22 @@ Tests a proxy configuration by testing the connection to the proxy server and te
 ```ruby
 # load the gem
 require 'vsphere-automation-appliance'
+# setup authorization
+VSphereAutomation::Configuration.new.tap do |config|
+  # Configure API key authorization: api_key
+  config.api_key['vmware-api-session-id'] = 'YOUR API KEY'
+  # Uncomment the following line to set a prefix for the API key, e.g. 'Bearer' (defaults to nil)
+  #config.api_key_prefix['vmware-api-session-id'] = 'Bearer'
+end
 
 api_instance = VSphereAutomation::Appliance::NetworkingProxyApi.new
 protocol = 'protocol_example' # String | Protocol whose proxy is to be tested.
-appliance_networking_proxy_test = VSphereAutomation::ApplianceNetworkingProxyTest.new # ApplianceNetworkingProxyTest | 
+action = 'action_example' # String | action=test
+request_body = Appliance::ApplianceNetworkingProxyTest.new # ApplianceNetworkingProxyTest | 
 
 begin
   #Tests a proxy configuration by testing the connection to the proxy server and test host.
-  result = api_instance.test(protocol, appliance_networking_proxy_test)
+  result = api_instance.test(protocol, action, request_body)
   p result
 rescue VSphereAutomation::ApiError => e
   puts "Exception when calling NetworkingProxyApi->test: #{e}"
@@ -207,7 +243,8 @@ end
 Name | Type | Description  | Notes
 ------------- | ------------- | ------------- | -------------
  **protocol** | **String**| Protocol whose proxy is to be tested. | 
- **appliance_networking_proxy_test** | [**ApplianceNetworkingProxyTest**](ApplianceNetworkingProxyTest.md)|  | 
+ **action** | **String**| action=test | 
+ **request_body** | [**ApplianceNetworkingProxyTest**](ApplianceNetworkingProxyTest.md)|  | 
 
 ### Return type
 
@@ -215,12 +252,12 @@ Name | Type | Description  | Notes
 
 ### Authorization
 
-No authorization required
+[api_key](../README.md#api_key)
 
 ### HTTP request headers
 
  - **Content-Type**: application/json
- - **Accept**: */*
+ - **Accept**: application/json