DOC-1046 Add arguments field to amqp_09 input and output (#178)

Author: asimms41

DOC-1046_Add_arguments_field

@@ -21,13 +21,13 @@ Common::
 --
 
 ```yml
-# Common config fields, showing default values
+# Common configuration fields, showing default values
 input:
   label: ""
   amqp_0_9:
     urls: [] # No default (required)
     queue: "" # No default (required)
-    consumer_tag: ""
+    consumer_tag: "" # Optional
     prefetch_count: 10
 ```
 
@@ -37,7 +37,7 @@ Advanced::
 --
 
 ```yml
-# All config fields, showing default values
+# All configuration fields, showing default values
 input:
   label: ""
   amqp_0_9:
@@ -47,8 +47,9 @@ input:
       enabled: false
       durable: true
       auto_delete: false
+      arguments: {} # No default (optional)
     bindings_declare: [] # No default (optional)
-    consumer_tag: ""
+    consumer_tag: "" # Optional
     auto_ack: false
     nack_reject_patterns: []
     prefetch_count: 10
@@ -57,37 +58,37 @@ input:
       enabled: false
       skip_cert_verify: false
       enable_renegotiation: false
-      root_cas: ""
-      root_cas_file: ""
+      root_cas: "" # Optional
+      root_cas_file: "" # Optional
       client_certs: []
 ```
 
 --
 ======
 
-TLS is automatic when connecting to an `amqps` URL, but custom settings can be enabled in the `tls` section.
+TLS is automatically enabled when connecting to an `amqps` URL. However, you can customize <<tls, TLS settings>> if required.
 
 == Metadata
 
 This input adds the following metadata fields to each message:
 
-- amqp_content_type
-- amqp_content_encoding
-- amqp_delivery_mode
-- amqp_priority
-- amqp_correlation_id
-- amqp_reply_to
-- amqp_expiration
-- amqp_message_id
-- amqp_timestamp
-- amqp_type
-- amqp_user_id
-- amqp_app_id
-- amqp_consumer_tag
-- amqp_delivery_tag
-- amqp_redelivered
-- amqp_exchange
-- amqp_routing_key
+- `amqp_content_type`
+- `amqp_content_encoding`
+- `amqp_delivery_mode`
+- `amqp_priority`
+- `amqp_correlation_id`
+- `amqp_reply_to`
+- `amqp_expiration`
+- `amqp_message_id`
+- `amqp_timestamp`
+- `amqp_type`
+- `amqp_user_id`
+- `amqp_app_id`
+- `amqp_consumer_tag`
+- `amqp_delivery_tag`
+- `amqp_redelivered`
+- `amqp_exchange`
+- `amqp_routing_key`
 - All existing message headers, including nested headers prefixed with the key of their respective parent.
 
 You can access these metadata fields using xref:configuration:interpolation.adoc#bloblang-queries[function interpolations].
@@ -96,8 +97,9 @@ You can access these metadata fields using xref:configuration:interpolation.adoc
 
 === `urls`
 
-A list of URLs to connect to. The first URL to successfully establish a connection will be used until the connection is closed. If an item of the list contains commas it will be expanded into multiple URLs.
+A list of URLs to connect to. This input attempts to connect to each URL in the list, in order, until a successful connection is established. It then continues to use that URL until the connection is closed.
 
+If an item in the list contains commas, it is split into multiple URLs.
 
 *Type*: `array`
 
@@ -129,17 +131,14 @@ An AMQP queue to consume from.
 
 === `queue_declare`
 
-Allows you to passively declare the target queue. If the queue already exists then the declaration passively verifies that they match the target fields.
-
+Passively declares the <<queue, target queue>> to make sure a queue with the specified name exists and is configured correctly. If the queue exists, then the passive declaration verifies that fields specified in this object match the its properties.
 
 *Type*: `object`
 
-
 === `queue_declare.enabled`
 
 Whether to enable queue declaration.
 
-
 *Type*: `bool`
 
 *Default*: `false`
@@ -148,34 +147,96 @@ Whether to enable queue declaration.
 
 Whether the declared queue is durable.
 
-
 *Type*: `bool`
 
 *Default*: `true`
 
 === `queue_declare.auto_delete`
 
-Whether the declared queue will auto-delete.
-
+Whether the declared queue auto-deletes when there are no active consumers.
 
 *Type*: `bool`
 
 *Default*: `false`
 
-=== `bindings_declare`
+=== `queue_declare.arguments`
 
-Allows you to passively declare bindings for the target queue.
+Arguments for server-specific implementations of the queue (optional). You can use arguments to configure additional parameters for queue types that require them. For more information about available arguments, see the https://github.com/rabbitmq/amqp091-go/blob/b3d409fe92c34bea04d8123a136384c85e8dc431/types.go#L282-L362[RabbitMQ Client Library^].
 
+*Type*: `object`
 
-*Type*: `array`
 
+```yml
+# Examples
+
+arguments:
+  x-max-length: 1000
+  x-max-length-bytes: 4096
+  x-queue-type: quorum
+```
+
+
+|===
+| Argument | Description | Accepted values
+
+| `x-queue-type`
+| Declares the type of queue.
+| Options: `classic` (default), `quorum`, `stream`, `drop-head`, `reject-publish`, and `reject-publish-dlx`.
+
+| `x-max-length`
+| The maximum number of messages in the queue.
+| A non-negative integer.
+
+| `x-max-length-bytes`
+| The maximum size of messages (in bytes) in the queue.
+| A non-negative integer.
+
+| `x-overflow`
+| Sets the queue's overflow behavior.
+| Options: `drop-head` (default), `reject-publish`, `reject-publish-dlx`.
+
+| `x-message-ttl`
+| The duration (in milliseconds) that messages remain in the queue before they expire and are discarded.
+| A string that represents the number of milliseconds. For example, `60000` retains messages for one minute.
+
+| `x-expires`
+| The duration after which the queue automatically expires.
+| A positive integer.
+
+| `x-max-age`
+| The duration (in configurable units) that streamed messages are retained on disk before they are discarded. 
+| Options: `Y`, `M`, `D`, `h`, `m`, `s`. For example, `7D` retains messages for a week.
+
+| `x-stream-max-segment-size-bytes`
+| The maximum size (in bytes) of the segment files held on disk.
+| A positive integer. Default: `500000000` (approximately 500 MB).
+
+| `x-queue-version`
+| The version of the classic queue to use.
+| Options: `1` or `2`.
+
+| `x-consumer-timeout`
+| The duration (in milliseconds) that a consumer can remain idle before it is automatically canceled.
+| A positive integer that represents the number of milliseconds. For example, `60000` sets a timeout duration of one minute.
+
+| `x-single-active-consumer`
+| When set to `true`, a single consumer receives messages from the queue even when multiple consumers are subscribed to it.
+| A boolean.
+
+|===
+
+=== `bindings_declare`
+
+Passively declares the bindings of the target queue to make sure they exist and are configured correctly. If the bindings exist, then the passive declaration verifies that fields specified in this object match them.
+
+*Type*: `array`
 
 ```yml
 # Examples
 
 bindings_declare:
-  - exchange: foo
-    key: bar
+  - exchange: my_exchange
+    key: my_routing_key
 ```
 
 === `bindings_declare[].exchange`
@@ -198,7 +259,7 @@ The key of the declared binding.
 
 === `consumer_tag`
 
-A consumer tag.
+A consumer tag to uniquely identify the consumer.
 
 
 *Type*: `string`
@@ -207,17 +268,17 @@ A consumer tag.
 
 === `auto_ack`
 
-Acknowledge messages automatically as they are consumed rather than waiting for acknowledgments from downstream. This can improve throughput and prevent the pipeline from blocking but at the cost of eliminating delivery guarantees.
-
+Set to `true` to automatically acknowledge messages as soon as they are consumed rather than waiting for acknowledgments from downstream. This can improve throughput and prevent the pipeline from becoming blocked, but delivery guarantees are lost.
 
 *Type*: `bool`
 
 *Default*: `false`
 
 === `nack_reject_patterns`
 
-A list of regular expression patterns whereby if a message that has failed to be delivered by Redpanda Connect has an error that matches it will be dropped (or delivered to a dead-letter queue if one exists). By default failed messages are nacked with requeue enabled.
+A list of regular expression patterns to match against errors in messages that Redpanda Connect fails to deliver. When a message has an error that matches a pattern, it is dropped or delivered to a dead-letter queue (if a queue has been configured).
 
+By default, failed messages are negatively acknowledged (nacked) and requeued.
 
 *Type*: `array`
 
@@ -236,16 +297,15 @@ nack_reject_patterns:
 
 === `prefetch_count`
 
-The maximum number of pending messages to have consumed at a time.
-
+The maximum number of pending messages at a given time.
 
 *Type*: `int`
 
 *Default*: `10`
 
 === `prefetch_size`
 
-The maximum amount of pending messages measured in bytes to have consumed at a time.
+The maximum size of pending messages (in bytes) at a given time.
 
 
 *Type*: `int`
@@ -254,12 +314,10 @@ The maximum amount of pending messages measured in bytes to have consumed at a t
 
 === `tls`
 
-Custom TLS settings can be used to override system defaults.
-
+Override system defaults with custom TLS settings.
 
 *Type*: `object`
 
-
 === `tls.enabled`
 
 Whether custom TLS settings are enabled.
@@ -271,7 +329,7 @@ Whether custom TLS settings are enabled.
 
 === `tls.skip_cert_verify`
 
-Whether to skip server side certificate verification.
+Whether to skip server-side certificate verification.
 
 
 *Type*: `bool`
@@ -293,7 +351,7 @@ endif::[]
 
 === `tls.root_cas`
 
-An optional root certificate authority to use. This is a string, representing a certificate chain from the parent trusted root certificate, to possible intermediate signing certificates, to the host certificate.
+Specify a certificate authority to use (optional). This is a string that represents a certificate chain from the parent-trusted root certificate, through possible intermediate signing certificates, to the host certificate.
 
 include::components:partial$secret_warning.adoc[]
 
@@ -313,8 +371,7 @@ root_cas: |-
 
 === `tls.root_cas_file`
 
-An optional path of a root certificate authority file to use. This is a file, often with a .pem extension, containing a certificate chain from the parent trusted root certificate, to possible intermediate signing certificates, to the host certificate.
-
+Specify the path to a root certificate authority file (optional). This is a file, often with a `.pem` extension, that contains a certificate chain from the parent-trusted root certificate, through possible intermediate signing certificates, to the host certificate.
 
 *Type*: `string`
 
@@ -328,7 +385,7 @@ root_cas_file: ./root_cas.pem
 
 === `tls.client_certs`
 
-A list of client certificates to use. For each certificate either the fields `cert` and `key`, or `cert_file` and `key_file` should be specified, but not both.
+A list of client certificates to use. For each certificate, specify values for either the `cert` and `key` fields, or the `cert_file` and `key_file` fields.
 
 
 *Type*: `array`
@@ -389,12 +446,10 @@ The path of a certificate key to use.
 
 A plain text password for when the private key is password encrypted in PKCS#1 or PKCS#8 format. The obsolete `pbeWithMD5AndDES-CBC` algorithm is not supported for the PKCS#8 format.
 
-Because the obsolete pbeWithMD5AndDES-CBC algorithm does not authenticate the ciphertext, it is vulnerable to padding oracle attacks that can let an attacker recover the plaintext.
+WARNING: The `pbeWithMD5AndDES-CBC` algorithm does not authenticate ciphertext, and is vulnerable to padding oracle attacks, which may allow an attacker to recover the plain text password.
 
 include::components:partial$secret_warning.adoc[]
 
-
-
 *Type*: `string`
 
 *Default*: `""`