ionoscloud 5.0.0 → 6.0.0.beta.3

data/spec/api/user_management_api_spec.rb

@@ -3,7 +3,7 @@
 
 #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
+The version of the OpenAPI document: 6.0-SDK.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'UserManagementApi' do
   # @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]
+  # @return [nil]
   describe 'um_groups_delete test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -130,7 +130,7 @@ describe 'UserManagementApi' do
   # @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]
+  # @return [nil]
   describe 'um_groups_shares_delete test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -204,14 +204,14 @@ describe 'UserManagementApi' do
 
   # unit tests for um_groups_users_delete
   # Remove a user from a group
-  # This will remove a user from a group
+  # This will remove a user from a group.
   # @param group_id 
   # @param user_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]
+  # @return [nil]
   describe 'um_groups_users_delete test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -282,7 +282,7 @@ describe 'UserManagementApi' do
 
   # unit tests for um_resources_get
   # List All Resources.
-  # You can retrieve a complete list of all resources that you have access to
+  # You can retrieve a complete list of all resources 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
@@ -302,7 +302,7 @@ describe 'UserManagementApi' do
   # @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]
+  # @return [nil]
   describe 'um_users_delete test' do
     it 'should work' do
       # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -399,97 +399,4 @@ describe 'UserManagementApi' do
     end
   end
 
-  # unit tests for um_users_s3keys_delete
-  # Delete a S3 key
-  # Delete a 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 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 '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 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 [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 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 [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 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 [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 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 [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 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 [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/user_s3_keys_api_spec.rb

@@ -0,0 +1,128 @@
+=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: 6.0-SDK.1
+
+Generated by: https://openapi-generator.tech
+OpenAPI Generator version: 5.0.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 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 [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 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 [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 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 [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 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 [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 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 [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 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 [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/{volume_api_spec.rb → volumes_api_spec.rb}

@@ -3,7 +3,7 @@
 
 #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
+The version of the OpenAPI document: 6.0-SDK.1
 
 Generated by: https://openapi-generator.tech
 OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -13,22 +13,22 @@ OpenAPI Generator version: 5.0.1-SNAPSHOT
 require 'spec_helper'
 require 'json'
 
-# Unit tests for Ionoscloud::VolumeApi
+# Unit tests for Ionoscloud::VolumesApi
 # Automatically generated by openapi-generator (https://openapi-generator.tech)
 # Please update as you see appropriate
-describe 'VolumeApi' do
+describe 'VolumesApi' do
   before do
     # run before each test
-    @api_instance = Ionoscloud::VolumeApi.new
+    @api_instance = Ionoscloud::VolumesApi.new
   end
 
   after do
     # run after each test
   end
 
-  describe 'test an instance of VolumeApi' do
-    it 'should create an instance of VolumeApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::VolumeApi)
+  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
 
@@ -61,7 +61,7 @@ describe 'VolumeApi' do
   # @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]
+  # @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
@@ -85,15 +85,15 @@ describe 'VolumeApi' do
   end
 
   # unit tests for datacenters_volumes_get
-  # List Volumes 
+  # List Volumes
   # Retrieves a list of Volumes.
   # @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
-  # @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)
+  # @option opts [Integer] :offset the first element (of the total list of 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
@@ -103,7 +103,7 @@ describe 'VolumeApi' do
 
   # unit tests for datacenters_volumes_patch
   # Partially modify a Volume
-  # You can use update attributes of a Volume
+  # You can use update attributes of a volume.
   # @param datacenter_id The unique ID of the datacenter
   # @param volume_id The unique ID of the Volume
   # @param volume Modified properties of Volume
@@ -161,7 +161,7 @@ describe 'VolumeApi' do
   # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
   # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
   # @option opts [String] :snapshot_id This is the ID of the snapshot
-  # @return [Object]
+  # @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

data/spec/api_client_spec.rb

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

data/spec/configuration_spec.rb

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

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

data/spec/models/backup_unit_properties_spec.rb

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

data/spec/models/backup_unit_spec.rb

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

data/spec/models/backup_unit_sso_spec.rb

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