ionoscloud 5.1.1 → 5.1.2

data/spec/api/nic_api_spec.rb

@@ -1,251 +0,0 @@
-=begin
-#CLOUD API
-
-#An enterprise-grade Infrastructure is provided as a Service (IaaS) solution that can be managed through a browser-based \"Data Center Designer\" (DCD) tool or via an easy to use API.   The API allows you to perform a variety of management tasks such as spinning up additional servers, adding volumes, adjusting networking, and so forth. It is designed to allow users to leverage the same power and flexibility found within the DCD visual tool. Both tools are consistent with their concepts and lend well to making the experience smooth and intuitive.
-
-The version of the OpenAPI document: 5.0
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::NicApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'NicApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::NicApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of NicApi' do
-    it 'should create an instance of NicApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::NicApi)
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_delete
-  # Delete a Nic
-  # Deletes the specified NIC.
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Object]
-  describe 'datacenters_servers_nics_delete test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_find_by_id
-  # Retrieve a Nic
-  # Retrieves the attributes of a given NIC
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Nic]
-  describe 'datacenters_servers_nics_find_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_delete
-  # Delete a Firewall Rule
-  # Removes the specific Firewall Rule
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param firewallrule_id The unique ID of the Firewall Rule
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Object]
-  describe 'datacenters_servers_nics_firewallrules_delete test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_find_by_id
-  # Retrieve a Firewall Rule
-  # Retrieves the attributes of a given Firewall Rule.
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param firewallrule_id The unique ID of the Firewall Rule
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [FirewallRule]
-  describe 'datacenters_servers_nics_firewallrules_find_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_get
-  # List Firewall Rules 
-  # Retrieves a list of firewall rules associated with a particular NIC
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @option opts [Integer] :offset the first element (of the total list of elements) to include in the response (use together with <code>limit</code> for pagination)
-  # @option opts [Integer] :limit the maximum number of elements to return (use together with <code>offset</code> for pagination)
-  # @return [FirewallRules]
-  describe 'datacenters_servers_nics_firewallrules_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_patch
-  # Partially modify a Firewall Rule
-  # You can use update attributes of a resource
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param firewallrule_id The unique ID of the Firewall Rule
-  # @param firewallrule Modified Firewall Rule
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [FirewallRule]
-  describe 'datacenters_servers_nics_firewallrules_patch test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_post
-  # Create a Firewall Rule
-  # This will add a Firewall Rule to the NIC
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the server
-  # @param nic_id The unique ID of the NIC
-  # @param firewallrule Firewall Rule to be created
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [FirewallRule]
-  describe 'datacenters_servers_nics_firewallrules_post test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_put
-  # Modify a Firewall Rule
-  # You can use update attributes of a resource
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param firewallrule_id The unique ID of the Firewall Rule
-  # @param firewallrule Modified Firewall Rule
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [FirewallRule]
-  describe 'datacenters_servers_nics_firewallrules_put test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_get
-  # List Nics 
-  # Retrieves a list of NICs.
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @option opts [Integer] :offset the first element (of the total list of elements) to include in the response (use together with <code>limit</code> for pagination)
-  # @option opts [Integer] :limit the maximum number of elements to return (use together with <code>offset</code> for pagination)
-  # @return [Nics]
-  describe 'datacenters_servers_nics_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_patch
-  # Partially modify a Nic
-  # You can use update attributes of a Nic
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param nic Modified properties of Nic
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Nic]
-  describe 'datacenters_servers_nics_patch test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_post
-  # Create a Nic
-  # Adds a NIC to the target server. Combine count of Nics and volumes attached to the server should not exceed size 24.
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic Nic to be created
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Nic]
-  describe 'datacenters_servers_nics_post test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_put
-  # Modify a Nic
-  # You can use update attributes of a Nic
-  # @param datacenter_id The unique ID of the datacenter
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param nic Modified Nic
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Nic]
-  describe 'datacenters_servers_nics_put test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/private_cross_connect_api_spec.rb

@@ -1,110 +0,0 @@
-=begin
-#CLOUD API
-
-#An enterprise-grade Infrastructure is provided as a Service (IaaS) solution that can be managed through a browser-based \"Data Center Designer\" (DCD) tool or via an easy to use API.   The API allows you to perform a variety of management tasks such as spinning up additional servers, adding volumes, adjusting networking, and so forth. It is designed to allow users to leverage the same power and flexibility found within the DCD visual tool. Both tools are consistent with their concepts and lend well to making the experience smooth and intuitive.
-
-The version of the OpenAPI document: 5.0
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::PrivateCrossConnectApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'PrivateCrossConnectApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::PrivateCrossConnectApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of PrivateCrossConnectApi' do
-    it 'should create an instance of PrivateCrossConnectApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::PrivateCrossConnectApi)
-    end
-  end
-
-  # unit tests for pccs_delete
-  # Delete a Private Cross-Connect
-  # Delete a private cross-connect if no datacenters are joined to the given PCC
-  # @param pcc_id The unique ID of the private cross-connect
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Object]
-  describe 'pccs_delete test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for pccs_find_by_id
-  # Retrieve a Private Cross-Connect
-  # You can retrieve a private cross-connect by using the resource's ID. This value can be found in the response body when a private cross-connect is created or when you GET a list of private cross-connects.
-  # @param pcc_id The unique ID of the private cross-connect
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [PrivateCrossConnect]
-  describe 'pccs_find_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for pccs_get
-  # List Private Cross-Connects 
-  # You can retrieve a complete list of private cross-connects provisioned under your account
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [PrivateCrossConnects]
-  describe 'pccs_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for pccs_patch
-  # Partially modify a private cross-connect
-  # You can use update private cross-connect to re-name or update its description
-  # @param pcc_id The unique ID of the private cross-connect
-  # @param pcc Modified properties of private cross-connect
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [PrivateCrossConnect]
-  describe 'pccs_patch test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for pccs_post
-  # Create a Private Cross-Connect
-  # You can use this POST method to create a private cross-connect
-  # @param pcc Private Cross-Connect to be created
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [PrivateCrossConnect]
-  describe 'pccs_post test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end

data/spec/api/request_api_spec.rb

@@ -1,92 +0,0 @@
-=begin
-#CLOUD API
-
-#An enterprise-grade Infrastructure is provided as a Service (IaaS) solution that can be managed through a browser-based \"Data Center Designer\" (DCD) tool or via an easy to use API.   The API allows you to perform a variety of management tasks such as spinning up additional servers, adding volumes, adjusting networking, and so forth. It is designed to allow users to leverage the same power and flexibility found within the DCD visual tool. Both tools are consistent with their concepts and lend well to making the experience smooth and intuitive.
-
-The version of the OpenAPI document: 5.0
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::RequestApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'RequestApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::RequestApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of RequestApi' do
-    it 'should create an instance of RequestApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::RequestApi)
-    end
-  end
-
-  # unit tests for requests_find_by_id
-  # Retrieve a Request
-  # Retrieves the attributes of a given request.
-  # @param request_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Request]
-  describe 'requests_find_by_id test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for requests_get
-  # List Requests
-  # Retrieve a list of API requests.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @option opts [String] :filter_status Request filter to fetch all requests based on a particular status [QUEUED, RUNNING, DONE, FAILED]. It doesn't depend on depth query parameter
-  # @option opts [String] :filter_created_after Request filter to fetch all requests created after the specified date. It doesn't depend on depth query parameter. Date format e.g. 2021-01-01+00:00:00
-  # @option opts [String] :filter_created_before Request filter to fetch all requests created before the specified date. It doesn't depend on depth query parameter. Date format e.g. 2021-01-01+00:00:00
-  # @option opts [String] :filter_created_date Response filter to select and display only the requests that contains the specified createdDate. The value is case insensitive and it  depends on depth query parameter that should have a value greater than 0. Date format e.g. 2020-11-16T17:42:59Z
-  # @option opts [String] :filter_created_by Response filter to select and display only the requests that contains the specified createdBy. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [String] :filter_etag Response filter to select and display only the requests that contains the specified etag. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [String] :filter_request_status Response filter to select and display only the requests that contains the specified requestStatus. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [String] :filter_method Response filter to select and display only the requests that contains the specified method. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [String] :filter_headers Response filter to select and display only the requests that contains the specified headers. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [String] :filter_body Response filter to select and display only the requests that contains the specified body. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [String] :filter_url Response filter to select and display only the requests that contains the specified url. The value is case insensitive and it depends on depth query parameter that should have a value greater than 0. 
-  # @option opts [Integer] :offset the first element (of the total list of elements) to include in the response (use together with <code>limit</code> for pagination)
-  # @option opts [Integer] :limit the maximum number of elements to return (use together with <code>offset</code> for pagination)
-  # @return [Requests]
-  describe 'requests_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-  # unit tests for requests_status_get
-  # Retrieve Request Status
-  # Retrieves the status of a given request.
-  # @param request_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [RequestStatus]
-  describe 'requests_status_get test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end