ionoscloud 5.1.1 → 6.0.0.beta.4

data/lib/test_driver.rb

@@ -1,104 +0,0 @@
-#!/usr/bin/env ruby
-
-$LOAD_PATH << '.'
-
-require 'json'
-require 'ionoscloud'
-
-config = Ionoscloud::Configuration.new
-
-config.username = ENV['IONOS_USERNAME']
-config.password = ENV['IONOS_PASSWORD']
-
-api_client = Ionoscloud::ApiClient.new(config)
-
-def underscore_string(str)
-  str.gsub(/::/, '/')
-     .gsub(/([A-Z]+)([A-Z][a-z])/, '\1_\2')
-     .gsub(/([a-z\d])([A-Z])/, '\1_\2')
-     .tr('-', '_')
-     .downcase
-end
-
-def get_class(operation)
-  Ionoscloud.constants.select do |c|
-    Ionoscloud.const_get(c).is_a? Class and Ionoscloud.const_get(c).name.end_with? 'Api'
-  end.each do |class_symbol|
-    class_name = class_symbol.to_s
-    methods = Ionoscloud.const_get(class_name).new.methods - Object.methods
-    return Ionoscloud.const_get(class_name) if methods.map(&:to_s).include? operation
-  end
-  nil
-end
-
-input = gets.chomp
-testing_data = JSON.parse(input.gsub('\"', '"'))
-
-operation = testing_data['operation']
-
-begin
-  if operation == 'waitForRequest'
-    request_id = testing_data['params'][0]['value'].scan(%r{/requests/(\b[0-9a-f]{8}\b-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-\b[0-9a-f]{12}\b)}).last.first
-    api_client.wait_for_completion(request_id)
-    puts JSON[{}]
-  else
-    method_name =  "#{underscore_string(operation)}_with_http_info"
-
-    cls = get_class method_name
-
-    special_params_names = %w[pretty depth XContractNumber contractNumber offset limit]
-
-    normal_params, special_params = testing_data['params'].partition do |el|
-      special_params_names.none? do |special_param_name|
-        special_param_name == el['name']
-      end
-    end
-
-    normal_params = normal_params.map { |el| el['value'] }
-
-    special_params = special_params.each_with_object({}) do |current, total|
-      total[current['name'].to_sym] = current['value']
-    end
-
-    response, status_code, headers = cls.new(api_client).public_send(
-      method_name.to_sym,
-      *normal_params,
-      special_params
-    )
-
-    response = response.to_hash unless response.nil?
-
-    headers = headers.transform_values do |value|
-      value.split(',', -1)
-    end
-
-    puts JSON[{
-      'result' => response,
-      'httpResponse' => {
-        'statusCode' => status_code,
-        'headers' => headers,
-        'body' => response
-      }
-    }]
-  end
-rescue Ionoscloud::ApiError => e
-  puts JSON[{
-    'result' => 'ApiException occured',
-    'httpResponse' => {
-      'statusCode' => e.code,
-      'headers' => e.response_headers,
-      'body' => JSON.parse(e.response_body)
-    },
-    'error' => JSON.parse(e.response_body)
-  }]
-rescue StandardError => e
-  puts JSON[{
-    'result' => 'GeneralException occured',
-    'httpResponse' => {
-      'statusCode' => nil,
-      'headers' => nil,
-      'body' => nil
-    },
-    'error' => e.inspect
-  }]
-end

data/spec/api/backup_unit_api_spec.rb

@@ -1,140 +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::BackupUnitApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'BackupUnitApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::BackupUnitApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of BackupUnitApi' do
-    it 'should create an instance of BackupUnitApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::BackupUnitApi)
-    end
-  end
-
-  # unit tests for backupunits_delete
-  # Delete a Backup Unit
-  # NOTE: Running through the deletion process will delete: - the backup plans inside the Backup Unit. - all backups associated with the Backup Unit. - the backup user and finally also the unit
-  # @param backupunit_id The unique ID of the backup Unit
-  # @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 'backupunits_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 backupunits_find_by_id
-  # Returns the specified backup Unit
-  # You can retrieve the details of an specific backup unit.
-  # @param backupunit_id The unique ID of the backup unit
-  # @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 [BackupUnit]
-  describe 'backupunits_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 backupunits_get
-  # List Backup Units 
-  # You can retrieve a complete list of backup Units that you have access to.
-  # @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 [BackupUnits]
-  describe 'backupunits_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 backupunits_patch
-  # Partially modify a Backup Unit
-  # You can use update a backup Unit properties
-  # @param backupunit_id The unique ID of the backup unit
-  # @param backup_unit_properties Modified backup Unit properties
-  # @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 [BackupUnit]
-  describe 'backupunits_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 backupunits_post
-  # Create a Backup Unit
-  # Create a Backup Unit. A Backup Unit is considered a resource like a virtual datacenter, IP Block, snapshot, etc. It shall be shareable via groups inside our User Management Feature 
-  # @param backup_unit Payload containing data to create a new Backup Unit
-  # @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 [BackupUnit]
-  describe 'backupunits_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 backupunits_put
-  # Modify a Backup Unit
-  # You can use update a backup Unit properties
-  # @param backupunit_id The unique ID of the backup unit
-  # @param backup_unit Modified backup Unit
-  # @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 [BackupUnit]
-  describe 'backupunits_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 backupunits_ssourl_get
-  # Returns a single signon URL for the specified backup Unit.
-  # Returns a single signon URL for the specified backup Unit.
-  # @param backupunit_id The unique UUID of the backup unit
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @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 [BackupUnitSSO]
-  describe 'backupunits_ssourl_get 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/contract_api_spec.rb

@@ -1,49 +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::ContractApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'ContractApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::ContractApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ContractApi' do
-    it 'should create an instance of ContractApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::ContractApi)
-    end
-  end
-
-  # unit tests for contracts_get
-  # Retrieve a Contract
-  # Retrieves the attributes of user's contract.
-  # @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 [Contract]
-  describe 'contracts_get 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/data_center_api_spec.rb

@@ -1,128 +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::DataCenterApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'DataCenterApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::DataCenterApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of DataCenterApi' do
-    it 'should create an instance of DataCenterApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::DataCenterApi)
-    end
-  end
-
-  # unit tests for datacenters_delete
-  # Delete a Data Center
-  # Will remove all objects within the datacenter and remove the datacenter object itself, too. This is a highly destructive method which should be used with caution
-  # @param datacenter_id The unique ID of the datacenter
-  # @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_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_find_by_id
-  # Retrieve a Data Center
-  # You can retrieve a data center by using the resource's ID. This value can be found in the response body when a datacenter is created or when you GET a list of datacenters.
-  # @param datacenter_id The unique ID of the datacenter
-  # @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 [Datacenter]
-  describe 'datacenters_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_get
-  # List Data Centers under your account
-  # You can retrieve a list of data centers provisioned under your account. Default list will contain first 100 items. For more items use pagination query parameters
-  # @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 [Datacenters]
-  describe 'datacenters_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_patch
-  # Partially modify a Data Center
-  # You can use update datacenter to re-name the datacenter or update its description
-  # @param datacenter_id The unique ID of the datacenter
-  # @param datacenter Modified properties of Data Center
-  # @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 [Datacenter]
-  describe 'datacenters_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_post
-  # Create a Data Center
-  # Virtual data centers are the foundation of the platform. They act as logical containers for all other objects you will be creating, e.g. servers. You can provision as many data centers as you want. Datacenters have their own private network and are logically segmented from each other to create isolation. You can use this POST method to create a simple datacenter or to create a datacenter with multiple objects under it such as servers and storage volumes.
-  # @param datacenter Datacenter 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 [Datacenter]
-  describe 'datacenters_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_put
-  # Modify a Data Center
-  # You can use update datacenter to re-name the datacenter or update its description
-  # @param datacenter_id The unique ID of the datacenter
-  # @param datacenter Modified Data Center
-  # @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 [Datacenter]
-  describe 'datacenters_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/image_api_spec.rb

@@ -1,111 +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::ImageApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'ImageApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::ImageApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ImageApi' do
-    it 'should create an instance of ImageApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::ImageApi)
-    end
-  end
-
-  # unit tests for images_delete
-  # Delete an Image
-  # Deletes the specified image. This operation is permitted on private image only.
-  # @param image_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 [Object]
-  describe 'images_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 images_find_by_id
-  # Retrieve an Image
-  # Retrieves the attributes of a given image.
-  # @param image_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 [Image]
-  describe 'images_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 images_get
-  # List Images 
-  # Retrieve a list of images within the datacenter
-  # @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 [Images]
-  describe 'images_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 images_patch
-  # Partially modify an Image
-  # You can use update attributes of a resource
-  # @param image_id 
-  # @param image Modified Image
-  # @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 [Image]
-  describe 'images_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 images_put
-  # Modify an Image
-  # You can use update attributes of a resource
-  # @param image_id 
-  # @param image Modified Image
-  # @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 [Image]
-  describe 'images_put test' do
-    it 'should work' do
-      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
-    end
-  end
-
-end