ionoscloud 6.0.0.beta.4 → 6.0.0

data/spec/api/data_centers_api_spec.rb

@@ -1,128 +0,0 @@
-=begin
-#CLOUD API
-
-#IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool.    Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
-
-The version of the OpenAPI document: 6.0-SDK.3
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::DataCentersApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'DataCentersApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::DataCentersApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of DataCentersApi' do
-    it 'should create an instance of DataCentersApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::DataCentersApi)
-    end
-  end
-
-  # unit tests for datacenters_delete
-  # Delete data centers
-  # Remove the specified data center and all the elements it contains. This is method is destructive and should be used carefully.
-  # @param datacenter_id The unique ID of the data center.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to be executed.
-  # @return [nil]
-  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 data centers
-  # Retrieve data centers by resource ID. This value is in the response body when the data center is created, and in the list of the data centers, returned by GET.
-  # @param datacenter_id The unique ID of the data center.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 your data centers
-  # List the data centers for your account. Default limit is the first 100 items; use pagination query parameters for listing more items.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to be executed.
-  # @option opts [Integer] :offset The first element (from the complete list of the elements) to include in the response (use together with limit for pagination).
-  # @option opts [Integer] :limit The maximum number of elements to return (use together with offset 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 data centers
-  # Update data centers, rename them, or change their descriptions.
-  # @param datacenter_id The unique ID of the data center.
-  # @param datacenter The modified properties of the data center.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 data centers
-  # Create new data centers, and data centers that already contain elements, such as servers and storage volumes, with this POST method.  Virtual data centers are the foundation of the platform; they act as logical containers for all other objects you create, such as servers and storage volumes. You can provision as many data centers as needed. Data centers have their own private networks and are logically segmented from each other to create isolation.
-  # @param datacenter The data center to be created.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 data centers
-  # Update data centers, rename them, or change their descriptions.
-  # @param datacenter_id The unique ID of the data center.
-  # @param datacenter The modified data center.
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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/firewall_rules_api_spec.rb

@@ -1,146 +0,0 @@
-=begin
-#CLOUD API
-
-#IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool.    Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
-
-The version of the OpenAPI document: 6.0-SDK.3
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::FirewallRulesApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'FirewallRulesApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::FirewallRulesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of FirewallRulesApi' do
-    it 'should create an instance of FirewallRulesApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::FirewallRulesApi)
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_firewallrules_delete
-  # Delete a Firewall Rule
-  # Removes the specified firewall rule.
-  # @param datacenter_id The unique ID of the data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to be executed.
-  # @return [nil]
-  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 data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 network interface.
-  # @param datacenter_id The unique ID of the data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to be executed.
-  # @option opts [Integer] :offset The first element (from the complete list of the elements) to include in the response (use together with limit for pagination).
-  # @option opts [Integer] :limit The maximum number of elements to return (use together with offset 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 data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 network interface.
-  # @param datacenter_id The unique ID of the data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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
-
-end

data/spec/api/flow_logs_api_spec.rb

@@ -1,140 +0,0 @@
-=begin
-#CLOUD API
-
-#IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool.    Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
-
-The version of the OpenAPI document: 6.0-SDK.3
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::FlowLogsApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'FlowLogsApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::FlowLogsApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of FlowLogsApi' do
-    it 'should create an instance of FlowLogsApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::FlowLogsApi)
-    end
-  end
-
-  # unit tests for datacenters_servers_nics_flowlogs_delete
-  # Delete a Flow Log
-  # Removes the specified Flow Log.
-  # @param datacenter_id The unique ID of the data center.
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param flowlog_id The unique ID of the Flow Log
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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
-  # @return [nil]
-  describe 'datacenters_servers_nics_flowlogs_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_flowlogs_find_by_id
-  # Retrieve a Flow Log
-  # Retrieves the attributes of a given Flow Log.
-  # @param datacenter_id The unique ID of the data center.
-  # @param server_id The unique ID of the Server
-  # @param nic_id The unique ID of the NIC
-  # @param flowlog_id The unique ID of the Flow Log
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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
-  # @return [FlowLog]
-  describe 'datacenters_servers_nics_flowlogs_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_flowlogs_get
-  # List Flow Logs
-  # Retrieves a list of Flow Logs associated with a particular network interface.
-  # @param datacenter_id The unique ID of the data center.
-  # @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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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] :offset The first element (from the complete list of the elements) to include in the response (use together with limit for pagination).
-  # @option opts [Integer] :limit The maximum number of elements to return (use together with offset for pagination).
-  # @return [FlowLogs]
-  describe 'datacenters_servers_nics_flowlogs_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_flowlogs_patch
-  # Partially update a Flow Log
-  # This will partially update a Flow Log record.
-  # @param datacenter_id The unique ID of the data center.
-  # @param server_id The unique ID of the server
-  # @param nic_id The unique ID of the NIC
-  # @param flowlog_id The unique ID of the Flow Log
-  # @param flowlog Modified Flow Log
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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
-  # @return [FlowLog]
-  describe 'datacenters_servers_nics_flowlogs_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_flowlogs_post
-  # Create a Flow Log
-  # This will add a Flow Log to the network interface.
-  # @param datacenter_id The unique ID of the data center.
-  # @param server_id The unique ID of the server
-  # @param nic_id The unique ID of the NIC
-  # @param flowlog Flow Log to be created
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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
-  # @return [FlowLog]
-  describe 'datacenters_servers_nics_flowlogs_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_flowlogs_put
-  # Modify a Flow Log
-  # This will update a Flow Log record.
-  # @param datacenter_id The unique ID of the data center.
-  # @param server_id The unique ID of the server
-  # @param nic_id The unique ID of the NIC
-  # @param flowlog_id The unique ID of the Flow Log
-  # @param flowlog Modified Flow Log
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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
-  # @return [FlowLog]
-  describe 'datacenters_servers_nics_flowlogs_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/images_api_spec.rb

@@ -1,111 +0,0 @@
-=begin
-#CLOUD API
-
-#IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool.    Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
-
-The version of the OpenAPI document: 6.0-SDK.3
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::ImagesApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'ImagesApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::ImagesApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of ImagesApi' do
-    it 'should create an instance of ImagesApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::ImagesApi)
-    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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to be executed.
-  # @return [nil]
-  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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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 the response is pretty-printed (with indentations and new lines).
-  # @option opts [Integer] :depth Controls the detail depth of the response objects.  GET /datacenters/[ID]  - depth=0: Only direct properties are included; children (servers and other elements) 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 with multiple contracts must provide the contract number, against which all API requests are to 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