chore(updater): bump pkg/dist/*.yml (2024-09-12)

pkg/dist/integration_endpoint_types.yml

@@ -37,6 +37,7 @@ datadog:
       pattern: ^[A-Za-z0-9]{1,256}$
       example: 848f30907c15c55d601fe45487cce9b6
       user_error: Must consist of up to 256 alpha-numeric characters
+      _secure: true
     datadog_tags:
       title: Custom tags provided by user
       type: array
@@ -133,6 +134,7 @@ external_aws_cloudwatch_logs:
       type: string
       max_length: 4096
       example: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+      _secure: true
 external_aws_cloudwatch_metrics:
   type: object
   required:
@@ -163,6 +165,7 @@ external_aws_cloudwatch_metrics:
       type: string
       max_length: 4096
       example: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+      _secure: true
 external_aws_s3:
   type: object
   required:
@@ -334,6 +337,7 @@ external_kafka:
       min_length: 1
       max_length: 256
       example: admin
+      _secure: true
     sasl_plain_username:
       title: Username for SASL PLAIN mechanism in the Kafka server.
       type:
@@ -581,6 +585,7 @@ external_schema_registry:
         - "null"
       max_length: 256
       example: Zm9vYg==
+      _secure: true
     basic_auth_username:
       title: Basic authentication user name
       type:
@@ -602,6 +607,7 @@ jolokia:
       min_length: 8
       max_length: 64
       example: yhfBNFii4C
+      _secure: true
     basic_auth_username:
       title: Jolokia basic authentication username
       type: string
@@ -619,6 +625,7 @@ prometheus:
       min_length: 8
       max_length: 64
       example: fhyFNBjj3R
+      _secure: true
     basic_auth_username:
       title: Prometheus basic authentication username
       type: string

pkg/dist/integration_types.yml

@@ -462,6 +462,9 @@ flink_external_bigquery:
 flink_external_kafka:
   title: Integration user config
   type: object
+flink_external_postgresql:
+  title: Integration user config
+  type: object
 jolokia:
   title: Integration user config
   type: object

pkg/dist/service_types.yml

@@ -1339,6 +1339,10 @@ grafana:
           type: string
           max_length: 2048
           example: https://yourprovider.com/oauth/token
+        use_refresh_token:
+          title: Set to true to use refresh token and check access token expiration.
+          type: boolean
+          example: true
     auth_github:
       title: Github Auth integration
       type: object
@@ -1626,6 +1630,7 @@ grafana:
           max_length: 4096
           pattern: ^[A-Za-z0-9/+=]+$
           example: AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
+          _secure: true
     google_analytics_ua_id:
       title: Google Analytics ID
       type: string
@@ -1758,6 +1763,7 @@ grafana:
           max_length: 255
           pattern: ^[^\x00-\x1F]+$
           example: ein0eemeev5eeth3Ahfu
+          _secure: true
         port:
           title: SMTP server port
           type: integer
@@ -2748,6 +2754,16 @@ kafka:
           description: If true, Karapace / Schema Registry on the service nodes can participate in leader election. It might be needed to disable this when the schemas topic is replicated to a secondary cluster and Karapace / Schema Registry there must not participate in leader election. Defaults to `true`.
           type: boolean
           example: true
+        retriable_errors_silenced:
+          title: retriable_errors_silenced
+          description: If enabled, kafka errors which can be retried or custom errors specified for the service will not be raised, instead, a warning log is emitted. This will denoise issue tracking systems, i.e. sentry. Defaults to `true`.
+          type: boolean
+          example: true
+        schema_reader_strict_mode:
+          title: schema_reader_strict_mode
+          description: If enabled, causes the Karapace schema-registry service to shutdown when there are invalid schema records in the `_schemas` topic. Defaults to `false`.
+          type: boolean
+          example: false
         topic_name:
           title: topic_name
           description: The durable single partition topic that acts as the durable log for the data. This topic must be compacted to avoid losing data due to retention policy. Please note that changing this configuration in an existing Schema Registry / Karapace setup leads to previous schemas being inaccessible, data encoded with them potentially unreadable and schema ID sequence put out of order. It's only possible to do the switch while Schema Registry / Karapace is disabled. Defaults to `_schemas`.
@@ -3695,6 +3711,7 @@ mysql:
       pattern: ^[a-zA-Z0-9-_]+$
       example: z66o9QXqKM
       user_error: Must consist of alpha-numeric characters, underscores or dashes
+      _secure: true
     admin_username:
       title: Custom username for admin user. This must be set only when a new service is being created.
       type:
@@ -5004,6 +5021,7 @@ opensearch:
           description: AWS secret key
           type: string
           pattern: ^[^\r\n]*$
+          _secure: true
         server_side_encryption:
           title: Server side encryption
           description: When set to true files are encrypted on server side
@@ -5130,6 +5148,7 @@ pg:
       pattern: ^[a-zA-Z0-9-_]+$
       example: z66o9QXqKM
       user_error: Must consist of alpha-numeric characters, underscores or dashes
+      _secure: true
     admin_username:
       title: Custom username for admin user. This must be set only when a new service is being created.
       type: