ionoscloud 6.0.0.beta.2 → 6.0.0.beta.3

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (415) hide show
  1. checksums.yaml +4 -4
  2. data/README.md +55 -0
  3. data/docs/BackupUnitsApi.md +6 -7
  4. data/docs/DataCentersApi.md +6 -7
  5. data/docs/FirewallRulesApi.md +6 -7
  6. data/docs/FlowLogsApi.md +6 -7
  7. data/docs/IPBlocksApi.md +6 -7
  8. data/docs/ImagesApi.md +6 -7
  9. data/docs/KubernetesApi.md +24 -28
  10. data/docs/LabelsApi.md +30 -35
  11. data/docs/LansApi.md +6 -7
  12. data/docs/LoadBalancersApi.md +12 -14
  13. data/docs/NATGatewaysApi.md +18 -21
  14. data/docs/NetworkInterfacesApi.md +6 -7
  15. data/docs/NetworkLoadBalancersApi.md +18 -21
  16. data/docs/PrivateCrossConnectsApi.md +6 -7
  17. data/docs/ServersApi.md +54 -63
  18. data/docs/SnapshotsApi.md +6 -7
  19. data/docs/UserManagementApi.md +24 -28
  20. data/docs/UserS3KeysApi.md +6 -7
  21. data/docs/VolumesApi.md +12 -14
  22. data/ionoscloud.gemspec +1 -1
  23. data/lib/ionoscloud.rb +1 -1
  24. data/lib/ionoscloud/api/_api.rb +1 -1
  25. data/lib/ionoscloud/api/backup_units_api.rb +6 -6
  26. data/lib/ionoscloud/api/contract_resources_api.rb +1 -1
  27. data/lib/ionoscloud/api/data_centers_api.rb +6 -6
  28. data/lib/ionoscloud/api/firewall_rules_api.rb +6 -6
  29. data/lib/ionoscloud/api/flow_logs_api.rb +6 -6
  30. data/lib/ionoscloud/api/images_api.rb +6 -6
  31. data/lib/ionoscloud/api/ip_blocks_api.rb +6 -6
  32. data/lib/ionoscloud/api/kubernetes_api.rb +21 -21
  33. data/lib/ionoscloud/api/labels_api.rb +26 -26
  34. data/lib/ionoscloud/api/lans_api.rb +6 -6
  35. data/lib/ionoscloud/api/load_balancers_api.rb +11 -11
  36. data/lib/ionoscloud/api/locations_api.rb +1 -1
  37. data/lib/ionoscloud/api/nat_gateways_api.rb +16 -16
  38. data/lib/ionoscloud/api/network_interfaces_api.rb +6 -6
  39. data/lib/ionoscloud/api/network_load_balancers_api.rb +16 -16
  40. data/lib/ionoscloud/api/private_cross_connects_api.rb +6 -6
  41. data/lib/ionoscloud/api/requests_api.rb +1 -1
  42. data/lib/ionoscloud/api/servers_api.rb +46 -46
  43. data/lib/ionoscloud/api/snapshots_api.rb +6 -6
  44. data/lib/ionoscloud/api/templates_api.rb +1 -1
  45. data/lib/ionoscloud/api/user_management_api.rb +21 -21
  46. data/lib/ionoscloud/api/user_s3_keys_api.rb +6 -6
  47. data/lib/ionoscloud/api/volumes_api.rb +11 -11
  48. data/lib/ionoscloud/api_client.rb +2 -2
  49. data/lib/ionoscloud/api_error.rb +1 -1
  50. data/lib/ionoscloud/configuration.rb +1 -1
  51. data/lib/ionoscloud/models/attached_volumes.rb +1 -1
  52. data/lib/ionoscloud/models/backup_unit.rb +1 -1
  53. data/lib/ionoscloud/models/backup_unit_properties.rb +1 -1
  54. data/lib/ionoscloud/models/backup_unit_sso.rb +1 -1
  55. data/lib/ionoscloud/models/backup_units.rb +3 -3
  56. data/lib/ionoscloud/models/balanced_nics.rb +1 -1
  57. data/lib/ionoscloud/models/cdroms.rb +1 -1
  58. data/lib/ionoscloud/models/connectable_datacenter.rb +1 -1
  59. data/lib/ionoscloud/models/contract.rb +1 -1
  60. data/lib/ionoscloud/models/contract_properties.rb +1 -1
  61. data/lib/ionoscloud/models/contracts.rb +1 -1
  62. data/lib/ionoscloud/models/cpu_architecture_properties.rb +1 -1
  63. data/lib/ionoscloud/models/data_center_entities.rb +1 -1
  64. data/lib/ionoscloud/models/datacenter.rb +1 -1
  65. data/lib/ionoscloud/models/datacenter_element_metadata.rb +1 -1
  66. data/lib/ionoscloud/models/datacenter_properties.rb +1 -1
  67. data/lib/ionoscloud/models/datacenters.rb +1 -1
  68. data/lib/ionoscloud/models/error.rb +1 -1
  69. data/lib/ionoscloud/models/error_message.rb +1 -1
  70. data/lib/ionoscloud/models/firewall_rule.rb +1 -1
  71. data/lib/ionoscloud/models/firewall_rules.rb +1 -1
  72. data/lib/ionoscloud/models/firewallrule_properties.rb +37 -22
  73. data/lib/ionoscloud/models/flow_log.rb +1 -1
  74. data/lib/ionoscloud/models/flow_log_properties.rb +1 -1
  75. data/lib/ionoscloud/models/flow_log_put.rb +1 -1
  76. data/lib/ionoscloud/models/flow_logs.rb +1 -1
  77. data/lib/ionoscloud/models/group.rb +1 -1
  78. data/lib/ionoscloud/models/group_entities.rb +1 -1
  79. data/lib/ionoscloud/models/group_members.rb +1 -1
  80. data/lib/ionoscloud/models/group_properties.rb +1 -1
  81. data/lib/ionoscloud/models/group_share.rb +1 -1
  82. data/lib/ionoscloud/models/group_share_properties.rb +1 -1
  83. data/lib/ionoscloud/models/group_shares.rb +1 -1
  84. data/lib/ionoscloud/models/group_users.rb +1 -1
  85. data/lib/ionoscloud/models/groups.rb +1 -1
  86. data/lib/ionoscloud/models/image.rb +1 -1
  87. data/lib/ionoscloud/models/image_properties.rb +1 -1
  88. data/lib/ionoscloud/models/images.rb +1 -1
  89. data/lib/ionoscloud/models/info.rb +1 -1
  90. data/lib/ionoscloud/models/ip_block.rb +1 -1
  91. data/lib/ionoscloud/models/ip_block_properties.rb +1 -1
  92. data/lib/ionoscloud/models/ip_blocks.rb +1 -1
  93. data/lib/ionoscloud/models/ip_consumer.rb +1 -1
  94. data/lib/ionoscloud/models/ip_failover.rb +1 -1
  95. data/lib/ionoscloud/models/kubernetes_auto_scaling.rb +1 -1
  96. data/lib/ionoscloud/models/kubernetes_cluster.rb +1 -1
  97. data/lib/ionoscloud/models/kubernetes_cluster_entities.rb +1 -1
  98. data/lib/ionoscloud/models/kubernetes_cluster_for_post.rb +1 -1
  99. data/lib/ionoscloud/models/kubernetes_cluster_for_put.rb +1 -1
  100. data/lib/ionoscloud/models/kubernetes_cluster_properties.rb +1 -1
  101. data/lib/ionoscloud/models/kubernetes_cluster_properties_for_post.rb +1 -1
  102. data/lib/ionoscloud/models/kubernetes_cluster_properties_for_put.rb +1 -1
  103. data/lib/ionoscloud/models/kubernetes_clusters.rb +1 -1
  104. data/lib/ionoscloud/models/kubernetes_maintenance_window.rb +1 -1
  105. data/lib/ionoscloud/models/kubernetes_node.rb +1 -1
  106. data/lib/ionoscloud/models/kubernetes_node_metadata.rb +1 -1
  107. data/lib/ionoscloud/models/kubernetes_node_pool.rb +1 -1
  108. data/lib/ionoscloud/models/kubernetes_node_pool_for_post.rb +1 -1
  109. data/lib/ionoscloud/models/kubernetes_node_pool_for_put.rb +1 -1
  110. data/lib/ionoscloud/models/kubernetes_node_pool_lan.rb +1 -1
  111. data/lib/ionoscloud/models/kubernetes_node_pool_lan_routes.rb +1 -1
  112. data/lib/ionoscloud/models/kubernetes_node_pool_properties.rb +1 -1
  113. data/lib/ionoscloud/models/kubernetes_node_pool_properties_for_post.rb +1 -1
  114. data/lib/ionoscloud/models/kubernetes_node_pool_properties_for_put.rb +1 -1
  115. data/lib/ionoscloud/models/kubernetes_node_pools.rb +1 -1
  116. data/lib/ionoscloud/models/kubernetes_node_properties.rb +1 -1
  117. data/lib/ionoscloud/models/kubernetes_nodes.rb +1 -1
  118. data/lib/ionoscloud/models/label.rb +1 -1
  119. data/lib/ionoscloud/models/label_properties.rb +1 -1
  120. data/lib/ionoscloud/models/label_resource.rb +1 -1
  121. data/lib/ionoscloud/models/label_resource_properties.rb +1 -1
  122. data/lib/ionoscloud/models/label_resources.rb +3 -3
  123. data/lib/ionoscloud/models/labels.rb +3 -3
  124. data/lib/ionoscloud/models/lan.rb +1 -1
  125. data/lib/ionoscloud/models/lan_entities.rb +1 -1
  126. data/lib/ionoscloud/models/lan_nics.rb +1 -1
  127. data/lib/ionoscloud/models/lan_post.rb +1 -1
  128. data/lib/ionoscloud/models/lan_properties.rb +1 -1
  129. data/lib/ionoscloud/models/lan_properties_post.rb +1 -1
  130. data/lib/ionoscloud/models/lans.rb +1 -1
  131. data/lib/ionoscloud/models/loadbalancer.rb +1 -1
  132. data/lib/ionoscloud/models/loadbalancer_entities.rb +1 -1
  133. data/lib/ionoscloud/models/loadbalancer_properties.rb +13 -30
  134. data/lib/ionoscloud/models/loadbalancers.rb +1 -1
  135. data/lib/ionoscloud/models/location.rb +1 -1
  136. data/lib/ionoscloud/models/location_properties.rb +1 -1
  137. data/lib/ionoscloud/models/locations.rb +1 -1
  138. data/lib/ionoscloud/models/nat_gateway.rb +1 -1
  139. data/lib/ionoscloud/models/nat_gateway_entities.rb +1 -1
  140. data/lib/ionoscloud/models/nat_gateway_lan_properties.rb +1 -1
  141. data/lib/ionoscloud/models/nat_gateway_properties.rb +1 -1
  142. data/lib/ionoscloud/models/nat_gateway_put.rb +1 -1
  143. data/lib/ionoscloud/models/nat_gateway_rule.rb +1 -1
  144. data/lib/ionoscloud/models/nat_gateway_rule_properties.rb +1 -1
  145. data/lib/ionoscloud/models/nat_gateway_rule_protocol.rb +1 -1
  146. data/lib/ionoscloud/models/nat_gateway_rule_put.rb +1 -1
  147. data/lib/ionoscloud/models/nat_gateway_rule_type.rb +1 -1
  148. data/lib/ionoscloud/models/nat_gateway_rules.rb +1 -1
  149. data/lib/ionoscloud/models/nat_gateways.rb +1 -1
  150. data/lib/ionoscloud/models/network_load_balancer.rb +1 -1
  151. data/lib/ionoscloud/models/network_load_balancer_entities.rb +1 -1
  152. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule.rb +1 -1
  153. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_health_check.rb +1 -1
  154. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_properties.rb +1 -1
  155. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_put.rb +1 -1
  156. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_target.rb +1 -1
  157. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_target_health_check.rb +1 -1
  158. data/lib/ionoscloud/models/network_load_balancer_forwarding_rules.rb +1 -1
  159. data/lib/ionoscloud/models/network_load_balancer_properties.rb +1 -1
  160. data/lib/ionoscloud/models/network_load_balancer_put.rb +1 -1
  161. data/lib/ionoscloud/models/network_load_balancers.rb +1 -1
  162. data/lib/ionoscloud/models/nic.rb +1 -1
  163. data/lib/ionoscloud/models/nic_entities.rb +1 -1
  164. data/lib/ionoscloud/models/nic_properties.rb +1 -1
  165. data/lib/ionoscloud/models/nic_put.rb +1 -1
  166. data/lib/ionoscloud/models/nics.rb +1 -1
  167. data/lib/ionoscloud/models/no_state_meta_data.rb +1 -1
  168. data/lib/ionoscloud/models/pagination_links.rb +1 -1
  169. data/lib/ionoscloud/models/peer.rb +1 -1
  170. data/lib/ionoscloud/models/private_cross_connect.rb +1 -1
  171. data/lib/ionoscloud/models/private_cross_connect_properties.rb +1 -1
  172. data/lib/ionoscloud/models/private_cross_connects.rb +1 -1
  173. data/lib/ionoscloud/models/remote_console_url.rb +1 -1
  174. data/lib/ionoscloud/models/request.rb +1 -1
  175. data/lib/ionoscloud/models/request_metadata.rb +1 -1
  176. data/lib/ionoscloud/models/request_properties.rb +1 -1
  177. data/lib/ionoscloud/models/request_status.rb +1 -1
  178. data/lib/ionoscloud/models/request_status_metadata.rb +1 -1
  179. data/lib/ionoscloud/models/request_target.rb +1 -1
  180. data/lib/ionoscloud/models/requests.rb +1 -1
  181. data/lib/ionoscloud/models/resource.rb +1 -1
  182. data/lib/ionoscloud/models/resource_entities.rb +1 -1
  183. data/lib/ionoscloud/models/resource_groups.rb +1 -1
  184. data/lib/ionoscloud/models/resource_limits.rb +1 -1
  185. data/lib/ionoscloud/models/resource_properties.rb +1 -1
  186. data/lib/ionoscloud/models/resource_reference.rb +1 -1
  187. data/lib/ionoscloud/models/resources.rb +1 -1
  188. data/lib/ionoscloud/models/resources_users.rb +1 -1
  189. data/lib/ionoscloud/models/s3_key.rb +1 -1
  190. data/lib/ionoscloud/models/s3_key_metadata.rb +1 -1
  191. data/lib/ionoscloud/models/s3_key_properties.rb +1 -1
  192. data/lib/ionoscloud/models/s3_keys.rb +1 -1
  193. data/lib/ionoscloud/models/s3_object_storage_sso.rb +1 -1
  194. data/lib/ionoscloud/models/server.rb +1 -1
  195. data/lib/ionoscloud/models/server_entities.rb +1 -1
  196. data/lib/ionoscloud/models/server_properties.rb +3 -3
  197. data/lib/ionoscloud/models/servers.rb +1 -1
  198. data/lib/ionoscloud/models/snapshot.rb +1 -1
  199. data/lib/ionoscloud/models/snapshot_properties.rb +1 -1
  200. data/lib/ionoscloud/models/snapshots.rb +1 -1
  201. data/lib/ionoscloud/models/target_port_range.rb +1 -1
  202. data/lib/ionoscloud/models/template.rb +1 -1
  203. data/lib/ionoscloud/models/template_properties.rb +1 -1
  204. data/lib/ionoscloud/models/templates.rb +1 -1
  205. data/lib/ionoscloud/models/token.rb +1 -1
  206. data/lib/ionoscloud/models/type.rb +1 -1
  207. data/lib/ionoscloud/models/user.rb +1 -1
  208. data/lib/ionoscloud/models/user_metadata.rb +1 -1
  209. data/lib/ionoscloud/models/user_post.rb +1 -1
  210. data/lib/ionoscloud/models/user_properties.rb +1 -1
  211. data/lib/ionoscloud/models/user_properties_post.rb +1 -1
  212. data/lib/ionoscloud/models/user_properties_put.rb +1 -1
  213. data/lib/ionoscloud/models/user_put.rb +1 -1
  214. data/lib/ionoscloud/models/users.rb +1 -1
  215. data/lib/ionoscloud/models/users_entities.rb +1 -1
  216. data/lib/ionoscloud/models/volume.rb +1 -1
  217. data/lib/ionoscloud/models/volume_properties.rb +1 -1
  218. data/lib/ionoscloud/models/volumes.rb +1 -1
  219. data/lib/ionoscloud/version.rb +2 -2
  220. data/spec/api/_api_spec.rb +1 -1
  221. data/spec/api/backup_units_api_spec.rb +2 -2
  222. data/spec/api/contract_resources_api_spec.rb +1 -1
  223. data/spec/api/data_centers_api_spec.rb +2 -2
  224. data/spec/api/firewall_rules_api_spec.rb +2 -2
  225. data/spec/api/flow_logs_api_spec.rb +2 -2
  226. data/spec/api/images_api_spec.rb +2 -2
  227. data/spec/api/ip_blocks_api_spec.rb +2 -2
  228. data/spec/api/kubernetes_api_spec.rb +5 -5
  229. data/spec/api/labels_api_spec.rb +6 -6
  230. data/spec/api/lans_api_spec.rb +2 -2
  231. data/spec/api/load_balancers_api_spec.rb +3 -3
  232. data/spec/api/locations_api_spec.rb +1 -1
  233. data/spec/api/nat_gateways_api_spec.rb +4 -4
  234. data/spec/api/network_interfaces_api_spec.rb +2 -2
  235. data/spec/api/network_load_balancers_api_spec.rb +4 -4
  236. data/spec/api/private_cross_connects_api_spec.rb +2 -2
  237. data/spec/api/requests_api_spec.rb +1 -1
  238. data/spec/api/servers_api_spec.rb +10 -10
  239. data/spec/api/snapshots_api_spec.rb +2 -2
  240. data/spec/api/templates_api_spec.rb +1 -1
  241. data/spec/api/user_management_api_spec.rb +5 -5
  242. data/spec/api/user_s3_keys_api_spec.rb +2 -2
  243. data/spec/api/volumes_api_spec.rb +3 -3
  244. data/spec/api_client_spec.rb +1 -1
  245. data/spec/configuration_spec.rb +1 -1
  246. data/spec/models/attached_volumes_spec.rb +1 -1
  247. data/spec/models/backup_unit_properties_spec.rb +1 -1
  248. data/spec/models/backup_unit_spec.rb +1 -1
  249. data/spec/models/backup_unit_sso_spec.rb +1 -1
  250. data/spec/models/backup_units_spec.rb +2 -2
  251. data/spec/models/balanced_nics_spec.rb +1 -1
  252. data/spec/models/cdroms_spec.rb +1 -1
  253. data/spec/models/connectable_datacenter_spec.rb +1 -1
  254. data/spec/models/contract_properties_spec.rb +1 -1
  255. data/spec/models/contract_spec.rb +1 -1
  256. data/spec/models/contracts_spec.rb +1 -1
  257. data/spec/models/cpu_architecture_properties_spec.rb +1 -1
  258. data/spec/models/data_center_entities_spec.rb +1 -1
  259. data/spec/models/datacenter_element_metadata_spec.rb +1 -1
  260. data/spec/models/datacenter_properties_spec.rb +1 -1
  261. data/spec/models/datacenter_spec.rb +1 -1
  262. data/spec/models/datacenters_spec.rb +1 -1
  263. data/spec/models/error_message_spec.rb +1 -1
  264. data/spec/models/error_spec.rb +1 -1
  265. data/spec/models/firewall_rule_spec.rb +1 -1
  266. data/spec/models/firewall_rules_spec.rb +1 -1
  267. data/spec/models/firewallrule_properties_spec.rb +1 -13
  268. data/spec/models/flow_log_properties_spec.rb +1 -1
  269. data/spec/models/flow_log_put_spec.rb +1 -1
  270. data/spec/models/flow_log_spec.rb +1 -1
  271. data/spec/models/flow_logs_spec.rb +1 -1
  272. data/spec/models/group_entities_spec.rb +1 -1
  273. data/spec/models/group_members_spec.rb +1 -1
  274. data/spec/models/group_properties_spec.rb +1 -1
  275. data/spec/models/group_share_properties_spec.rb +1 -1
  276. data/spec/models/group_share_spec.rb +1 -1
  277. data/spec/models/group_shares_spec.rb +1 -1
  278. data/spec/models/group_spec.rb +1 -1
  279. data/spec/models/group_users_spec.rb +1 -1
  280. data/spec/models/groups_spec.rb +1 -1
  281. data/spec/models/image_properties_spec.rb +1 -1
  282. data/spec/models/image_spec.rb +1 -1
  283. data/spec/models/images_spec.rb +1 -1
  284. data/spec/models/info_spec.rb +1 -1
  285. data/spec/models/ip_block_properties_spec.rb +1 -1
  286. data/spec/models/ip_block_spec.rb +1 -1
  287. data/spec/models/ip_blocks_spec.rb +1 -1
  288. data/spec/models/ip_consumer_spec.rb +1 -1
  289. data/spec/models/ip_failover_spec.rb +1 -1
  290. data/spec/models/kubernetes_auto_scaling_spec.rb +1 -1
  291. data/spec/models/kubernetes_cluster_entities_spec.rb +1 -1
  292. data/spec/models/kubernetes_cluster_for_post_spec.rb +1 -1
  293. data/spec/models/kubernetes_cluster_for_put_spec.rb +1 -1
  294. data/spec/models/kubernetes_cluster_properties_for_post_spec.rb +1 -1
  295. data/spec/models/kubernetes_cluster_properties_for_put_spec.rb +1 -1
  296. data/spec/models/kubernetes_cluster_properties_spec.rb +1 -1
  297. data/spec/models/kubernetes_cluster_spec.rb +1 -1
  298. data/spec/models/kubernetes_clusters_spec.rb +1 -1
  299. data/spec/models/kubernetes_maintenance_window_spec.rb +1 -1
  300. data/spec/models/kubernetes_node_metadata_spec.rb +1 -1
  301. data/spec/models/kubernetes_node_pool_for_post_spec.rb +1 -1
  302. data/spec/models/kubernetes_node_pool_for_put_spec.rb +1 -1
  303. data/spec/models/kubernetes_node_pool_lan_routes_spec.rb +1 -1
  304. data/spec/models/kubernetes_node_pool_lan_spec.rb +1 -1
  305. data/spec/models/kubernetes_node_pool_properties_for_post_spec.rb +1 -1
  306. data/spec/models/kubernetes_node_pool_properties_for_put_spec.rb +1 -1
  307. data/spec/models/kubernetes_node_pool_properties_spec.rb +1 -1
  308. data/spec/models/kubernetes_node_pool_spec.rb +1 -1
  309. data/spec/models/kubernetes_node_pools_spec.rb +1 -1
  310. data/spec/models/kubernetes_node_properties_spec.rb +1 -1
  311. data/spec/models/kubernetes_node_spec.rb +1 -1
  312. data/spec/models/kubernetes_nodes_spec.rb +1 -1
  313. data/spec/models/label_properties_spec.rb +1 -1
  314. data/spec/models/label_resource_properties_spec.rb +1 -1
  315. data/spec/models/label_resource_spec.rb +1 -1
  316. data/spec/models/label_resources_spec.rb +2 -2
  317. data/spec/models/label_spec.rb +1 -1
  318. data/spec/models/labels_spec.rb +2 -2
  319. data/spec/models/lan_entities_spec.rb +1 -1
  320. data/spec/models/lan_nics_spec.rb +1 -1
  321. data/spec/models/lan_post_spec.rb +1 -1
  322. data/spec/models/lan_properties_post_spec.rb +1 -1
  323. data/spec/models/lan_properties_spec.rb +1 -1
  324. data/spec/models/lan_spec.rb +1 -1
  325. data/spec/models/lans_spec.rb +1 -1
  326. data/spec/models/loadbalancer_entities_spec.rb +1 -1
  327. data/spec/models/loadbalancer_properties_spec.rb +1 -5
  328. data/spec/models/loadbalancer_spec.rb +1 -1
  329. data/spec/models/loadbalancers_spec.rb +1 -1
  330. data/spec/models/location_properties_spec.rb +1 -1
  331. data/spec/models/location_spec.rb +1 -1
  332. data/spec/models/locations_spec.rb +1 -1
  333. data/spec/models/nat_gateway_entities_spec.rb +1 -1
  334. data/spec/models/nat_gateway_lan_properties_spec.rb +1 -1
  335. data/spec/models/nat_gateway_properties_spec.rb +1 -1
  336. data/spec/models/nat_gateway_put_spec.rb +1 -1
  337. data/spec/models/nat_gateway_rule_properties_spec.rb +1 -1
  338. data/spec/models/nat_gateway_rule_protocol_spec.rb +1 -1
  339. data/spec/models/nat_gateway_rule_put_spec.rb +1 -1
  340. data/spec/models/nat_gateway_rule_spec.rb +1 -1
  341. data/spec/models/nat_gateway_rule_type_spec.rb +1 -1
  342. data/spec/models/nat_gateway_rules_spec.rb +1 -1
  343. data/spec/models/nat_gateway_spec.rb +1 -1
  344. data/spec/models/nat_gateways_spec.rb +1 -1
  345. data/spec/models/network_load_balancer_entities_spec.rb +1 -1
  346. data/spec/models/network_load_balancer_forwarding_rule_health_check_spec.rb +1 -1
  347. data/spec/models/network_load_balancer_forwarding_rule_properties_spec.rb +1 -1
  348. data/spec/models/network_load_balancer_forwarding_rule_put_spec.rb +1 -1
  349. data/spec/models/network_load_balancer_forwarding_rule_spec.rb +1 -1
  350. data/spec/models/network_load_balancer_forwarding_rule_target_health_check_spec.rb +1 -1
  351. data/spec/models/network_load_balancer_forwarding_rule_target_spec.rb +1 -1
  352. data/spec/models/network_load_balancer_forwarding_rules_spec.rb +1 -1
  353. data/spec/models/network_load_balancer_properties_spec.rb +1 -1
  354. data/spec/models/network_load_balancer_put_spec.rb +1 -1
  355. data/spec/models/network_load_balancer_spec.rb +1 -1
  356. data/spec/models/network_load_balancers_spec.rb +1 -1
  357. data/spec/models/nic_entities_spec.rb +1 -1
  358. data/spec/models/nic_properties_spec.rb +1 -1
  359. data/spec/models/nic_put_spec.rb +1 -1
  360. data/spec/models/nic_spec.rb +1 -1
  361. data/spec/models/nics_spec.rb +1 -1
  362. data/spec/models/no_state_meta_data_spec.rb +1 -1
  363. data/spec/models/pagination_links_spec.rb +1 -1
  364. data/spec/models/peer_spec.rb +1 -1
  365. data/spec/models/private_cross_connect_properties_spec.rb +1 -1
  366. data/spec/models/private_cross_connect_spec.rb +1 -1
  367. data/spec/models/private_cross_connects_spec.rb +1 -1
  368. data/spec/models/remote_console_url_spec.rb +1 -1
  369. data/spec/models/request_metadata_spec.rb +1 -1
  370. data/spec/models/request_properties_spec.rb +1 -1
  371. data/spec/models/request_spec.rb +1 -1
  372. data/spec/models/request_status_metadata_spec.rb +1 -1
  373. data/spec/models/request_status_spec.rb +1 -1
  374. data/spec/models/request_target_spec.rb +1 -1
  375. data/spec/models/requests_spec.rb +1 -1
  376. data/spec/models/resource_entities_spec.rb +1 -1
  377. data/spec/models/resource_groups_spec.rb +1 -1
  378. data/spec/models/resource_limits_spec.rb +1 -1
  379. data/spec/models/resource_properties_spec.rb +1 -1
  380. data/spec/models/resource_reference_spec.rb +1 -1
  381. data/spec/models/resource_spec.rb +1 -1
  382. data/spec/models/resources_spec.rb +1 -1
  383. data/spec/models/resources_users_spec.rb +1 -1
  384. data/spec/models/s3_key_metadata_spec.rb +1 -1
  385. data/spec/models/s3_key_properties_spec.rb +1 -1
  386. data/spec/models/s3_key_spec.rb +1 -1
  387. data/spec/models/s3_keys_spec.rb +1 -1
  388. data/spec/models/s3_object_storage_sso_spec.rb +1 -1
  389. data/spec/models/server_entities_spec.rb +1 -1
  390. data/spec/models/server_properties_spec.rb +2 -2
  391. data/spec/models/server_spec.rb +1 -1
  392. data/spec/models/servers_spec.rb +1 -1
  393. data/spec/models/snapshot_properties_spec.rb +1 -1
  394. data/spec/models/snapshot_spec.rb +1 -1
  395. data/spec/models/snapshots_spec.rb +1 -1
  396. data/spec/models/target_port_range_spec.rb +1 -1
  397. data/spec/models/template_properties_spec.rb +1 -1
  398. data/spec/models/template_spec.rb +1 -1
  399. data/spec/models/templates_spec.rb +1 -1
  400. data/spec/models/token_spec.rb +1 -1
  401. data/spec/models/type_spec.rb +1 -1
  402. data/spec/models/user_metadata_spec.rb +1 -1
  403. data/spec/models/user_post_spec.rb +1 -1
  404. data/spec/models/user_properties_post_spec.rb +1 -1
  405. data/spec/models/user_properties_put_spec.rb +1 -1
  406. data/spec/models/user_properties_spec.rb +1 -1
  407. data/spec/models/user_put_spec.rb +1 -1
  408. data/spec/models/user_spec.rb +1 -1
  409. data/spec/models/users_entities_spec.rb +1 -1
  410. data/spec/models/users_spec.rb +1 -1
  411. data/spec/models/volume_properties_spec.rb +1 -1
  412. data/spec/models/volume_spec.rb +1 -1
  413. data/spec/models/volumes_spec.rb +1 -1
  414. data/spec/spec_helper.rb +1 -1
  415. metadata +164 -163
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'BackupUnitsApi' do
40
40
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
41
41
  # @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
42
42
  # @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
43
- # @return [Object]
43
+ # @return [nil]
44
44
  describe 'backupunits_delete test' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'DataCentersApi' do
40
40
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
41
41
  # @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
42
42
  # @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
43
- # @return [Object]
43
+ # @return [nil]
44
44
  describe 'datacenters_delete test' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -43,7 +43,7 @@ describe 'FirewallRulesApi' do
43
43
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
44
44
  # @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
45
45
  # @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
46
- # @return [Object]
46
+ # @return [nil]
47
47
  describe 'datacenters_servers_nics_firewallrules_delete test' do
48
48
  it 'should work' do
49
49
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -42,7 +42,7 @@ describe 'FlowLogsApi' do
42
42
  # @param [Hash] opts the optional parameters
43
43
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
44
44
  # @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
45
- # @return [Object]
45
+ # @return [nil]
46
46
  describe 'datacenters_servers_nics_flowlogs_delete test' do
47
47
  it 'should work' do
48
48
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'ImagesApi' do
40
40
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
41
41
  # @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
42
42
  # @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
43
- # @return [Object]
43
+ # @return [nil]
44
44
  describe 'images_delete test' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'IPBlocksApi' do
40
40
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
41
41
  # @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
42
42
  # @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
43
- # @return [Object]
43
+ # @return [nil]
44
44
  describe 'ipblocks_delete test' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'KubernetesApi' do
40
40
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
41
41
  # @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
42
42
  # @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
43
- # @return [Object]
43
+ # @return [nil]
44
44
  describe 'k8s_delete test' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -100,7 +100,7 @@ describe 'KubernetesApi' do
100
100
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
101
101
  # @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
102
102
  # @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
103
- # @return [Object]
103
+ # @return [nil]
104
104
  describe 'k8s_nodepools_delete test' do
105
105
  it 'should work' do
106
106
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -148,7 +148,7 @@ describe 'KubernetesApi' do
148
148
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
149
149
  # @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
150
150
  # @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
151
- # @return [Object]
151
+ # @return [nil]
152
152
  describe 'k8s_nodepools_nodes_delete test' do
153
153
  it 'should work' do
154
154
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -198,7 +198,7 @@ describe 'KubernetesApi' do
198
198
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
199
199
  # @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
200
200
  # @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
201
- # @return [Object]
201
+ # @return [nil]
202
202
  describe 'k8s_nodepools_nodes_replace_post test' do
203
203
  it 'should work' do
204
204
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -41,7 +41,7 @@ describe 'LabelsApi' do
41
41
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
42
42
  # @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
43
43
  # @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
44
- # @return [Object]
44
+ # @return [nil]
45
45
  describe 'datacenters_labels_delete test' do
46
46
  it 'should work' do
47
47
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -124,7 +124,7 @@ describe 'LabelsApi' do
124
124
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
125
125
  # @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
126
126
  # @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
127
- # @return [Object]
127
+ # @return [nil]
128
128
  describe 'datacenters_servers_labels_delete test' do
129
129
  it 'should work' do
130
130
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -211,7 +211,7 @@ describe 'LabelsApi' do
211
211
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
212
212
  # @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
213
213
  # @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
214
- # @return [Object]
214
+ # @return [nil]
215
215
  describe 'datacenters_volumes_labels_delete test' do
216
216
  it 'should work' do
217
217
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -295,7 +295,7 @@ describe 'LabelsApi' do
295
295
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
296
296
  # @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
297
297
  # @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
298
- # @return [Object]
298
+ # @return [nil]
299
299
  describe 'ipblocks_labels_delete test' do
300
300
  it 'should work' do
301
301
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -404,7 +404,7 @@ describe 'LabelsApi' do
404
404
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
405
405
  # @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
406
406
  # @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
407
- # @return [Object]
407
+ # @return [nil]
408
408
  describe 'snapshots_labels_delete test' do
409
409
  it 'should work' do
410
410
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -41,7 +41,7 @@ describe 'LansApi' do
41
41
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
42
42
  # @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
43
43
  # @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
44
- # @return [Object]
44
+ # @return [nil]
45
45
  describe 'datacenters_lans_delete test' do
46
46
  it 'should work' do
47
47
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -42,7 +42,7 @@ describe 'LoadBalancersApi' do
42
42
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
43
43
  # @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
44
44
  # @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
45
- # @return [Object]
45
+ # @return [nil]
46
46
  describe 'datacenters_loadbalancers_balancednics_delete test' do
47
47
  it 'should work' do
48
48
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -112,7 +112,7 @@ describe 'LoadBalancersApi' do
112
112
  # @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
113
113
  # @option opts [Integer] :offset the first element (of the total list of elements) to include in the response (use together with limit for pagination)
114
114
  # @option opts [Integer] :limit the maximum number of elements to return (use together with offset for pagination)
115
- # @return [Object]
115
+ # @return [nil]
116
116
  describe 'datacenters_loadbalancers_delete test' do
117
117
  it 'should work' do
118
118
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -41,7 +41,7 @@ describe 'NATGatewaysApi' do
41
41
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
42
42
  # @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
43
43
  # @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
44
- # @return [Object]
44
+ # @return [nil]
45
45
  describe 'datacenters_natgateways_delete test' do
46
46
  it 'should work' do
47
47
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -73,7 +73,7 @@ describe 'NATGatewaysApi' do
73
73
  # @param [Hash] opts the optional parameters
74
74
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
75
75
  # @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
76
- # @return [Object]
76
+ # @return [nil]
77
77
  describe 'datacenters_natgateways_flowlogs_delete test' do
78
78
  it 'should work' do
79
79
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -240,7 +240,7 @@ describe 'NATGatewaysApi' do
240
240
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
241
241
  # @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
242
242
  # @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
243
- # @return [Object]
243
+ # @return [nil]
244
244
  describe 'datacenters_natgateways_rules_delete test' do
245
245
  it 'should work' do
246
246
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -42,7 +42,7 @@ describe 'NetworkInterfacesApi' do
42
42
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
43
43
  # @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
44
44
  # @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
45
- # @return [Object]
45
+ # @return [nil]
46
46
  describe 'datacenters_servers_nics_delete test' do
47
47
  it 'should work' do
48
48
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -41,7 +41,7 @@ describe 'NetworkLoadBalancersApi' do
41
41
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
42
42
  # @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
43
43
  # @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
44
- # @return [Object]
44
+ # @return [nil]
45
45
  describe 'datacenters_networkloadbalancers_delete test' do
46
46
  it 'should work' do
47
47
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -74,7 +74,7 @@ describe 'NetworkLoadBalancersApi' do
74
74
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
75
75
  # @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
76
76
  # @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
77
- # @return [Object]
77
+ # @return [nil]
78
78
  describe 'datacenters_networkloadbalancers_flowlogs_delete test' do
79
79
  it 'should work' do
80
80
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -177,7 +177,7 @@ describe 'NetworkLoadBalancersApi' do
177
177
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
178
178
  # @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
179
179
  # @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
180
- # @return [Object]
180
+ # @return [nil]
181
181
  describe 'datacenters_networkloadbalancers_forwardingrules_delete test' do
182
182
  it 'should work' do
183
183
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -40,7 +40,7 @@ describe 'PrivateCrossConnectsApi' do
40
40
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
41
41
  # @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
42
42
  # @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
43
- # @return [Object]
43
+ # @return [nil]
44
44
  describe 'pccs_delete test' do
45
45
  it 'should work' do
46
46
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -3,7 +3,7 @@
3
3
 
4
4
  #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.
5
5
 
6
- The version of the OpenAPI document: 6.0
6
+ The version of the OpenAPI document: 6.0-SDK.1
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
9
  OpenAPI Generator version: 5.0.1-SNAPSHOT
@@ -42,7 +42,7 @@ describe 'ServersApi' do
42
42
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
43
43
  # @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
44
44
  # @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
45
- # @return [Object]
45
+ # @return [nil]
46
46
  describe 'datacenters_servers_cdroms_delete test' do
47
47
  it 'should work' do
48
48
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -110,7 +110,7 @@ describe 'ServersApi' do
110
110
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
111
111
  # @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
112
112
  # @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
113
- # @return [Object]
113
+ # @return [nil]
114
114
  describe 'datacenters_servers_delete test' do
115
115
  it 'should work' do
116
116
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -210,7 +210,7 @@ describe 'ServersApi' do
210
210
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
211
211
  # @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
212
212
  # @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
213
- # @return [Object]
213
+ # @return [nil]
214
214
  describe 'datacenters_servers_reboot_post test' do
215
215
  it 'should work' do
216
216
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -242,7 +242,7 @@ describe 'ServersApi' do
242
242
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
243
243
  # @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
244
244
  # @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
245
- # @return [Object]
245
+ # @return [nil]
246
246
  describe 'datacenters_servers_resume_post test' do
247
247
  it 'should work' do
248
248
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -258,7 +258,7 @@ describe 'ServersApi' do
258
258
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
259
259
  # @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
260
260
  # @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
261
- # @return [Object]
261
+ # @return [nil]
262
262
  describe 'datacenters_servers_start_post test' do
263
263
  it 'should work' do
264
264
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -274,7 +274,7 @@ describe 'ServersApi' do
274
274
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
275
275
  # @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
276
276
  # @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
277
- # @return [Object]
277
+ # @return [nil]
278
278
  describe 'datacenters_servers_stop_post test' do
279
279
  it 'should work' do
280
280
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -290,7 +290,7 @@ describe 'ServersApi' do
290
290
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
291
291
  # @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
292
292
  # @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
293
- # @return [Object]
293
+ # @return [nil]
294
294
  describe 'datacenters_servers_suspend_post test' do
295
295
  it 'should work' do
296
296
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -322,7 +322,7 @@ describe 'ServersApi' do
322
322
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
323
323
  # @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
324
324
  # @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
325
- # @return [Object]
325
+ # @return [nil]
326
326
  describe 'datacenters_servers_upgrade_post test' do
327
327
  it 'should work' do
328
328
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers
@@ -339,7 +339,7 @@ describe 'ServersApi' do
339
339
  # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
340
340
  # @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
341
341
  # @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
342
- # @return [Object]
342
+ # @return [nil]
343
343
  describe 'datacenters_servers_volumes_delete test' do
344
344
  it 'should work' do
345
345
  # assertion here. ref: https://www.relishapp.com/rspec/rspec-expectations/docs/built-in-matchers