ionoscloud 5.1.1 → 6.0.0.beta.4

data/spec/api/user_s3_keys_api_spec.rb

@@ -0,0 +1,128 @@
+=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::UserS3KeysApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'UserS3KeysApi' do
+  before do
+    # run before each test
+    @api_instance = Ionoscloud::UserS3KeysApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of UserS3KeysApi' do
+    it 'should create an instance of UserS3KeysApi' do
+      expect(@api_instance).to be_instance_of(Ionoscloud::UserS3KeysApi)
+    end
+  end
+
+  # unit tests for um_users_s3keys_delete
+  # Delete an S3 Key
+  # Delete an S3 key.
+  # @param user_id The unique ID of the user
+  # @param key_id The unique access key ID of the S3 key
+  # @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 'um_users_s3keys_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 um_users_s3keys_find_by_key_id
+  # Retrieve given S3 Key belonging to the given User
+  # You can retrieve S3 key belonging to the given User. This user Id can be found in the response body when a user is created or when you GET a list of users. The key Id can be found in the response body when a S3 key is created or when you GET a list of all S3 keys of a user
+  # @param user_id The unique ID of the user
+  # @param key_id The unique access key ID of the S3 key
+  # @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 [S3Key]
+  describe 'um_users_s3keys_find_by_key_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 um_users_s3keys_get
+  # Retrieve a User's S3 keys
+  # You can retrieve S3 keys owned by a user by using the users ID. This user Id can be found in the response body when a user is created or when you GET a list of users.
+  # @param user_id The unique ID of the user
+  # @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 [S3Keys]
+  describe 'um_users_s3keys_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 um_users_s3keys_post
+  # Create a S3 Key for the given User
+  # Creates a S3 key for the given user. This user Id can be found in the response body when a user is created or when you GET a list of users. Maximum of 5 keys can be generated for a given user
+  # @param user_id The unique ID of the user
+  # @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 [S3Key]
+  describe 'um_users_s3keys_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 um_users_s3keys_put
+  # Modify a S3 key having the given key id
+  # You can enable or disable a given S3 key.
+  # @param user_id 
+  # @param key_id The unique access key ID of the S3 key
+  # @param s3_key Modified S3 key
+  # @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 [S3Key]
+  describe 'um_users_s3keys_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 um_users_s3ssourl_get
+  # Retrieve S3 object storage single signon URL for the given user
+  # You can retrieve S3 object storage single signon URL for the given user. This user Id can be found in the response body when a user is created or when you GET a list of users.
+  # @param user_id The unique ID of the user
+  # @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] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
+  # @return [S3ObjectStorageSSO]
+  describe 'um_users_s3ssourl_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/volumes_api_spec.rb

@@ -0,0 +1,171 @@
+=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::VolumesApi
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe 'VolumesApi' do
+  before do
+    # run before each test
+    @api_instance = Ionoscloud::VolumesApi.new
+  end
+
+  after do
+    # run after each test
+  end
+
+  describe 'test an instance of VolumesApi' do
+    it 'should create an instance of VolumesApi' do
+      expect(@api_instance).to be_instance_of(Ionoscloud::VolumesApi)
+    end
+  end
+
+  # unit tests for datacenters_volumes_create_snapshot_post
+  # Create Volume Snapshot
+  # Creates a snapshot of a volume within the datacenter. You can use a snapshot to create a new storage volume or to restore a storage volume.
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume_id The unique ID of the Volume
+  # @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 [String] :name The name of the snapshot
+  # @option opts [String] :description The description of the snapshot
+  # @option opts [Boolean] :sec_auth_protection Flag representing if extra protection is enabled on snapshot e.g. Two Factor protection etc.
+  # @option opts [String] :licence_type The OS type of this Snapshot
+  # @return [Snapshot]
+  describe 'datacenters_volumes_create_snapshot_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_volumes_delete
+  # Delete a Volume
+  # Deletes the specified volume. This will result in the volume being removed from your datacenter. Use this with caution.
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume_id The unique ID of the Volume
+  # @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_volumes_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_volumes_find_by_id
+  # Retrieve a Volume
+  # Retrieves the attributes of a given Volume
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume_id The unique ID of the Volume
+  # @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 [Volume]
+  describe 'datacenters_volumes_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_volumes_get
+  # List Volumes
+  # Retrieves a list of Volumes.
+  # @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.
+  # @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 [Volumes]
+  describe 'datacenters_volumes_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_volumes_patch
+  # Partially modify a Volume
+  # You can use update attributes of a volume.
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume_id The unique ID of the Volume
+  # @param volume Modified properties of Volume
+  # @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 [Volume]
+  describe 'datacenters_volumes_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_volumes_post
+  # Create a Volume
+  # Creates a volume within the datacenter. This will not attach the volume to a server. Please see the Servers section for details on how to attach storage volumes
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume Volume 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 [Volume]
+  describe 'datacenters_volumes_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_volumes_put
+  # Modify a Volume
+  # You can use update attributes of a Volume
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume_id The unique ID of the Volume
+  # @param volume Modified Volume
+  # @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 [Volume]
+  describe 'datacenters_volumes_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_volumes_restore_snapshot_post
+  # Restore Volume Snapshot
+  # This will restore a snapshot onto a volume. A snapshot is created as just another image that can be used to create subsequent volumes if you want or to restore an existing volume.
+  # @param datacenter_id The unique ID of the data center.
+  # @param volume_id The unique ID of the Volume
+  # @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 [String] :snapshot_id This is the ID of the snapshot
+  # @return [nil]
+  describe 'datacenters_volumes_restore_snapshot_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_client_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/configuration_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT
@@ -18,7 +18,7 @@ describe Ionoscloud::Configuration do
   before(:each) do
     # uncomment below to setup host and base_path
     # require 'URI'
-    # uri = URI.parse("https://api.ionos.com/cloudapi/v5")
+    # uri = URI.parse("https://api.ionos.com/cloudapi/v6")
     # Ionoscloud.configure do |c|
     #   c.host = uri.host
     #   c.base_path = uri.path
@@ -28,14 +28,14 @@ describe Ionoscloud::Configuration do
   describe '#base_url' do
     it 'should have the default value' do
       # uncomment below to test default value of the base path
-      # expect(config.base_url).to eq("https://api.ionos.com/cloudapi/v5")
+      # expect(config.base_url).to eq("https://api.ionos.com/cloudapi/v6")
     end
 
     it 'should remove trailing slashes' do
       [nil, '', '/', '//'].each do |base_path|
         config.base_path = base_path
         # uncomment below to test trailing slashes
-        # expect(config.base_url).to eq("https://api.ionos.com/cloudapi/v5")
+        # expect(config.base_url).to eq("https://api.ionos.com/cloudapi/v6")
       end
     end
   end

data/spec/models/attached_volumes_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/backup_unit_properties_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/backup_unit_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/backup_unit_sso_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/backup_units_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/balanced_nics_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/cdroms_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/connectable_datacenter_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/contract_properties_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/contract_spec.rb

@@ -1,9 +1,9 @@
 =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.
+#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: 5.0
+The version of the OpenAPI document: 6.0-SDK.3
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.2.1-SNAPSHOT

data/spec/models/contracts_spec.rb

@@ -0,0 +1,52 @@
+=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'
+require 'date'
+
+# Unit tests for Ionoscloud::Contracts
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Ionoscloud::Contracts do
+  let(:instance) { Ionoscloud::Contracts.new }
+
+  describe 'test an instance of Contracts' do
+    it 'should create an instance of Contracts' do
+      expect(instance).to be_instance_of(Ionoscloud::Contracts)
+    end
+  end
+  describe 'test attribute "id"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "type"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "href"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "items"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end

data/spec/models/cpu_architecture_properties_spec.rb

@@ -0,0 +1,52 @@
+=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'
+require 'date'
+
+# Unit tests for Ionoscloud::CpuArchitectureProperties
+# Automatically generated by openapi-generator (https://openapi-generator.tech)
+# Please update as you see appropriate
+describe Ionoscloud::CpuArchitectureProperties do
+  let(:instance) { Ionoscloud::CpuArchitectureProperties.new }
+
+  describe 'test an instance of CpuArchitectureProperties' do
+    it 'should create an instance of CpuArchitectureProperties' do
+      expect(instance).to be_instance_of(Ionoscloud::CpuArchitectureProperties)
+    end
+  end
+  describe 'test attribute "cpu_family"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "max_cores"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "max_ram"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+  describe 'test attribute "vendor"' do
+    it 'should work' do
+      # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
+    end
+  end
+
+end