ionoscloud 6.0.0.beta.3 → 6.0.0.beta.4

Sign up to get free protection for your applications and to get access to all the features.
Files changed (594) hide show
  1. checksums.yaml +4 -4
  2. data/LICENSE +190 -0
  3. data/docs/{BackupUnitsApi.md → api/BackupUnitsApi.md} +40 -40
  4. data/docs/{ContractResourcesApi.md → api/ContractResourcesApi.md} +6 -6
  5. data/docs/api/DataCentersApi.md +516 -0
  6. data/docs/api/DefaultApi.md +78 -0
  7. data/docs/{FirewallRulesApi.md → api/FirewallRulesApi.md} +52 -52
  8. data/docs/{FlowLogsApi.md → api/FlowLogsApi.md} +40 -40
  9. data/docs/{IPBlocksApi.md → api/IPBlocksApi.md} +40 -36
  10. data/docs/{ImagesApi.md → api/ImagesApi.md} +30 -30
  11. data/docs/{KubernetesApi.md → api/KubernetesApi.md} +98 -98
  12. data/docs/{LabelsApi.md → api/LabelsApi.md} +182 -190
  13. data/docs/{LansApi.md → api/LansApi.md} +80 -80
  14. data/docs/{LoadBalancersApi.md → api/LoadBalancersApi.md} +84 -92
  15. data/docs/{LocationsApi.md → api/LocationsApi.md} +32 -32
  16. data/docs/{NATGatewaysApi.md → api/NATGatewaysApi.md} +136 -140
  17. data/docs/{NetworkInterfacesApi.md → api/NetworkInterfacesApi.md} +52 -52
  18. data/docs/{NetworkLoadBalancersApi.md → api/NetworkLoadBalancersApi.md} +151 -155
  19. data/docs/{PrivateCrossConnectsApi.md → api/PrivateCrossConnectsApi.md} +31 -35
  20. data/docs/{RequestsApi.md → api/RequestsApi.md} +22 -22
  21. data/docs/{ServersApi.md → api/ServersApi.md} +188 -188
  22. data/docs/{SnapshotsApi.md → api/SnapshotsApi.md} +30 -30
  23. data/docs/{TemplatesApi.md → api/TemplatesApi.md} +4 -4
  24. data/docs/{UserManagementApi.md → api/UserManagementApi.md} +148 -144
  25. data/docs/{UserS3KeysApi.md → api/UserS3KeysApi.md} +34 -34
  26. data/docs/{VolumesApi.md → api/VolumesApi.md} +68 -68
  27. data/docs/{AttachedVolumes.md → models/AttachedVolumes.md} +0 -0
  28. data/docs/{BackupUnit.md → models/BackupUnit.md} +0 -0
  29. data/docs/{BackupUnitProperties.md → models/BackupUnitProperties.md} +0 -0
  30. data/docs/{BackupUnitSSO.md → models/BackupUnitSSO.md} +0 -0
  31. data/docs/{BackupUnits.md → models/BackupUnits.md} +0 -0
  32. data/docs/{BalancedNics.md → models/BalancedNics.md} +0 -0
  33. data/docs/{Cdroms.md → models/Cdroms.md} +0 -0
  34. data/docs/{ConnectableDatacenter.md → models/ConnectableDatacenter.md} +0 -0
  35. data/docs/{Contract.md → models/Contract.md} +0 -0
  36. data/docs/{ContractProperties.md → models/ContractProperties.md} +0 -0
  37. data/docs/{Contracts.md → models/Contracts.md} +0 -0
  38. data/docs/{CpuArchitectureProperties.md → models/CpuArchitectureProperties.md} +0 -0
  39. data/docs/{DataCenterEntities.md → models/DataCenterEntities.md} +0 -0
  40. data/docs/{Datacenter.md → models/Datacenter.md} +0 -0
  41. data/docs/{DatacenterElementMetadata.md → models/DatacenterElementMetadata.md} +0 -0
  42. data/docs/{DatacenterProperties.md → models/DatacenterProperties.md} +0 -0
  43. data/docs/{Datacenters.md → models/Datacenters.md} +0 -0
  44. data/docs/{Error.md → models/Error.md} +0 -0
  45. data/docs/{ErrorMessage.md → models/ErrorMessage.md} +0 -0
  46. data/docs/{FirewallRule.md → models/FirewallRule.md} +0 -0
  47. data/docs/{FirewallRules.md → models/FirewallRules.md} +0 -0
  48. data/docs/{FirewallruleProperties.md → models/FirewallruleProperties.md} +0 -0
  49. data/docs/{FlowLog.md → models/FlowLog.md} +0 -0
  50. data/docs/{FlowLogProperties.md → models/FlowLogProperties.md} +0 -0
  51. data/docs/{FlowLogPut.md → models/FlowLogPut.md} +0 -0
  52. data/docs/{FlowLogs.md → models/FlowLogs.md} +0 -0
  53. data/docs/{Group.md → models/Group.md} +0 -0
  54. data/docs/{GroupEntities.md → models/GroupEntities.md} +0 -0
  55. data/docs/{GroupMembers.md → models/GroupMembers.md} +0 -0
  56. data/docs/{GroupProperties.md → models/GroupProperties.md} +0 -0
  57. data/docs/{GroupShare.md → models/GroupShare.md} +0 -0
  58. data/docs/{GroupShareProperties.md → models/GroupShareProperties.md} +0 -0
  59. data/docs/{GroupShares.md → models/GroupShares.md} +0 -0
  60. data/docs/{GroupUsers.md → models/GroupUsers.md} +0 -0
  61. data/docs/{Groups.md → models/Groups.md} +0 -0
  62. data/docs/{IPFailover.md → models/IPFailover.md} +0 -0
  63. data/docs/{Image.md → models/Image.md} +0 -0
  64. data/docs/{ImageProperties.md → models/ImageProperties.md} +0 -0
  65. data/docs/{Images.md → models/Images.md} +0 -0
  66. data/docs/{Info.md → models/Info.md} +0 -0
  67. data/docs/{IpBlock.md → models/IpBlock.md} +0 -0
  68. data/docs/{IpBlockProperties.md → models/IpBlockProperties.md} +0 -0
  69. data/docs/{IpBlocks.md → models/IpBlocks.md} +7 -1
  70. data/docs/{IpConsumer.md → models/IpConsumer.md} +0 -0
  71. data/docs/{KubernetesAutoScaling.md → models/KubernetesAutoScaling.md} +0 -0
  72. data/docs/{KubernetesCluster.md → models/KubernetesCluster.md} +0 -0
  73. data/docs/{KubernetesClusterEntities.md → models/KubernetesClusterEntities.md} +0 -0
  74. data/docs/{KubernetesClusterForPost.md → models/KubernetesClusterForPost.md} +0 -0
  75. data/docs/{KubernetesClusterForPut.md → models/KubernetesClusterForPut.md} +0 -0
  76. data/docs/{KubernetesClusterProperties.md → models/KubernetesClusterProperties.md} +4 -2
  77. data/docs/{KubernetesClusterPropertiesForPost.md → models/KubernetesClusterPropertiesForPost.md} +4 -2
  78. data/docs/{KubernetesClusterPropertiesForPut.md → models/KubernetesClusterPropertiesForPut.md} +5 -1
  79. data/docs/{KubernetesClusters.md → models/KubernetesClusters.md} +0 -0
  80. data/docs/{KubernetesMaintenanceWindow.md → models/KubernetesMaintenanceWindow.md} +0 -0
  81. data/docs/{KubernetesNode.md → models/KubernetesNode.md} +0 -0
  82. data/docs/{KubernetesNodeMetadata.md → models/KubernetesNodeMetadata.md} +0 -0
  83. data/docs/{KubernetesNodePool.md → models/KubernetesNodePool.md} +0 -0
  84. data/docs/{KubernetesNodePoolForPost.md → models/KubernetesNodePoolForPost.md} +0 -0
  85. data/docs/{KubernetesNodePoolForPut.md → models/KubernetesNodePoolForPut.md} +0 -0
  86. data/docs/{KubernetesNodePoolLan.md → models/KubernetesNodePoolLan.md} +1 -1
  87. data/docs/{KubernetesNodePoolLanRoutes.md → models/KubernetesNodePoolLanRoutes.md} +0 -0
  88. data/docs/{KubernetesNodePoolProperties.md → models/KubernetesNodePoolProperties.md} +3 -1
  89. data/docs/{KubernetesNodePoolPropertiesForPost.md → models/KubernetesNodePoolPropertiesForPost.md} +3 -1
  90. data/docs/{KubernetesNodePoolPropertiesForPut.md → models/KubernetesNodePoolPropertiesForPut.md} +0 -0
  91. data/docs/{KubernetesNodePools.md → models/KubernetesNodePools.md} +0 -0
  92. data/docs/{KubernetesNodeProperties.md → models/KubernetesNodeProperties.md} +0 -0
  93. data/docs/{KubernetesNodes.md → models/KubernetesNodes.md} +0 -0
  94. data/docs/{Label.md → models/Label.md} +0 -0
  95. data/docs/{LabelProperties.md → models/LabelProperties.md} +0 -0
  96. data/docs/{LabelResource.md → models/LabelResource.md} +0 -0
  97. data/docs/{LabelResourceProperties.md → models/LabelResourceProperties.md} +0 -0
  98. data/docs/{LabelResources.md → models/LabelResources.md} +0 -0
  99. data/docs/{Labels.md → models/Labels.md} +0 -0
  100. data/docs/{Lan.md → models/Lan.md} +0 -0
  101. data/docs/{LanEntities.md → models/LanEntities.md} +0 -0
  102. data/docs/{LanNics.md → models/LanNics.md} +0 -0
  103. data/docs/{LanPost.md → models/LanPost.md} +0 -0
  104. data/docs/{LanProperties.md → models/LanProperties.md} +0 -0
  105. data/docs/{LanPropertiesPost.md → models/LanPropertiesPost.md} +0 -0
  106. data/docs/{Lans.md → models/Lans.md} +0 -0
  107. data/docs/{Loadbalancer.md → models/Loadbalancer.md} +0 -0
  108. data/docs/{LoadbalancerEntities.md → models/LoadbalancerEntities.md} +0 -0
  109. data/docs/{LoadbalancerProperties.md → models/LoadbalancerProperties.md} +0 -0
  110. data/docs/{Loadbalancers.md → models/Loadbalancers.md} +0 -0
  111. data/docs/{Location.md → models/Location.md} +0 -0
  112. data/docs/{LocationProperties.md → models/LocationProperties.md} +0 -0
  113. data/docs/{Locations.md → models/Locations.md} +0 -0
  114. data/docs/{NatGateway.md → models/NatGateway.md} +0 -0
  115. data/docs/{NatGatewayEntities.md → models/NatGatewayEntities.md} +0 -0
  116. data/docs/{NatGatewayLanProperties.md → models/NatGatewayLanProperties.md} +0 -0
  117. data/docs/{NatGatewayProperties.md → models/NatGatewayProperties.md} +0 -0
  118. data/docs/{NatGatewayPut.md → models/NatGatewayPut.md} +0 -0
  119. data/docs/{NatGatewayRule.md → models/NatGatewayRule.md} +0 -0
  120. data/docs/{NatGatewayRuleProperties.md → models/NatGatewayRuleProperties.md} +0 -0
  121. data/docs/{NatGatewayRuleProtocol.md → models/NatGatewayRuleProtocol.md} +0 -0
  122. data/docs/{NatGatewayRulePut.md → models/NatGatewayRulePut.md} +0 -0
  123. data/docs/{NatGatewayRuleType.md → models/NatGatewayRuleType.md} +0 -0
  124. data/docs/{NatGatewayRules.md → models/NatGatewayRules.md} +0 -0
  125. data/docs/{NatGateways.md → models/NatGateways.md} +0 -0
  126. data/docs/{NetworkLoadBalancer.md → models/NetworkLoadBalancer.md} +0 -0
  127. data/docs/{NetworkLoadBalancerEntities.md → models/NetworkLoadBalancerEntities.md} +0 -0
  128. data/docs/{NetworkLoadBalancerForwardingRule.md → models/NetworkLoadBalancerForwardingRule.md} +0 -0
  129. data/docs/{NetworkLoadBalancerForwardingRuleHealthCheck.md → models/NetworkLoadBalancerForwardingRuleHealthCheck.md} +0 -2
  130. data/docs/{NetworkLoadBalancerForwardingRuleProperties.md → models/NetworkLoadBalancerForwardingRuleProperties.md} +1 -1
  131. data/docs/{NetworkLoadBalancerForwardingRulePut.md → models/NetworkLoadBalancerForwardingRulePut.md} +0 -0
  132. data/docs/{NetworkLoadBalancerForwardingRuleTarget.md → models/NetworkLoadBalancerForwardingRuleTarget.md} +0 -0
  133. data/docs/{NetworkLoadBalancerForwardingRuleTargetHealthCheck.md → models/NetworkLoadBalancerForwardingRuleTargetHealthCheck.md} +0 -0
  134. data/docs/{NetworkLoadBalancerForwardingRules.md → models/NetworkLoadBalancerForwardingRules.md} +0 -0
  135. data/docs/{NetworkLoadBalancerProperties.md → models/NetworkLoadBalancerProperties.md} +0 -0
  136. data/docs/{NetworkLoadBalancerPut.md → models/NetworkLoadBalancerPut.md} +0 -0
  137. data/docs/{NetworkLoadBalancers.md → models/NetworkLoadBalancers.md} +0 -0
  138. data/docs/{Nic.md → models/Nic.md} +0 -0
  139. data/docs/{NicEntities.md → models/NicEntities.md} +0 -0
  140. data/docs/{NicProperties.md → models/NicProperties.md} +0 -0
  141. data/docs/{NicPut.md → models/NicPut.md} +0 -0
  142. data/docs/{Nics.md → models/Nics.md} +0 -0
  143. data/docs/{NoStateMetaData.md → models/NoStateMetaData.md} +0 -0
  144. data/docs/{PaginationLinks.md → models/PaginationLinks.md} +0 -0
  145. data/docs/{Peer.md → models/Peer.md} +0 -0
  146. data/docs/{PrivateCrossConnect.md → models/PrivateCrossConnect.md} +0 -0
  147. data/docs/{PrivateCrossConnectProperties.md → models/PrivateCrossConnectProperties.md} +1 -1
  148. data/docs/{PrivateCrossConnects.md → models/PrivateCrossConnects.md} +0 -0
  149. data/docs/{RemoteConsoleUrl.md → models/RemoteConsoleUrl.md} +0 -0
  150. data/docs/{Request.md → models/Request.md} +0 -0
  151. data/docs/{RequestMetadata.md → models/RequestMetadata.md} +0 -0
  152. data/docs/{RequestProperties.md → models/RequestProperties.md} +0 -0
  153. data/docs/{RequestStatus.md → models/RequestStatus.md} +0 -0
  154. data/docs/{RequestStatusMetadata.md → models/RequestStatusMetadata.md} +0 -0
  155. data/docs/{RequestTarget.md → models/RequestTarget.md} +0 -0
  156. data/docs/{Requests.md → models/Requests.md} +1 -1
  157. data/docs/{Resource.md → models/Resource.md} +0 -0
  158. data/docs/{ResourceEntities.md → models/ResourceEntities.md} +0 -0
  159. data/docs/{ResourceGroups.md → models/ResourceGroups.md} +0 -0
  160. data/docs/{ResourceLimits.md → models/ResourceLimits.md} +0 -0
  161. data/docs/{ResourceProperties.md → models/ResourceProperties.md} +1 -1
  162. data/docs/{ResourceReference.md → models/ResourceReference.md} +0 -0
  163. data/docs/{Resources.md → models/Resources.md} +0 -0
  164. data/docs/{ResourcesUsers.md → models/ResourcesUsers.md} +0 -0
  165. data/docs/models/S3Bucket.md +18 -0
  166. data/docs/{S3Key.md → models/S3Key.md} +0 -0
  167. data/docs/{S3KeyMetadata.md → models/S3KeyMetadata.md} +0 -0
  168. data/docs/{S3KeyProperties.md → models/S3KeyProperties.md} +0 -0
  169. data/docs/{S3Keys.md → models/S3Keys.md} +0 -0
  170. data/docs/{S3ObjectStorageSSO.md → models/S3ObjectStorageSSO.md} +0 -0
  171. data/docs/{Server.md → models/Server.md} +0 -0
  172. data/docs/{ServerEntities.md → models/ServerEntities.md} +0 -0
  173. data/docs/{ServerProperties.md → models/ServerProperties.md} +0 -0
  174. data/docs/{Servers.md → models/Servers.md} +0 -0
  175. data/docs/{Snapshot.md → models/Snapshot.md} +0 -0
  176. data/docs/{SnapshotProperties.md → models/SnapshotProperties.md} +0 -0
  177. data/docs/{Snapshots.md → models/Snapshots.md} +0 -0
  178. data/docs/{TargetPortRange.md → models/TargetPortRange.md} +0 -0
  179. data/docs/{Template.md → models/Template.md} +0 -0
  180. data/docs/{TemplateProperties.md → models/TemplateProperties.md} +0 -0
  181. data/docs/{Templates.md → models/Templates.md} +0 -0
  182. data/docs/{Token.md → models/Token.md} +0 -0
  183. data/docs/{Type.md → models/Type.md} +0 -0
  184. data/docs/{User.md → models/User.md} +0 -0
  185. data/docs/{UserMetadata.md → models/UserMetadata.md} +0 -0
  186. data/docs/{UserPost.md → models/UserPost.md} +0 -0
  187. data/docs/{UserProperties.md → models/UserProperties.md} +0 -0
  188. data/docs/{UserPropertiesPost.md → models/UserPropertiesPost.md} +0 -0
  189. data/docs/{UserPropertiesPut.md → models/UserPropertiesPut.md} +0 -0
  190. data/docs/{UserPut.md → models/UserPut.md} +0 -0
  191. data/docs/models/Users.md +30 -0
  192. data/docs/{UsersEntities.md → models/UsersEntities.md} +0 -0
  193. data/docs/{Volume.md → models/Volume.md} +0 -0
  194. data/docs/{VolumeProperties.md → models/VolumeProperties.md} +2 -0
  195. data/docs/{Volumes.md → models/Volumes.md} +0 -0
  196. data/ionoscloud.gemspec +4 -4
  197. data/lib/ionoscloud/api/_api.rb +9 -9
  198. data/lib/ionoscloud/api/backup_units_api.rb +43 -43
  199. data/lib/ionoscloud/api/contract_resources_api.rb +9 -9
  200. data/lib/ionoscloud/api/data_centers_api.rb +81 -81
  201. data/lib/ionoscloud/api/firewall_rules_api.rb +55 -55
  202. data/lib/ionoscloud/api/flow_logs_api.rb +43 -43
  203. data/lib/ionoscloud/api/images_api.rb +33 -33
  204. data/lib/ionoscloud/api/ip_blocks_api.rb +57 -39
  205. data/lib/ionoscloud/api/kubernetes_api.rb +105 -105
  206. data/lib/ionoscloud/api/labels_api.rb +185 -221
  207. data/lib/ionoscloud/api/lans_api.rb +83 -83
  208. data/lib/ionoscloud/api/load_balancers_api.rb +87 -123
  209. data/lib/ionoscloud/api/locations_api.rb +31 -31
  210. data/lib/ionoscloud/api/nat_gateways_api.rb +139 -157
  211. data/lib/ionoscloud/api/network_interfaces_api.rb +55 -55
  212. data/lib/ionoscloud/api/network_load_balancers_api.rb +151 -169
  213. data/lib/ionoscloud/api/private_cross_connects_api.rb +35 -53
  214. data/lib/ionoscloud/api/requests_api.rb +25 -25
  215. data/lib/ionoscloud/api/servers_api.rb +191 -191
  216. data/lib/ionoscloud/api/snapshots_api.rb +33 -33
  217. data/lib/ionoscloud/api/templates_api.rb +7 -7
  218. data/lib/ionoscloud/api/user_management_api.rb +165 -147
  219. data/lib/ionoscloud/api/user_s3_keys_api.rb +37 -37
  220. data/lib/ionoscloud/api/volumes_api.rb +71 -71
  221. data/lib/ionoscloud/api_client.rb +8 -7
  222. data/lib/ionoscloud/api_error.rb +3 -3
  223. data/lib/ionoscloud/configuration.rb +3 -3
  224. data/lib/ionoscloud/models/attached_volumes.rb +5 -3
  225. data/lib/ionoscloud/models/backup_unit.rb +5 -3
  226. data/lib/ionoscloud/models/backup_unit_properties.rb +5 -3
  227. data/lib/ionoscloud/models/backup_unit_sso.rb +5 -3
  228. data/lib/ionoscloud/models/backup_units.rb +5 -3
  229. data/lib/ionoscloud/models/balanced_nics.rb +5 -3
  230. data/lib/ionoscloud/models/cdroms.rb +5 -3
  231. data/lib/ionoscloud/models/connectable_datacenter.rb +5 -3
  232. data/lib/ionoscloud/models/contract.rb +5 -3
  233. data/lib/ionoscloud/models/contract_properties.rb +5 -3
  234. data/lib/ionoscloud/models/contracts.rb +5 -3
  235. data/lib/ionoscloud/models/cpu_architecture_properties.rb +5 -3
  236. data/lib/ionoscloud/models/data_center_entities.rb +5 -3
  237. data/lib/ionoscloud/models/datacenter.rb +5 -3
  238. data/lib/ionoscloud/models/datacenter_element_metadata.rb +5 -3
  239. data/lib/ionoscloud/models/datacenter_properties.rb +5 -3
  240. data/lib/ionoscloud/models/datacenters.rb +5 -3
  241. data/lib/ionoscloud/models/error.rb +5 -3
  242. data/lib/ionoscloud/models/error_message.rb +5 -3
  243. data/lib/ionoscloud/models/firewall_rule.rb +5 -3
  244. data/lib/ionoscloud/models/firewall_rules.rb +5 -3
  245. data/lib/ionoscloud/models/firewallrule_properties.rb +5 -3
  246. data/lib/ionoscloud/models/flow_log.rb +5 -3
  247. data/lib/ionoscloud/models/flow_log_properties.rb +5 -3
  248. data/lib/ionoscloud/models/flow_log_put.rb +5 -3
  249. data/lib/ionoscloud/models/flow_logs.rb +5 -3
  250. data/lib/ionoscloud/models/group.rb +5 -3
  251. data/lib/ionoscloud/models/group_entities.rb +5 -3
  252. data/lib/ionoscloud/models/group_members.rb +5 -3
  253. data/lib/ionoscloud/models/group_properties.rb +5 -3
  254. data/lib/ionoscloud/models/group_share.rb +5 -3
  255. data/lib/ionoscloud/models/group_share_properties.rb +5 -3
  256. data/lib/ionoscloud/models/group_shares.rb +5 -3
  257. data/lib/ionoscloud/models/group_users.rb +5 -3
  258. data/lib/ionoscloud/models/groups.rb +5 -3
  259. data/lib/ionoscloud/models/image.rb +5 -3
  260. data/lib/ionoscloud/models/image_properties.rb +7 -5
  261. data/lib/ionoscloud/models/images.rb +5 -3
  262. data/lib/ionoscloud/models/info.rb +5 -3
  263. data/lib/ionoscloud/models/ip_block.rb +5 -3
  264. data/lib/ionoscloud/models/ip_block_properties.rb +5 -3
  265. data/lib/ionoscloud/models/ip_blocks.rb +38 -7
  266. data/lib/ionoscloud/models/ip_consumer.rb +5 -3
  267. data/lib/ionoscloud/models/ip_failover.rb +5 -3
  268. data/lib/ionoscloud/models/kubernetes_auto_scaling.rb +5 -3
  269. data/lib/ionoscloud/models/kubernetes_cluster.rb +5 -3
  270. data/lib/ionoscloud/models/kubernetes_cluster_entities.rb +5 -3
  271. data/lib/ionoscloud/models/kubernetes_cluster_for_post.rb +5 -3
  272. data/lib/ionoscloud/models/kubernetes_cluster_for_put.rb +5 -3
  273. data/lib/ionoscloud/models/kubernetes_cluster_properties.rb +27 -11
  274. data/lib/ionoscloud/models/kubernetes_cluster_properties_for_post.rb +27 -11
  275. data/lib/ionoscloud/models/kubernetes_cluster_properties_for_put.rb +33 -7
  276. data/lib/ionoscloud/models/kubernetes_clusters.rb +5 -3
  277. data/lib/ionoscloud/models/kubernetes_maintenance_window.rb +5 -3
  278. data/lib/ionoscloud/models/kubernetes_node.rb +5 -3
  279. data/lib/ionoscloud/models/kubernetes_node_metadata.rb +5 -3
  280. data/lib/ionoscloud/models/kubernetes_node_pool.rb +5 -3
  281. data/lib/ionoscloud/models/kubernetes_node_pool_for_post.rb +5 -3
  282. data/lib/ionoscloud/models/kubernetes_node_pool_for_put.rb +5 -3
  283. data/lib/ionoscloud/models/kubernetes_node_pool_lan.rb +10 -3
  284. data/lib/ionoscloud/models/kubernetes_node_pool_lan_routes.rb +5 -3
  285. data/lib/ionoscloud/models/kubernetes_node_pool_properties.rb +19 -7
  286. data/lib/ionoscloud/models/kubernetes_node_pool_properties_for_post.rb +19 -7
  287. data/lib/ionoscloud/models/kubernetes_node_pool_properties_for_put.rb +5 -3
  288. data/lib/ionoscloud/models/kubernetes_node_pools.rb +5 -3
  289. data/lib/ionoscloud/models/kubernetes_node_properties.rb +5 -3
  290. data/lib/ionoscloud/models/kubernetes_nodes.rb +5 -3
  291. data/lib/ionoscloud/models/label.rb +5 -3
  292. data/lib/ionoscloud/models/label_properties.rb +5 -3
  293. data/lib/ionoscloud/models/label_resource.rb +5 -3
  294. data/lib/ionoscloud/models/label_resource_properties.rb +5 -3
  295. data/lib/ionoscloud/models/label_resources.rb +5 -3
  296. data/lib/ionoscloud/models/labels.rb +5 -3
  297. data/lib/ionoscloud/models/lan.rb +5 -3
  298. data/lib/ionoscloud/models/lan_entities.rb +5 -3
  299. data/lib/ionoscloud/models/lan_nics.rb +5 -3
  300. data/lib/ionoscloud/models/lan_post.rb +5 -3
  301. data/lib/ionoscloud/models/lan_properties.rb +5 -3
  302. data/lib/ionoscloud/models/lan_properties_post.rb +5 -3
  303. data/lib/ionoscloud/models/lans.rb +5 -3
  304. data/lib/ionoscloud/models/loadbalancer.rb +5 -3
  305. data/lib/ionoscloud/models/loadbalancer_entities.rb +5 -3
  306. data/lib/ionoscloud/models/loadbalancer_properties.rb +5 -3
  307. data/lib/ionoscloud/models/loadbalancers.rb +5 -3
  308. data/lib/ionoscloud/models/location.rb +5 -3
  309. data/lib/ionoscloud/models/location_properties.rb +5 -3
  310. data/lib/ionoscloud/models/locations.rb +5 -3
  311. data/lib/ionoscloud/models/nat_gateway.rb +5 -3
  312. data/lib/ionoscloud/models/nat_gateway_entities.rb +5 -3
  313. data/lib/ionoscloud/models/nat_gateway_lan_properties.rb +5 -3
  314. data/lib/ionoscloud/models/nat_gateway_properties.rb +5 -3
  315. data/lib/ionoscloud/models/nat_gateway_put.rb +5 -3
  316. data/lib/ionoscloud/models/nat_gateway_rule.rb +5 -3
  317. data/lib/ionoscloud/models/nat_gateway_rule_properties.rb +5 -3
  318. data/lib/ionoscloud/models/nat_gateway_rule_protocol.rb +3 -3
  319. data/lib/ionoscloud/models/nat_gateway_rule_put.rb +5 -3
  320. data/lib/ionoscloud/models/nat_gateway_rule_type.rb +3 -3
  321. data/lib/ionoscloud/models/nat_gateway_rules.rb +5 -3
  322. data/lib/ionoscloud/models/nat_gateways.rb +5 -3
  323. data/lib/ionoscloud/models/network_load_balancer.rb +5 -3
  324. data/lib/ionoscloud/models/network_load_balancer_entities.rb +5 -3
  325. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule.rb +5 -3
  326. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_health_check.rb +6 -14
  327. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_properties.rb +7 -5
  328. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_put.rb +5 -3
  329. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_target.rb +5 -3
  330. data/lib/ionoscloud/models/network_load_balancer_forwarding_rule_target_health_check.rb +5 -3
  331. data/lib/ionoscloud/models/network_load_balancer_forwarding_rules.rb +5 -3
  332. data/lib/ionoscloud/models/network_load_balancer_properties.rb +5 -3
  333. data/lib/ionoscloud/models/network_load_balancer_put.rb +5 -3
  334. data/lib/ionoscloud/models/network_load_balancers.rb +5 -3
  335. data/lib/ionoscloud/models/nic.rb +5 -3
  336. data/lib/ionoscloud/models/nic_entities.rb +5 -3
  337. data/lib/ionoscloud/models/nic_properties.rb +5 -3
  338. data/lib/ionoscloud/models/nic_put.rb +5 -3
  339. data/lib/ionoscloud/models/nics.rb +5 -3
  340. data/lib/ionoscloud/models/no_state_meta_data.rb +5 -3
  341. data/lib/ionoscloud/models/pagination_links.rb +5 -3
  342. data/lib/ionoscloud/models/peer.rb +5 -3
  343. data/lib/ionoscloud/models/private_cross_connect.rb +5 -3
  344. data/lib/ionoscloud/models/private_cross_connect_properties.rb +6 -4
  345. data/lib/ionoscloud/models/private_cross_connects.rb +5 -3
  346. data/lib/ionoscloud/models/remote_console_url.rb +5 -3
  347. data/lib/ionoscloud/models/request.rb +5 -3
  348. data/lib/ionoscloud/models/request_metadata.rb +5 -3
  349. data/lib/ionoscloud/models/request_properties.rb +5 -3
  350. data/lib/ionoscloud/models/request_status.rb +5 -3
  351. data/lib/ionoscloud/models/request_status_metadata.rb +5 -3
  352. data/lib/ionoscloud/models/request_target.rb +5 -3
  353. data/lib/ionoscloud/models/requests.rb +6 -4
  354. data/lib/ionoscloud/models/resource.rb +5 -3
  355. data/lib/ionoscloud/models/resource_entities.rb +5 -3
  356. data/lib/ionoscloud/models/resource_groups.rb +5 -3
  357. data/lib/ionoscloud/models/resource_limits.rb +5 -3
  358. data/lib/ionoscloud/models/resource_properties.rb +6 -4
  359. data/lib/ionoscloud/models/resource_reference.rb +5 -3
  360. data/lib/ionoscloud/models/resources.rb +5 -3
  361. data/lib/ionoscloud/models/resources_users.rb +5 -3
  362. data/lib/ionoscloud/models/s3_bucket.rb +224 -0
  363. data/lib/ionoscloud/models/s3_key.rb +5 -3
  364. data/lib/ionoscloud/models/s3_key_metadata.rb +5 -3
  365. data/lib/ionoscloud/models/s3_key_properties.rb +5 -3
  366. data/lib/ionoscloud/models/s3_keys.rb +5 -3
  367. data/lib/ionoscloud/models/s3_object_storage_sso.rb +5 -3
  368. data/lib/ionoscloud/models/server.rb +5 -3
  369. data/lib/ionoscloud/models/server_entities.rb +5 -3
  370. data/lib/ionoscloud/models/server_properties.rb +5 -3
  371. data/lib/ionoscloud/models/servers.rb +5 -3
  372. data/lib/ionoscloud/models/snapshot.rb +5 -3
  373. data/lib/ionoscloud/models/snapshot_properties.rb +5 -3
  374. data/lib/ionoscloud/models/snapshots.rb +5 -3
  375. data/lib/ionoscloud/models/target_port_range.rb +5 -3
  376. data/lib/ionoscloud/models/template.rb +5 -3
  377. data/lib/ionoscloud/models/template_properties.rb +5 -3
  378. data/lib/ionoscloud/models/templates.rb +5 -3
  379. data/lib/ionoscloud/models/token.rb +5 -3
  380. data/lib/ionoscloud/models/type.rb +5 -5
  381. data/lib/ionoscloud/models/user.rb +5 -3
  382. data/lib/ionoscloud/models/user_metadata.rb +5 -3
  383. data/lib/ionoscloud/models/user_post.rb +5 -3
  384. data/lib/ionoscloud/models/user_properties.rb +5 -3
  385. data/lib/ionoscloud/models/user_properties_post.rb +5 -3
  386. data/lib/ionoscloud/models/user_properties_put.rb +5 -3
  387. data/lib/ionoscloud/models/user_put.rb +5 -3
  388. data/lib/ionoscloud/models/users.rb +38 -7
  389. data/lib/ionoscloud/models/users_entities.rb +5 -3
  390. data/lib/ionoscloud/models/volume.rb +5 -3
  391. data/lib/ionoscloud/models/volume_properties.rb +19 -8
  392. data/lib/ionoscloud/models/volumes.rb +5 -3
  393. data/lib/ionoscloud/version.rb +4 -4
  394. data/lib/ionoscloud.rb +4 -3
  395. data/spec/api/_api_spec.rb +6 -6
  396. data/spec/api/backup_units_api_spec.rb +23 -23
  397. data/spec/api/contract_resources_api_spec.rb +6 -6
  398. data/spec/api/data_centers_api_spec.rb +42 -42
  399. data/spec/api/firewall_rules_api_spec.rb +29 -29
  400. data/spec/api/flow_logs_api_spec.rb +23 -23
  401. data/spec/api/images_api_spec.rb +18 -18
  402. data/spec/api/ip_blocks_api_spec.rb +23 -21
  403. data/spec/api/kubernetes_api_spec.rb +50 -50
  404. data/spec/api/labels_api_spec.rb +94 -98
  405. data/spec/api/lans_api_spec.rb +43 -43
  406. data/spec/api/load_balancers_api_spec.rb +45 -49
  407. data/spec/api/locations_api_spec.rb +17 -17
  408. data/spec/api/nat_gateways_api_spec.rb +71 -73
  409. data/spec/api/network_interfaces_api_spec.rb +29 -29
  410. data/spec/api/network_load_balancers_api_spec.rb +77 -79
  411. data/spec/api/private_cross_connects_api_spec.rb +19 -21
  412. data/spec/api/requests_api_spec.rb +14 -14
  413. data/spec/api/servers_api_spec.rb +97 -97
  414. data/spec/api/snapshots_api_spec.rb +18 -18
  415. data/spec/api/templates_api_spec.rb +5 -5
  416. data/spec/api/user_management_api_spec.rb +77 -75
  417. data/spec/api/user_s3_keys_api_spec.rb +20 -20
  418. data/spec/api/volumes_api_spec.rb +37 -37
  419. data/spec/api_client_spec.rb +3 -3
  420. data/spec/configuration_spec.rb +3 -3
  421. data/spec/models/attached_volumes_spec.rb +3 -3
  422. data/spec/models/backup_unit_properties_spec.rb +3 -3
  423. data/spec/models/backup_unit_spec.rb +3 -3
  424. data/spec/models/backup_unit_sso_spec.rb +3 -3
  425. data/spec/models/backup_units_spec.rb +3 -3
  426. data/spec/models/balanced_nics_spec.rb +3 -3
  427. data/spec/models/cdroms_spec.rb +3 -3
  428. data/spec/models/connectable_datacenter_spec.rb +3 -3
  429. data/spec/models/contract_properties_spec.rb +3 -3
  430. data/spec/models/contract_spec.rb +3 -3
  431. data/spec/models/contracts_spec.rb +3 -3
  432. data/spec/models/cpu_architecture_properties_spec.rb +3 -3
  433. data/spec/models/data_center_entities_spec.rb +3 -3
  434. data/spec/models/datacenter_element_metadata_spec.rb +3 -3
  435. data/spec/models/datacenter_properties_spec.rb +3 -3
  436. data/spec/models/datacenter_spec.rb +3 -3
  437. data/spec/models/datacenters_spec.rb +3 -3
  438. data/spec/models/error_message_spec.rb +3 -3
  439. data/spec/models/error_spec.rb +3 -3
  440. data/spec/models/firewall_rule_spec.rb +3 -3
  441. data/spec/models/firewall_rules_spec.rb +3 -3
  442. data/spec/models/firewallrule_properties_spec.rb +3 -3
  443. data/spec/models/flow_log_properties_spec.rb +3 -3
  444. data/spec/models/flow_log_put_spec.rb +3 -3
  445. data/spec/models/flow_log_spec.rb +3 -3
  446. data/spec/models/flow_logs_spec.rb +3 -3
  447. data/spec/models/group_entities_spec.rb +3 -3
  448. data/spec/models/group_members_spec.rb +3 -3
  449. data/spec/models/group_properties_spec.rb +3 -3
  450. data/spec/models/group_share_properties_spec.rb +3 -3
  451. data/spec/models/group_share_spec.rb +3 -3
  452. data/spec/models/group_shares_spec.rb +3 -3
  453. data/spec/models/group_spec.rb +3 -3
  454. data/spec/models/group_users_spec.rb +3 -3
  455. data/spec/models/groups_spec.rb +3 -3
  456. data/spec/models/image_properties_spec.rb +4 -4
  457. data/spec/models/image_spec.rb +3 -3
  458. data/spec/models/images_spec.rb +3 -3
  459. data/spec/models/info_spec.rb +3 -3
  460. data/spec/models/ip_block_properties_spec.rb +3 -3
  461. data/spec/models/ip_block_spec.rb +3 -3
  462. data/spec/models/ip_blocks_spec.rb +21 -3
  463. data/spec/models/ip_consumer_spec.rb +3 -3
  464. data/spec/models/ip_failover_spec.rb +3 -3
  465. data/spec/models/kubernetes_auto_scaling_spec.rb +3 -3
  466. data/spec/models/kubernetes_cluster_entities_spec.rb +3 -3
  467. data/spec/models/kubernetes_cluster_for_post_spec.rb +3 -3
  468. data/spec/models/kubernetes_cluster_for_put_spec.rb +3 -3
  469. data/spec/models/kubernetes_cluster_properties_for_post_spec.rb +10 -4
  470. data/spec/models/kubernetes_cluster_properties_for_put_spec.rb +15 -3
  471. data/spec/models/kubernetes_cluster_properties_spec.rb +10 -4
  472. data/spec/models/kubernetes_cluster_spec.rb +3 -3
  473. data/spec/models/kubernetes_clusters_spec.rb +3 -3
  474. data/spec/models/kubernetes_maintenance_window_spec.rb +3 -3
  475. data/spec/models/kubernetes_node_metadata_spec.rb +3 -3
  476. data/spec/models/kubernetes_node_pool_for_post_spec.rb +3 -3
  477. data/spec/models/kubernetes_node_pool_for_put_spec.rb +3 -3
  478. data/spec/models/kubernetes_node_pool_lan_routes_spec.rb +3 -3
  479. data/spec/models/kubernetes_node_pool_lan_spec.rb +3 -3
  480. data/spec/models/kubernetes_node_pool_properties_for_post_spec.rb +9 -3
  481. data/spec/models/kubernetes_node_pool_properties_for_put_spec.rb +3 -3
  482. data/spec/models/kubernetes_node_pool_properties_spec.rb +9 -3
  483. data/spec/models/kubernetes_node_pool_spec.rb +3 -3
  484. data/spec/models/kubernetes_node_pools_spec.rb +3 -3
  485. data/spec/models/kubernetes_node_properties_spec.rb +3 -3
  486. data/spec/models/kubernetes_node_spec.rb +3 -3
  487. data/spec/models/kubernetes_nodes_spec.rb +3 -3
  488. data/spec/models/label_properties_spec.rb +3 -3
  489. data/spec/models/label_resource_properties_spec.rb +3 -3
  490. data/spec/models/label_resource_spec.rb +3 -3
  491. data/spec/models/label_resources_spec.rb +3 -3
  492. data/spec/models/label_spec.rb +3 -3
  493. data/spec/models/labels_spec.rb +3 -3
  494. data/spec/models/lan_entities_spec.rb +3 -3
  495. data/spec/models/lan_nics_spec.rb +3 -3
  496. data/spec/models/lan_post_spec.rb +3 -3
  497. data/spec/models/lan_properties_post_spec.rb +3 -3
  498. data/spec/models/lan_properties_spec.rb +3 -3
  499. data/spec/models/lan_spec.rb +3 -3
  500. data/spec/models/lans_spec.rb +3 -3
  501. data/spec/models/loadbalancer_entities_spec.rb +3 -3
  502. data/spec/models/loadbalancer_properties_spec.rb +3 -3
  503. data/spec/models/loadbalancer_spec.rb +3 -3
  504. data/spec/models/loadbalancers_spec.rb +3 -3
  505. data/spec/models/location_properties_spec.rb +3 -3
  506. data/spec/models/location_spec.rb +3 -3
  507. data/spec/models/locations_spec.rb +3 -3
  508. data/spec/models/nat_gateway_entities_spec.rb +3 -3
  509. data/spec/models/nat_gateway_lan_properties_spec.rb +3 -3
  510. data/spec/models/nat_gateway_properties_spec.rb +3 -3
  511. data/spec/models/nat_gateway_put_spec.rb +3 -3
  512. data/spec/models/nat_gateway_rule_properties_spec.rb +3 -3
  513. data/spec/models/nat_gateway_rule_protocol_spec.rb +3 -3
  514. data/spec/models/nat_gateway_rule_put_spec.rb +3 -3
  515. data/spec/models/nat_gateway_rule_spec.rb +3 -3
  516. data/spec/models/nat_gateway_rule_type_spec.rb +3 -3
  517. data/spec/models/nat_gateway_rules_spec.rb +3 -3
  518. data/spec/models/nat_gateway_spec.rb +3 -3
  519. data/spec/models/nat_gateways_spec.rb +3 -3
  520. data/spec/models/network_load_balancer_entities_spec.rb +3 -3
  521. data/spec/models/network_load_balancer_forwarding_rule_health_check_spec.rb +3 -9
  522. data/spec/models/network_load_balancer_forwarding_rule_properties_spec.rb +4 -4
  523. data/spec/models/network_load_balancer_forwarding_rule_put_spec.rb +3 -3
  524. data/spec/models/network_load_balancer_forwarding_rule_spec.rb +3 -3
  525. data/spec/models/network_load_balancer_forwarding_rule_target_health_check_spec.rb +3 -3
  526. data/spec/models/network_load_balancer_forwarding_rule_target_spec.rb +3 -3
  527. data/spec/models/network_load_balancer_forwarding_rules_spec.rb +3 -3
  528. data/spec/models/network_load_balancer_properties_spec.rb +3 -3
  529. data/spec/models/network_load_balancer_put_spec.rb +3 -3
  530. data/spec/models/network_load_balancer_spec.rb +3 -3
  531. data/spec/models/network_load_balancers_spec.rb +3 -3
  532. data/spec/models/nic_entities_spec.rb +3 -3
  533. data/spec/models/nic_properties_spec.rb +3 -3
  534. data/spec/models/nic_put_spec.rb +3 -3
  535. data/spec/models/nic_spec.rb +3 -3
  536. data/spec/models/nics_spec.rb +3 -3
  537. data/spec/models/no_state_meta_data_spec.rb +3 -3
  538. data/spec/models/pagination_links_spec.rb +3 -3
  539. data/spec/models/peer_spec.rb +3 -3
  540. data/spec/models/private_cross_connect_properties_spec.rb +3 -3
  541. data/spec/models/private_cross_connect_spec.rb +3 -3
  542. data/spec/models/private_cross_connects_spec.rb +3 -3
  543. data/spec/models/remote_console_url_spec.rb +3 -3
  544. data/spec/models/request_metadata_spec.rb +3 -3
  545. data/spec/models/request_properties_spec.rb +3 -3
  546. data/spec/models/request_spec.rb +3 -3
  547. data/spec/models/request_status_metadata_spec.rb +3 -3
  548. data/spec/models/request_status_spec.rb +3 -3
  549. data/spec/models/request_target_spec.rb +3 -3
  550. data/spec/models/requests_spec.rb +3 -3
  551. data/spec/models/resource_entities_spec.rb +3 -3
  552. data/spec/models/resource_groups_spec.rb +3 -3
  553. data/spec/models/resource_limits_spec.rb +3 -3
  554. data/spec/models/resource_properties_spec.rb +3 -3
  555. data/spec/models/resource_reference_spec.rb +3 -3
  556. data/spec/models/resource_spec.rb +3 -3
  557. data/spec/models/resources_spec.rb +3 -3
  558. data/spec/models/resources_users_spec.rb +3 -3
  559. data/spec/models/s3_bucket_spec.rb +34 -0
  560. data/spec/models/s3_key_metadata_spec.rb +3 -3
  561. data/spec/models/s3_key_properties_spec.rb +3 -3
  562. data/spec/models/s3_key_spec.rb +3 -3
  563. data/spec/models/s3_keys_spec.rb +3 -3
  564. data/spec/models/s3_object_storage_sso_spec.rb +3 -3
  565. data/spec/models/server_entities_spec.rb +3 -3
  566. data/spec/models/server_properties_spec.rb +3 -3
  567. data/spec/models/server_spec.rb +3 -3
  568. data/spec/models/servers_spec.rb +3 -3
  569. data/spec/models/snapshot_properties_spec.rb +3 -3
  570. data/spec/models/snapshot_spec.rb +3 -3
  571. data/spec/models/snapshots_spec.rb +3 -3
  572. data/spec/models/target_port_range_spec.rb +3 -3
  573. data/spec/models/template_properties_spec.rb +3 -3
  574. data/spec/models/template_spec.rb +3 -3
  575. data/spec/models/templates_spec.rb +3 -3
  576. data/spec/models/token_spec.rb +3 -3
  577. data/spec/models/type_spec.rb +3 -3
  578. data/spec/models/user_metadata_spec.rb +3 -3
  579. data/spec/models/user_post_spec.rb +3 -3
  580. data/spec/models/user_properties_post_spec.rb +3 -3
  581. data/spec/models/user_properties_put_spec.rb +3 -3
  582. data/spec/models/user_properties_spec.rb +3 -3
  583. data/spec/models/user_put_spec.rb +3 -3
  584. data/spec/models/user_spec.rb +3 -3
  585. data/spec/models/users_entities_spec.rb +3 -3
  586. data/spec/models/users_spec.rb +21 -3
  587. data/spec/models/volume_properties_spec.rb +11 -5
  588. data/spec/models/volume_spec.rb +3 -3
  589. data/spec/models/volumes_spec.rb +3 -3
  590. data/spec/spec_helper.rb +3 -3
  591. metadata +368 -364
  592. data/docs/DataCentersApi.md +0 -516
  593. data/docs/DefaultApi.md +0 -78
  594. data/docs/Users.md +0 -24
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -35,12 +35,12 @@ describe 'VolumesApi' do
35
35
  # unit tests for datacenters_volumes_create_snapshot_post
36
36
  # Create Volume Snapshot
37
37
  # Creates a snapshot of a volume within the datacenter. You can use a snapshot to create a new storage volume or to restore a storage volume.
38
- # @param datacenter_id The unique ID of the datacenter
38
+ # @param datacenter_id The unique ID of the data center.
39
39
  # @param volume_id The unique ID of the Volume
40
40
  # @param [Hash] opts the optional parameters
41
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
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
- # @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
41
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
42
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
43
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
44
44
  # @option opts [String] :name The name of the snapshot
45
45
  # @option opts [String] :description The description of the snapshot
46
46
  # @option opts [Boolean] :sec_auth_protection Flag representing if extra protection is enabled on snapshot e.g. Two Factor protection etc.
@@ -55,12 +55,12 @@ describe 'VolumesApi' do
55
55
  # unit tests for datacenters_volumes_delete
56
56
  # Delete a Volume
57
57
  # Deletes the specified volume. This will result in the volume being removed from your datacenter. Use this with caution.
58
- # @param datacenter_id The unique ID of the datacenter
58
+ # @param datacenter_id The unique ID of the data center.
59
59
  # @param volume_id The unique ID of the Volume
60
60
  # @param [Hash] opts the optional parameters
61
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
62
- # @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
63
- # @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
61
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
62
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
63
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
64
64
  # @return [nil]
65
65
  describe 'datacenters_volumes_delete test' do
66
66
  it 'should work' do
@@ -71,12 +71,12 @@ describe 'VolumesApi' do
71
71
  # unit tests for datacenters_volumes_find_by_id
72
72
  # Retrieve a Volume
73
73
  # Retrieves the attributes of a given Volume
74
- # @param datacenter_id The unique ID of the datacenter
74
+ # @param datacenter_id The unique ID of the data center.
75
75
  # @param volume_id The unique ID of the Volume
76
76
  # @param [Hash] opts the optional parameters
77
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
78
- # @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
79
- # @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
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
78
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
79
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
80
80
  # @return [Volume]
81
81
  describe 'datacenters_volumes_find_by_id test' do
82
82
  it 'should work' do
@@ -87,13 +87,13 @@ describe 'VolumesApi' do
87
87
  # unit tests for datacenters_volumes_get
88
88
  # List Volumes
89
89
  # Retrieves a list of Volumes.
90
- # @param datacenter_id The unique ID of the datacenter
90
+ # @param datacenter_id The unique ID of the data center.
91
91
  # @param [Hash] opts the optional parameters
92
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
93
- # @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
94
- # @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
95
- # @option opts [Integer] :offset the first element (of the total list of elements) to include in the response (use together with limit for pagination)
96
- # @option opts [Integer] :limit the maximum number of elements to return (use together with offset for pagination)
92
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
93
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
94
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
95
+ # @option opts [Integer] :offset The first element (from the complete list of the elements) to include in the response (use together with limit for pagination).
96
+ # @option opts [Integer] :limit The maximum number of elements to return (use together with offset for pagination).
97
97
  # @return [Volumes]
98
98
  describe 'datacenters_volumes_get test' do
99
99
  it 'should work' do
@@ -104,13 +104,13 @@ describe 'VolumesApi' do
104
104
  # unit tests for datacenters_volumes_patch
105
105
  # Partially modify a Volume
106
106
  # You can use update attributes of a volume.
107
- # @param datacenter_id The unique ID of the datacenter
107
+ # @param datacenter_id The unique ID of the data center.
108
108
  # @param volume_id The unique ID of the Volume
109
109
  # @param volume Modified properties of Volume
110
110
  # @param [Hash] opts the optional parameters
111
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
112
- # @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
113
- # @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
111
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
112
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
113
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
114
114
  # @return [Volume]
115
115
  describe 'datacenters_volumes_patch test' do
116
116
  it 'should work' do
@@ -121,12 +121,12 @@ describe 'VolumesApi' do
121
121
  # unit tests for datacenters_volumes_post
122
122
  # Create a Volume
123
123
  # Creates a volume within the datacenter. This will not attach the volume to a server. Please see the Servers section for details on how to attach storage volumes
124
- # @param datacenter_id The unique ID of the datacenter
124
+ # @param datacenter_id The unique ID of the data center.
125
125
  # @param volume Volume to be created
126
126
  # @param [Hash] opts the optional parameters
127
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
128
- # @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
129
- # @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
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
128
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
129
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
130
130
  # @return [Volume]
131
131
  describe 'datacenters_volumes_post test' do
132
132
  it 'should work' do
@@ -137,13 +137,13 @@ describe 'VolumesApi' do
137
137
  # unit tests for datacenters_volumes_put
138
138
  # Modify a Volume
139
139
  # You can use update attributes of a Volume
140
- # @param datacenter_id The unique ID of the datacenter
140
+ # @param datacenter_id The unique ID of the data center.
141
141
  # @param volume_id The unique ID of the Volume
142
142
  # @param volume Modified Volume
143
143
  # @param [Hash] opts the optional parameters
144
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
145
- # @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
146
- # @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
144
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
145
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
146
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
147
147
  # @return [Volume]
148
148
  describe 'datacenters_volumes_put test' do
149
149
  it 'should work' do
@@ -154,12 +154,12 @@ describe 'VolumesApi' do
154
154
  # unit tests for datacenters_volumes_restore_snapshot_post
155
155
  # Restore Volume Snapshot
156
156
  # This will restore a snapshot onto a volume. A snapshot is created as just another image that can be used to create subsequent volumes if you want or to restore an existing volume.
157
- # @param datacenter_id The unique ID of the datacenter
157
+ # @param datacenter_id The unique ID of the data center.
158
158
  # @param volume_id The unique ID of the Volume
159
159
  # @param [Hash] opts the optional parameters
160
- # @option opts [Boolean] :pretty Controls whether response is pretty-printed (with indentation and new lines)
161
- # @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
162
- # @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
160
+ # @option opts [Boolean] :pretty Controls whether the response is pretty-printed (with indentations and new lines).
161
+ # @option opts [Integer] :depth Controls the detail depth of the response objects. GET /datacenters/[ID] - depth=0: Only direct properties are included; children (servers and other elements) are not included. - depth=1: Direct properties and children references are included. - depth=2: Direct properties and children properties are included. - depth=3: Direct properties and children properties and children's children are included. - depth=... and so on
162
+ # @option opts [Integer] :x_contract_number Users with multiple contracts must provide the contract number, against which all API requests are to be executed.
163
163
  # @option opts [String] :snapshot_id This is the ID of the snapshot
164
164
  # @return [nil]
165
165
  describe 'datacenters_volumes_restore_snapshot_post test' do
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12
 
@@ -1,12 +1,12 @@
1
1
  =begin
2
2
  #CLOUD API
3
3
 
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.
4
+ #IONOS Enterprise-grade Infrastructure as a Service (IaaS) solutions can be managed through the Cloud API, in addition or as an alternative to the \"Data Center Designer\" (DCD) browser-based tool. Both methods employ consistent concepts and features, deliver similar power and flexibility, and can be used to perform a multitude of management tasks, including adding servers, volumes, configuring networks, and so on.
5
5
 
6
- The version of the OpenAPI document: 6.0-SDK.1
6
+ The version of the OpenAPI document: 6.0-SDK.3
7
7
 
8
8
  Generated by: https://openapi-generator.tech
9
- OpenAPI Generator version: 5.0.1-SNAPSHOT
9
+ OpenAPI Generator version: 5.2.1-SNAPSHOT
10
10
 
11
11
  =end
12
12