ionoscloud 5.1.1 → 5.1.2

data/spec/api/user_management_api_spec.rb

@@ -1,497 +0,0 @@
-=begin
-#CLOUD API
-
-#An enterprise-grade Infrastructure is provided as a Service (IaaS) solution that can be managed through a browser-based \"Data Center Designer\" (DCD) tool or via an easy to use API.   The API allows you to perform a variety of management tasks such as spinning up additional servers, adding volumes, adjusting networking, and so forth. It is designed to allow users to leverage the same power and flexibility found within the DCD visual tool. Both tools are consistent with their concepts and lend well to making the experience smooth and intuitive.
-
-The version of the OpenAPI document: 5.0
-
-Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 5.2.1-SNAPSHOT
-
-=end
-
-require 'spec_helper'
-require 'json'
-
-# Unit tests for Ionoscloud::UserManagementApi
-# Automatically generated by openapi-generator (https://openapi-generator.tech)
-# Please update as you see appropriate
-describe 'UserManagementApi' do
-  before do
-    # run before each test
-    @api_instance = Ionoscloud::UserManagementApi.new
-  end
-
-  after do
-    # run after each test
-  end
-
-  describe 'test an instance of UserManagementApi' do
-    it 'should create an instance of UserManagementApi' do
-      expect(@api_instance).to be_instance_of(Ionoscloud::UserManagementApi)
-    end
-  end
-
-  # unit tests for um_groups_delete
-  # Delete a Group
-  # Delete a group
-  # @param group_id The unique ID of the group
-  # @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_groups_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_groups_find_by_id
-  # Retrieve a Group
-  # You can retrieve a group by using the group ID. This value can be found in the response body when a group is created or when you GET a list of groups.
-  # @param group_id The unique ID of the group
-  # @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 [Group]
-  describe 'um_groups_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 um_groups_get
-  # List All Groups.
-  # You can retrieve a complete list of all groups that you have access to
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Groups]
-  describe 'um_groups_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_groups_post
-  # Create a Group
-  # You can use this POST method to create a group
-  # @param group Group to be created
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Group]
-  describe 'um_groups_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_groups_put
-  # Modify a group
-  # You can use this method to update properties of the group.
-  # @param group_id The unique ID of the group
-  # @param group Modified properties of the Group
-  # @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 [Group]
-  describe 'um_groups_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_groups_resources_get
-  # Retrieve resources assigned to a group
-  # @param group_id The unique ID of the group
-  # @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 [ResourceGroups]
-  describe 'um_groups_resources_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_groups_shares_delete
-  # Remove a resource from a group
-  # This will remove a resource from a group
-  # @param group_id 
-  # @param resource_id 
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [Object]
-  describe 'um_groups_shares_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_groups_shares_find_by_resource_id
-  # Retrieve a group share
-  # This will retrieve the properties of a group share.
-  # @param group_id 
-  # @param resource_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 [GroupShare]
-  describe 'um_groups_shares_find_by_resource_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_groups_shares_get
-  # List Group Shares 
-  # You can retrieve a list of all resources along with their permissions of the group
-  # @param group_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 [GroupShares]
-  describe 'um_groups_shares_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_groups_shares_post
-  # Add a resource to a group
-  # This will add a resource to the group. 
-  # @param group_id 
-  # @param resource_id 
-  # @param resource Resource to be added
-  # @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 [GroupShare]
-  describe 'um_groups_shares_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_groups_shares_put
-  # Modify resource permissions of a group
-  # You can use update resource permissions of a group. If empty body will be provided, no updates will happen, instead you will be returned the current permissions of resource in a group. In this case response code will be 200
-  # @param group_id 
-  # @param resource_id 
-  # @param resource Modified Resource
-  # @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 [GroupShare]
-  describe 'um_groups_shares_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_groups_users_delete
-  # 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]
-  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
-    end
-  end
-
-  # unit tests for um_groups_users_get
-  # List Group Members 
-  # You can retrieve a list of users who are members of the group
-  # @param group_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 [GroupMembers]
-  describe 'um_groups_users_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_groups_users_post
-  # Add a user to a group
-  # This will attach a pre-existing user to a group. 
-  # @param group_id 
-  # @param user User to be added
-  # @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 [User]
-  describe 'um_groups_users_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_resources_find_by_type
-  # Retrieve a list of Resources by type.
-  # You can retrieve a list of resources by using the type. Allowed values are { datacenter, snapshot, image, ipblock, pcc, backupunit, k8s }. This value of resource type also be found in the response body when you GET a list of all resources.
-  # @param resource_type The resource Type
-  # @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 [Resources]
-  describe 'um_resources_find_by_type 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_resources_find_by_type_and_id
-  # Retrieve a Resource by type.
-  # You can retrieve a resource by using the type and its uuid. Allowed values for types are { datacenter, snapshot, image, ipblock, pcc, backupunit, k8s }. The value of resource type can also be found in the response body when you GET a list of all resources.
-  # @param resource_type The resource Type
-  # @param resource_id The resource Uuid
-  # @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 [Resource]
-  describe 'um_resources_find_by_type_and_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_resources_get
-  # List All Resources.
-  # 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
-  # @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 [Resources]
-  describe 'um_resources_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_delete
-  # Delete a User
-  # Delete a 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 [Object]
-  describe 'um_users_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_find_by_id
-  # Retrieve a User
-  # You can retrieve user details by using the users ID. This value 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 [User]
-  describe 'um_users_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 um_users_get
-  # List all Users 
-  # You can retrieve a complete list of users under your account
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @option opts [Integer] :offset the first element (of the total list of elements) to include in the response (use together with <code>limit</code> for pagination)
-  # @option opts [Integer] :limit the maximum number of elements to return (use together with <code>offset</code> for pagination)
-  # @return [Users]
-  describe 'um_users_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_groups_get
-  # Retrieve a User's group resources
-  # You can retrieve group resources of user by using the users ID. This value 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 [ResourceGroups]
-  describe 'um_users_groups_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_owns_get
-  # Retrieve a User's own resources
-  # You can retrieve resources owned by using the users ID. This value 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 [ResourcesUsers]
-  describe 'um_users_owns_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_post
-  # Create a user
-  # You can use this POST method to create a user
-  # @param user User to be created
-  # @param [Hash] opts the optional parameters
-  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
-  # @option opts [Integer] :depth Controls the details depth of response objects.  Eg. GET /datacenters/[ID]  - depth=0: only direct properties are included. Children (servers etc.) are not included  - depth=1: direct properties and children references are included  - depth=2: direct properties and children properties are included  - depth=3: direct properties and children properties and children's children are included  - depth=... and so on
-  # @option opts [Integer] :x_contract_number Users having more than 1 contract need to provide contract number, against which all API requests should be executed
-  # @return [User]
-  describe 'um_users_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_put
-  # Modify a user
-  # You can use update attributes of a User
-  # @param user_id 
-  # @param user Modified 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 [User]
-  describe 'um_users_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_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