build(deps): bump github.com/aiven/go-api-schemas from 1.59.0 to 1.60…

….0 (#648)

charts/aiven-operator-crds/templates/aiven.io_kafkaconnects.yaml

@@ -329,7 +329,7 @@ spec:
                             to wait for the return of one or more departed workers before
                             rebalancing and reassigning their connectors and tasks to
                             the group. During this period the connectors and tasks of
-                            the departed workers remain unassigned.  Defaults to 5 minutes.
+                            the departed workers remain unassigned. Defaults to 5 minutes.
                           maximum: 600000
                           minimum: 0
                           type: integer

charts/aiven-operator-crds/templates/aiven.io_kafkas.yaml

@@ -753,7 +753,7 @@ spec:
                             to wait for the return of one or more departed workers before
                             rebalancing and reassigning their connectors and tasks to
                             the group. During this period the connectors and tasks of
-                            the departed workers remain unassigned.  Defaults to 5 minutes.
+                            the departed workers remain unassigned. Defaults to 5 minutes.
                           maximum: 600000
                           minimum: 0
                           type: integer

charts/aiven-operator-crds/templates/aiven.io_mysqls.yaml

@@ -394,8 +394,8 @@ spec:
                             "Specifies whether flushing a page from the InnoDB
                             buffer pool also flushes other dirty pages in the same extent
                             (default is 1): 0 - dirty pages in the same extent are not
-                            flushed,  1 - flush contiguous dirty pages in the same extent,  2
-                            - flush dirty pages in the same extent"
+                            flushed, 1 - flush contiguous dirty pages in the same extent,
+                            2 - flush dirty pages in the same extent"
                           maximum: 2
                           minimum: 0
                           type: integer

charts/aiven-operator-crds/templates/aiven.io_postgresqls.yaml

@@ -361,7 +361,7 @@ spec:
                         autovacuum_analyze_threshold:
                           description:
                             Specifies the minimum number of inserted, updated
-                            or deleted tuples needed to trigger an  ANALYZE in any one
+                            or deleted tuples needed to trigger an ANALYZE in any one
                             table. The default is 50 tuples.
                           maximum: 2147483647
                           minimum: 0

config/crd/bases/aiven.io_kafkaconnects.yaml

@@ -329,7 +329,7 @@ spec:
                             to wait for the return of one or more departed workers before
                             rebalancing and reassigning their connectors and tasks to
                             the group. During this period the connectors and tasks of
-                            the departed workers remain unassigned.  Defaults to 5 minutes.
+                            the departed workers remain unassigned. Defaults to 5 minutes.
                           maximum: 600000
                           minimum: 0
                           type: integer

config/crd/bases/aiven.io_kafkas.yaml

@@ -753,7 +753,7 @@ spec:
                             to wait for the return of one or more departed workers before
                             rebalancing and reassigning their connectors and tasks to
                             the group. During this period the connectors and tasks of
-                            the departed workers remain unassigned.  Defaults to 5 minutes.
+                            the departed workers remain unassigned. Defaults to 5 minutes.
                           maximum: 600000
                           minimum: 0
                           type: integer

config/crd/bases/aiven.io_mysqls.yaml

@@ -394,8 +394,8 @@ spec:
                             "Specifies whether flushing a page from the InnoDB
                             buffer pool also flushes other dirty pages in the same extent
                             (default is 1): 0 - dirty pages in the same extent are not
-                            flushed,  1 - flush contiguous dirty pages in the same extent,  2
-                            - flush dirty pages in the same extent"
+                            flushed, 1 - flush contiguous dirty pages in the same extent,
+                            2 - flush dirty pages in the same extent"
                           maximum: 2
                           minimum: 0
                           type: integer

config/crd/bases/aiven.io_postgresqls.yaml

@@ -361,7 +361,7 @@ spec:
                         autovacuum_analyze_threshold:
                           description:
                             Specifies the minimum number of inserted, updated
-                            or deleted tuples needed to trigger an  ANALYZE in any one
+                            or deleted tuples needed to trigger an ANALYZE in any one
                             table. The default is 50 tuples.
                           maximum: 2147483647
                           minimum: 0

docs/docs/api-reference/kafka.md

@@ -263,7 +263,7 @@ Kafka Connect configuration values.
 - [`producer_compression_type`](#spec.userConfig.kafka_connect_config.producer_compression_type-property){: name='spec.userConfig.kafka_connect_config.producer_compression_type-property'} (string, Enum: `gzip`, `snappy`, `lz4`, `zstd`, `none`). Specify the default compression type for producers. This configuration accepts the standard compression codecs (`gzip`, `snappy`, `lz4`, `zstd`). It additionally accepts `none` which is the default and equivalent to no compression.
 - [`producer_linger_ms`](#spec.userConfig.kafka_connect_config.producer_linger_ms-property){: name='spec.userConfig.kafka_connect_config.producer_linger_ms-property'} (integer, Minimum: 0, Maximum: 5000). This setting gives the upper bound on the delay for batching: once there is batch.size worth of records for a partition it will be sent immediately regardless of this setting, however if there are fewer than this many bytes accumulated for this partition the producer will `linger` for the specified time waiting for more records to show up. Defaults to 0.
 - [`producer_max_request_size`](#spec.userConfig.kafka_connect_config.producer_max_request_size-property){: name='spec.userConfig.kafka_connect_config.producer_max_request_size-property'} (integer, Minimum: 131072, Maximum: 67108864). This setting will limit the number of record batches the producer will send in a single request to avoid sending huge requests.
-- [`scheduled_rebalance_max_delay_ms`](#spec.userConfig.kafka_connect_config.scheduled_rebalance_max_delay_ms-property){: name='spec.userConfig.kafka_connect_config.scheduled_rebalance_max_delay_ms-property'} (integer, Minimum: 0, Maximum: 600000). The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned.  Defaults to 5 minutes.
+- [`scheduled_rebalance_max_delay_ms`](#spec.userConfig.kafka_connect_config.scheduled_rebalance_max_delay_ms-property){: name='spec.userConfig.kafka_connect_config.scheduled_rebalance_max_delay_ms-property'} (integer, Minimum: 0, Maximum: 600000). The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned. Defaults to 5 minutes.
 - [`session_timeout_ms`](#spec.userConfig.kafka_connect_config.session_timeout_ms-property){: name='spec.userConfig.kafka_connect_config.session_timeout_ms-property'} (integer, Minimum: 1, Maximum: 2147483647). The timeout in milliseconds used to detect failures when using Kafka’s group management facilities (defaults to 10000).
 
 ### kafka_rest_config {: #spec.userConfig.kafka_rest_config }

docs/docs/api-reference/kafkaconnect.md

@@ -160,7 +160,7 @@ Kafka Connect configuration values.
 - [`producer_compression_type`](#spec.userConfig.kafka_connect.producer_compression_type-property){: name='spec.userConfig.kafka_connect.producer_compression_type-property'} (string, Enum: `gzip`, `snappy`, `lz4`, `zstd`, `none`). Specify the default compression type for producers. This configuration accepts the standard compression codecs (`gzip`, `snappy`, `lz4`, `zstd`). It additionally accepts `none` which is the default and equivalent to no compression.
 - [`producer_linger_ms`](#spec.userConfig.kafka_connect.producer_linger_ms-property){: name='spec.userConfig.kafka_connect.producer_linger_ms-property'} (integer, Minimum: 0, Maximum: 5000). This setting gives the upper bound on the delay for batching: once there is batch.size worth of records for a partition it will be sent immediately regardless of this setting, however if there are fewer than this many bytes accumulated for this partition the producer will `linger` for the specified time waiting for more records to show up. Defaults to 0.
 - [`producer_max_request_size`](#spec.userConfig.kafka_connect.producer_max_request_size-property){: name='spec.userConfig.kafka_connect.producer_max_request_size-property'} (integer, Minimum: 131072, Maximum: 67108864). This setting will limit the number of record batches the producer will send in a single request to avoid sending huge requests.
-- [`scheduled_rebalance_max_delay_ms`](#spec.userConfig.kafka_connect.scheduled_rebalance_max_delay_ms-property){: name='spec.userConfig.kafka_connect.scheduled_rebalance_max_delay_ms-property'} (integer, Minimum: 0, Maximum: 600000). The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned.  Defaults to 5 minutes.
+- [`scheduled_rebalance_max_delay_ms`](#spec.userConfig.kafka_connect.scheduled_rebalance_max_delay_ms-property){: name='spec.userConfig.kafka_connect.scheduled_rebalance_max_delay_ms-property'} (integer, Minimum: 0, Maximum: 600000). The maximum delay that is scheduled in order to wait for the return of one or more departed workers before rebalancing and reassigning their connectors and tasks to the group. During this period the connectors and tasks of the departed workers remain unassigned. Defaults to 5 minutes.
 - [`session_timeout_ms`](#spec.userConfig.kafka_connect.session_timeout_ms-property){: name='spec.userConfig.kafka_connect.session_timeout_ms-property'} (integer, Minimum: 1, Maximum: 2147483647). The timeout in milliseconds used to detect failures when using Kafka’s group management facilities (defaults to 10000).
 
 ### private_access {: #spec.userConfig.private_access }

docs/docs/api-reference/mysql.md

@@ -213,7 +213,7 @@ mysql.conf configuration values.
 - [`group_concat_max_len`](#spec.userConfig.mysql.group_concat_max_len-property){: name='spec.userConfig.mysql.group_concat_max_len-property'} (integer, Minimum: 4). The maximum permitted result length in bytes for the GROUP_CONCAT() function.
 - [`information_schema_stats_expiry`](#spec.userConfig.mysql.information_schema_stats_expiry-property){: name='spec.userConfig.mysql.information_schema_stats_expiry-property'} (integer, Minimum: 900, Maximum: 31536000). The time, in seconds, before cached statistics expire.
 - [`innodb_change_buffer_max_size`](#spec.userConfig.mysql.innodb_change_buffer_max_size-property){: name='spec.userConfig.mysql.innodb_change_buffer_max_size-property'} (integer, Minimum: 0, Maximum: 50). Maximum size for the InnoDB change buffer, as a percentage of the total size of the buffer pool. Default is 25.
-- [`innodb_flush_neighbors`](#spec.userConfig.mysql.innodb_flush_neighbors-property){: name='spec.userConfig.mysql.innodb_flush_neighbors-property'} (integer, Minimum: 0, Maximum: 2). Specifies whether flushing a page from the InnoDB buffer pool also flushes other dirty pages in the same extent (default is 1): 0 - dirty pages in the same extent are not flushed,  1 - flush contiguous dirty pages in the same extent,  2 - flush dirty pages in the same extent.
+- [`innodb_flush_neighbors`](#spec.userConfig.mysql.innodb_flush_neighbors-property){: name='spec.userConfig.mysql.innodb_flush_neighbors-property'} (integer, Minimum: 0, Maximum: 2). Specifies whether flushing a page from the InnoDB buffer pool also flushes other dirty pages in the same extent (default is 1): 0 - dirty pages in the same extent are not flushed, 1 - flush contiguous dirty pages in the same extent, 2 - flush dirty pages in the same extent.
 - [`innodb_ft_min_token_size`](#spec.userConfig.mysql.innodb_ft_min_token_size-property){: name='spec.userConfig.mysql.innodb_ft_min_token_size-property'} (integer, Minimum: 0, Maximum: 16). Minimum length of words that are stored in an InnoDB FULLTEXT index. Changing this parameter will lead to a restart of the MySQL service.
 - [`innodb_ft_server_stopword_table`](#spec.userConfig.mysql.innodb_ft_server_stopword_table-property){: name='spec.userConfig.mysql.innodb_ft_server_stopword_table-property'} (string, Pattern: `^.+/.+$`, MaxLength: 1024). This option is used to specify your own InnoDB FULLTEXT index stopword list for all InnoDB tables.
 - [`innodb_lock_wait_timeout`](#spec.userConfig.mysql.innodb_lock_wait_timeout-property){: name='spec.userConfig.mysql.innodb_lock_wait_timeout-property'} (integer, Minimum: 1, Maximum: 3600). The length of time in seconds an InnoDB transaction waits for a row lock before giving up. Default is 120.

docs/docs/api-reference/postgresql.md

@@ -215,7 +215,7 @@ postgresql.conf configuration values.
 **Optional**
 
 - [`autovacuum_analyze_scale_factor`](#spec.userConfig.pg.autovacuum_analyze_scale_factor-property){: name='spec.userConfig.pg.autovacuum_analyze_scale_factor-property'} (number, Minimum: 0, Maximum: 1). Specifies a fraction of the table size to add to autovacuum_analyze_threshold when deciding whether to trigger an ANALYZE. The default is 0.2 (20% of table size).
-- [`autovacuum_analyze_threshold`](#spec.userConfig.pg.autovacuum_analyze_threshold-property){: name='spec.userConfig.pg.autovacuum_analyze_threshold-property'} (integer, Minimum: 0, Maximum: 2147483647). Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an  ANALYZE in any one table. The default is 50 tuples.
+- [`autovacuum_analyze_threshold`](#spec.userConfig.pg.autovacuum_analyze_threshold-property){: name='spec.userConfig.pg.autovacuum_analyze_threshold-property'} (integer, Minimum: 0, Maximum: 2147483647). Specifies the minimum number of inserted, updated or deleted tuples needed to trigger an ANALYZE in any one table. The default is 50 tuples.
 - [`autovacuum_freeze_max_age`](#spec.userConfig.pg.autovacuum_freeze_max_age-property){: name='spec.userConfig.pg.autovacuum_freeze_max_age-property'} (integer, Minimum: 200000000, Maximum: 1500000000). Specifies the maximum age (in transactions) that a table's pg_class.relfrozenxid field can attain before a VACUUM operation is forced to prevent transaction ID wraparound within the table. Note that the system will launch autovacuum processes to prevent wraparound even when autovacuum is otherwise disabled. This parameter will cause the server to be restarted.
 - [`autovacuum_max_workers`](#spec.userConfig.pg.autovacuum_max_workers-property){: name='spec.userConfig.pg.autovacuum_max_workers-property'} (integer, Minimum: 1, Maximum: 20). Specifies the maximum number of autovacuum processes (other than the autovacuum launcher) that may be running at any one time. The default is three. This parameter can only be set at server start.
 - [`autovacuum_naptime`](#spec.userConfig.pg.autovacuum_naptime-property){: name='spec.userConfig.pg.autovacuum_naptime-property'} (integer, Minimum: 1, Maximum: 86400). Specifies the minimum delay between autovacuum runs on any given database. The delay is measured in seconds, and the default is one minute.

go.mod

@@ -4,7 +4,7 @@ go 1.21
 
 require (
 	github.com/aiven/aiven-go-client/v2 v2.12.0
-	github.com/aiven/go-api-schemas v1.59.0
+	github.com/aiven/go-api-schemas v1.60.0
 	github.com/aiven/go-client-codegen v0.1.0
 	github.com/dave/jennifer v1.7.0
 	github.com/docker/go-units v0.5.0

go.sum

@@ -35,8 +35,8 @@ github.com/BurntSushi/toml v0.3.1/go.mod h1:xHWCNGjB5oqiDr8zfno3MHue2Ht5sIBksp03
 github.com/BurntSushi/xgb v0.0.0-20160522181843-27f122750802/go.mod h1:IVnqGOEym/WlBOVXweHU+Q+/VP0lqqI8lqeDx9IjBqo=
 github.com/aiven/aiven-go-client/v2 v2.12.0 h1:VxOfn61AtfLjy2B+DdXF2/7OHyyFZ1aQaIlE3TOyIsE=
 github.com/aiven/aiven-go-client/v2 v2.12.0/go.mod h1:x0xhzxWEKAwKv0xY5FvECiI6tesWshcPHvjwl0B/1SU=
-github.com/aiven/go-api-schemas v1.59.0 h1:DEH5KuxCpdtIxcnBubwf/svjExE1KK3DbQHT+tb5aeU=
-github.com/aiven/go-api-schemas v1.59.0/go.mod h1:/bPxBUHza/2Aeer6hIIdB++GxKiw9K1KCBtRa2rtZ5I=
+github.com/aiven/go-api-schemas v1.60.0 h1:R5p3V028HX2BLayO2E24SFs0GehJWTfo7L/vfrTa72Y=
+github.com/aiven/go-api-schemas v1.60.0/go.mod h1:/bPxBUHza/2Aeer6hIIdB++GxKiw9K1KCBtRa2rtZ5I=
 github.com/aiven/go-client-codegen v0.1.0 h1:MWBiyQ4gC/SVBvUa4vYqH/6evA2D6/sqAgpJSBU98Ao=
 github.com/aiven/go-client-codegen v0.1.0/go.mod h1:qQ5dwRfNnGS4eAYk7JdC5htQI85g7eA/e71ZLyY8pQw=
 github.com/alecthomas/template v0.0.0-20160405071501-a0175ee3bccc/go.mod h1:LOuyumcjzFXgccqObfd/Ljyb9UuFJ6TxHnclSeseNhc=