@robinmordasiewicz/f5xc-terraform-mcp 2.3.0 → 2.4.4

package/dist/docs/resources/global_log_receiver.md

@@ -0,0 +1,1085 @@
+---
+page_title: "f5xc_global_log_receiver Resource - terraform-provider-f5xc"
+subcategory: "Monitoring"
+description: |-
+  [Category: Monitoring] [Namespace: required] Manages a Global Log Receiver resource in F5 Distributed Cloud for global log aggregation settings.
+---
+
+# f5xc_global_log_receiver (Resource)
+
+[Category: Monitoring] [Namespace: required] Manages a Global Log Receiver resource in F5 Distributed Cloud for global log aggregation settings.
+
+~> **Note** Please refer to [Global Log Receiver API docs](https://docs.cloud.f5.com/docs-v2/api/global-log-receiver) to learn more.
+
+## Example Usage
+
+```terraform
+# Global Log Receiver Resource Example
+# [Category: Monitoring] [Namespace: required] Manages a Global Log Receiver resource in F5 Distributed Cloud for global log aggregation settings.
+
+# Basic Global Log Receiver configuration
+resource "f5xc_global_log_receiver" "example" {
+  name      = "example-global-log-receiver"
+  namespace = "system"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  # Resource-specific configuration
+  # [OneOf: audit_logs, dns_logs, request_logs, security_even...
+  audit_logs {
+    # Configure audit_logs settings
+  }
+  # [OneOf: aws_cloud_watch_receiver, azure_event_hubs_receiv...
+  aws_cloud_watch_receiver {
+    # Configure aws_cloud_watch_receiver settings
+  }
+  # Object reference. This type establishes a direct referenc...
+  aws_cred {
+    # Configure aws_cred settings
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the Global Log Receiver. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the Global Log Receiver will be created
+
+<a id="annotations"></a>&#x2022; [`annotations`](#annotations) - Optional Map<br>Annotations is an unstructured key value map stored with a resource that may be set by external tools to store and retrieve arbitrary metadata
+
+<a id="description"></a>&#x2022; [`description`](#description) - Optional String<br>Human readable description for the object
+
+<a id="disable"></a>&#x2022; [`disable`](#disable) - Optional Bool<br>A value of true will administratively disable the object
+
+<a id="labels"></a>&#x2022; [`labels`](#labels) - Optional Map<br>Labels is a user defined key value map that can be attached to resources for organization and filtering
+
+### Spec Argument Reference
+
+-> **One of the following:**
+&#x2022; <a id="audit-logs"></a>[`audit_logs`](#audit-logs) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="dns-logs"></a>[`dns_logs`](#dns-logs) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="request-logs"></a>[`request_logs`](#request-logs) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="security-events"></a>[`security_events`](#security-events) - Optional Block<br>Enable this option
+
+-> **One of the following:**
+&#x2022; <a id="aws-cloud-watch-receiver"></a>[`aws_cloud_watch_receiver`](#aws-cloud-watch-receiver) - Optional Block<br>AWS Cloudwatch Logs Configuration. AWS Cloudwatch Logs Configuration for Global Log Receiver<br>See [AWS Cloud Watch Receiver](#aws-cloud-watch-receiver) below for details.
+<br><br>&#x2022; <a id="azure-event-hubs-receiver"></a>[`azure_event_hubs_receiver`](#azure-event-hubs-receiver) - Optional Block<br>Azure Event Hubs Configuration. Azure Event Hubs Configuration for Global Log Receiver<br>See [Azure Event Hubs Receiver](#azure-event-hubs-receiver) below for details.
+<br><br>&#x2022; <a id="azure-receiver"></a>[`azure_receiver`](#azure-receiver) - Optional Block<br>Azure Blob Configuration. Azure Blob Configuration for Global Log Receiver<br>See [Azure Receiver](#azure-receiver) below for details.
+<br><br>&#x2022; <a id="datadog-receiver"></a>[`datadog_receiver`](#datadog-receiver) - Optional Block<br>Datadog Configuration. Configuration for Datadog endpoint<br>See [Datadog Receiver](#datadog-receiver) below for details.
+<br><br>&#x2022; <a id="gcp-bucket-receiver"></a>[`gcp_bucket_receiver`](#gcp-bucket-receiver) - Optional Block<br>GCP BucketConfiguration. GCP Bucket Configuration for Global Log Receiver<br>See [GCP Bucket Receiver](#gcp-bucket-receiver) below for details.
+<br><br>&#x2022; <a id="http-receiver"></a>[`http_receiver`](#http-receiver) - Optional Block<br>HTTP Configuration. Configuration for HTTP endpoint
+<br><br>&#x2022; <a id="kafka-receiver"></a>[`kafka_receiver`](#kafka-receiver) - Optional Block<br>Kafka Configuration. Kafka Configuration for Global Log Receiver
+<br><br>&#x2022; <a id="new-relic-receiver"></a>[`new_relic_receiver`](#new-relic-receiver) - Optional Block<br>NewRelic Configuration. Configuration for NewRelic endpoint
+<br><br>&#x2022; <a id="qradar-receiver"></a>[`qradar_receiver`](#qradar-receiver) - Optional Block<br>IBM QRadar Configuration. Configuration for IBM QRadar endpoint
+<br><br>&#x2022; <a id="s3-receiver"></a>[`s3_receiver`](#s3-receiver) - Optional Block<br>S3 Configuration. S3 Configuration for Global Log Receiver
+<br><br>&#x2022; <a id="splunk-receiver"></a>[`splunk_receiver`](#splunk-receiver) - Optional Block<br>Splunk HEC Logs Configuration. Configuration for Splunk HEC Logs endpoint
+<br><br>&#x2022; <a id="sumo-logic-receiver"></a>[`sumo_logic_receiver`](#sumo-logic-receiver) - Optional Block<br>SumoLogic Configuration. Configuration for SumoLogic endpoint
+
+-> **One of the following:**
+&#x2022; <a id="ns-all"></a>[`ns_all`](#ns-all) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="ns-current"></a>[`ns_current`](#ns-current) - Optional Block<br>Enable this option
+<br><br>&#x2022; <a id="ns-list"></a>[`ns_list`](#ns-list) - Optional Block<br>Namespace List. Namespace List
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block
+
+### Attributes Reference
+
+In addition to all arguments above, the following attributes are exported:
+
+<a id="id"></a>&#x2022; [`id`](#id) - Optional String<br>Unique identifier for the resource
+
+---
+
+#### AWS Cloud Watch Receiver
+
+An [`aws_cloud_watch_receiver`](#aws-cloud-watch-receiver) block supports the following:
+
+<a id="aws-cloud-watch-receiver-aws-cred"></a>&#x2022; [`aws_cred`](#aws-cloud-watch-receiver-aws-cred) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [AWS Cred](#aws-cloud-watch-receiver-aws-cred) below.
+
+<a id="aws-cloud-watch-receiver-aws-region"></a>&#x2022; [`aws_region`](#aws-cloud-watch-receiver-aws-region) - Optional String<br>AWS Region. AWS Region Name
+
+<a id="aws-cloud-watch-receiver-batch"></a>&#x2022; [`batch`](#aws-cloud-watch-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#aws-cloud-watch-receiver-batch) below.
+
+<a id="aws-cloud-watch-receiver-compression"></a>&#x2022; [`compression`](#aws-cloud-watch-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#aws-cloud-watch-receiver-compression) below.
+
+<a id="aws-cloud-watch-receiver-group-name"></a>&#x2022; [`group_name`](#aws-cloud-watch-receiver-group-name) - Optional String<br>Group Name. The group name of the target Cloudwatch Logs stream
+
+<a id="aws-cloud-watch-receiver-stream-name"></a>&#x2022; [`stream_name`](#aws-cloud-watch-receiver-stream-name) - Optional String<br>Stream Name. The stream name of the target Cloudwatch Logs stream. Note that there can only be one writer to a log stream at a time
+
+#### AWS Cloud Watch Receiver AWS Cred
+
+An [`aws_cred`](#aws-cloud-watch-receiver-aws-cred) block (within [`aws_cloud_watch_receiver`](#aws-cloud-watch-receiver)) supports the following:
+
+<a id="aws-cloud-watch-receiver-aws-cred-name"></a>&#x2022; [`name`](#aws-cloud-watch-receiver-aws-cred-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="aws-cloud-watch-receiver-aws-cred-namespace"></a>&#x2022; [`namespace`](#aws-cloud-watch-receiver-aws-cred-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="aws-cloud-watch-receiver-aws-cred-tenant"></a>&#x2022; [`tenant`](#aws-cloud-watch-receiver-aws-cred-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### AWS Cloud Watch Receiver Batch
+
+A [`batch`](#aws-cloud-watch-receiver-batch) block (within [`aws_cloud_watch_receiver`](#aws-cloud-watch-receiver)) supports the following:
+
+<a id="aws-cloud-watch-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#aws-cloud-watch-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="aws-cloud-watch-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#aws-cloud-watch-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="aws-cloud-watch-receiver-batch-max-events"></a>&#x2022; [`max_events`](#aws-cloud-watch-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="aws-cloud-watch-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#aws-cloud-watch-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="aws-cloud-watch-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#aws-cloud-watch-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="aws-cloud-watch-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#aws-cloud-watch-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### AWS Cloud Watch Receiver Compression
+
+A [`compression`](#aws-cloud-watch-receiver-compression) block (within [`aws_cloud_watch_receiver`](#aws-cloud-watch-receiver)) supports the following:
+
+<a id="aws-cloud-watch-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#aws-cloud-watch-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="aws-cloud-watch-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#aws-cloud-watch-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="aws-cloud-watch-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#aws-cloud-watch-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### Azure Event Hubs Receiver
+
+An [`azure_event_hubs_receiver`](#azure-event-hubs-receiver) block supports the following:
+
+<a id="azure-event-hubs-receiver-connection-string"></a>&#x2022; [`connection_string`](#azure-event-hubs-receiver-connection-string) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Connection String](#azure-event-hubs-receiver-connection-string) below.
+
+<a id="azure-event-hubs-receiver-instance"></a>&#x2022; [`instance`](#azure-event-hubs-receiver-instance) - Optional String<br>Event Hubs Instance. Event Hubs Instance name into which logs should be stored
+
+<a id="azure-event-hubs-receiver-namespace"></a>&#x2022; [`namespace`](#azure-event-hubs-receiver-namespace) - Optional String<br>Event Hubs Namespace. Event Hubs Namespace is namespace with instance into which logs should be stored
+
+#### Azure Event Hubs Receiver Connection String
+
+A [`connection_string`](#azure-event-hubs-receiver-connection-string) block (within [`azure_event_hubs_receiver`](#azure-event-hubs-receiver)) supports the following:
+
+<a id="azure-event-hubs-receiver-connection-string-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#azure-event-hubs-receiver-connection-string-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#azure-event-hubs-receiver-connection-string-blindfold-secret-info) below.
+
+<a id="azure-event-hubs-receiver-connection-string-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#azure-event-hubs-receiver-connection-string-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#azure-event-hubs-receiver-connection-string-clear-secret-info) below.
+
+#### Azure Event Hubs Receiver Connection String Blindfold Secret Info
+
+A [`blindfold_secret_info`](#azure-event-hubs-receiver-connection-string-blindfold-secret-info) block (within [`azure_event_hubs_receiver.connection_string`](#azure-event-hubs-receiver-connection-string)) supports the following:
+
+<a id="azure-event-hubs-receiver-connection-string-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#azure-event-hubs-receiver-connection-string-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="azure-event-hubs-receiver-connection-string-blindfold-secret-info-location"></a>&#x2022; [`location`](#azure-event-hubs-receiver-connection-string-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="azure-event-hubs-receiver-connection-string-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#azure-event-hubs-receiver-connection-string-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Azure Event Hubs Receiver Connection String Clear Secret Info
+
+A [`clear_secret_info`](#azure-event-hubs-receiver-connection-string-clear-secret-info) block (within [`azure_event_hubs_receiver.connection_string`](#azure-event-hubs-receiver-connection-string)) supports the following:
+
+<a id="azure-event-hubs-receiver-connection-string-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#azure-event-hubs-receiver-connection-string-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="azure-event-hubs-receiver-connection-string-clear-secret-info-url"></a>&#x2022; [`url`](#azure-event-hubs-receiver-connection-string-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Azure Receiver
+
+An [`azure_receiver`](#azure-receiver) block supports the following:
+
+<a id="azure-receiver-batch"></a>&#x2022; [`batch`](#azure-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#azure-receiver-batch) below.
+
+<a id="azure-receiver-compression"></a>&#x2022; [`compression`](#azure-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#azure-receiver-compression) below.
+
+<a id="azure-receiver-connection-string"></a>&#x2022; [`connection_string`](#azure-receiver-connection-string) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Connection String](#azure-receiver-connection-string) below.
+
+<a id="azure-receiver-container-name"></a>&#x2022; [`container_name`](#azure-receiver-container-name) - Optional String<br>Container Name. Container Name is the name of the container into which logs should be stored
+
+<a id="azure-receiver-filename-options"></a>&#x2022; [`filename_options`](#azure-receiver-filename-options) - Optional Block<br>Filename Options. Filename Options allow customization of filename and folder paths used by a destination endpoint bucket or file<br>See [Filename Options](#azure-receiver-filename-options) below.
+
+#### Azure Receiver Batch
+
+A [`batch`](#azure-receiver-batch) block (within [`azure_receiver`](#azure-receiver)) supports the following:
+
+<a id="azure-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#azure-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="azure-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#azure-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="azure-receiver-batch-max-events"></a>&#x2022; [`max_events`](#azure-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="azure-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#azure-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="azure-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#azure-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="azure-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#azure-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### Azure Receiver Compression
+
+A [`compression`](#azure-receiver-compression) block (within [`azure_receiver`](#azure-receiver)) supports the following:
+
+<a id="azure-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#azure-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="azure-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#azure-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="azure-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#azure-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### Azure Receiver Connection String
+
+A [`connection_string`](#azure-receiver-connection-string) block (within [`azure_receiver`](#azure-receiver)) supports the following:
+
+<a id="azure-receiver-connection-string-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#azure-receiver-connection-string-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#azure-receiver-connection-string-blindfold-secret-info) below.
+
+<a id="azure-receiver-connection-string-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#azure-receiver-connection-string-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#azure-receiver-connection-string-clear-secret-info) below.
+
+#### Azure Receiver Connection String Blindfold Secret Info
+
+A [`blindfold_secret_info`](#azure-receiver-connection-string-blindfold-secret-info) block (within [`azure_receiver.connection_string`](#azure-receiver-connection-string)) supports the following:
+
+<a id="azure-receiver-connection-string-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#azure-receiver-connection-string-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="azure-receiver-connection-string-blindfold-secret-info-location"></a>&#x2022; [`location`](#azure-receiver-connection-string-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="azure-receiver-connection-string-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#azure-receiver-connection-string-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Azure Receiver Connection String Clear Secret Info
+
+A [`clear_secret_info`](#azure-receiver-connection-string-clear-secret-info) block (within [`azure_receiver.connection_string`](#azure-receiver-connection-string)) supports the following:
+
+<a id="azure-receiver-connection-string-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#azure-receiver-connection-string-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="azure-receiver-connection-string-clear-secret-info-url"></a>&#x2022; [`url`](#azure-receiver-connection-string-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Azure Receiver Filename Options
+
+A [`filename_options`](#azure-receiver-filename-options) block (within [`azure_receiver`](#azure-receiver)) supports the following:
+
+<a id="azure-receiver-filename-options-custom-folder"></a>&#x2022; [`custom_folder`](#azure-receiver-filename-options-custom-folder) - Optional String<br>Custom Folder. Use your own folder name as the name of the folder in the endpoint bucket or file The folder name must match `/^[a-z_]\[a-z0-9\-\._]*$/i`
+
+<a id="azure-receiver-filename-options-log-type-folder"></a>&#x2022; [`log_type_folder`](#azure-receiver-filename-options-log-type-folder) - Optional Block<br>Enable this option
+
+<a id="azure-receiver-filename-options-no-folder"></a>&#x2022; [`no_folder`](#azure-receiver-filename-options-no-folder) - Optional Block<br>Enable this option
+
+#### Datadog Receiver
+
+A [`datadog_receiver`](#datadog-receiver) block supports the following:
+
+<a id="datadog-receiver-batch"></a>&#x2022; [`batch`](#datadog-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#datadog-receiver-batch) below.
+
+<a id="datadog-receiver-compression"></a>&#x2022; [`compression`](#datadog-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#datadog-receiver-compression) below.
+
+<a id="datadog-receiver-datadog-api-key"></a>&#x2022; [`datadog_api_key`](#datadog-receiver-datadog-api-key) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Datadog API Key](#datadog-receiver-datadog-api-key) below.
+
+<a id="datadog-receiver-endpoint"></a>&#x2022; [`endpoint`](#datadog-receiver-endpoint) - Optional String<br>Datadog Endpoint. Datadog Endpoint, example: `example.com:9000`
+
+<a id="datadog-receiver-no-tls"></a>&#x2022; [`no_tls`](#datadog-receiver-no-tls) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-site"></a>&#x2022; [`site`](#datadog-receiver-site) - Optional String<br>Datadog Site. Datadog Site, example: `datadoghq.com`
+
+<a id="datadog-receiver-use-tls"></a>&#x2022; [`use_tls`](#datadog-receiver-use-tls) - Optional Block<br>TLS Parameters Endpoint. TLS Parameters for client connection to the endpoint<br>See [Use TLS](#datadog-receiver-use-tls) below.
+
+#### Datadog Receiver Batch
+
+A [`batch`](#datadog-receiver-batch) block (within [`datadog_receiver`](#datadog-receiver)) supports the following:
+
+<a id="datadog-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#datadog-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="datadog-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#datadog-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-batch-max-events"></a>&#x2022; [`max_events`](#datadog-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="datadog-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#datadog-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#datadog-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="datadog-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#datadog-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### Datadog Receiver Compression
+
+A [`compression`](#datadog-receiver-compression) block (within [`datadog_receiver`](#datadog-receiver)) supports the following:
+
+<a id="datadog-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#datadog-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#datadog-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#datadog-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### Datadog Receiver Datadog API Key
+
+A [`datadog_api_key`](#datadog-receiver-datadog-api-key) block (within [`datadog_receiver`](#datadog-receiver)) supports the following:
+
+<a id="datadog-receiver-datadog-api-key-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#datadog-receiver-datadog-api-key-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#datadog-receiver-datadog-api-key-blindfold-secret-info) below.
+
+<a id="datadog-receiver-datadog-api-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#datadog-receiver-datadog-api-key-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#datadog-receiver-datadog-api-key-clear-secret-info) below.
+
+#### Datadog Receiver Datadog API Key Blindfold Secret Info
+
+A [`blindfold_secret_info`](#datadog-receiver-datadog-api-key-blindfold-secret-info) block (within [`datadog_receiver.datadog_api_key`](#datadog-receiver-datadog-api-key)) supports the following:
+
+<a id="datadog-receiver-datadog-api-key-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#datadog-receiver-datadog-api-key-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="datadog-receiver-datadog-api-key-blindfold-secret-info-location"></a>&#x2022; [`location`](#datadog-receiver-datadog-api-key-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="datadog-receiver-datadog-api-key-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#datadog-receiver-datadog-api-key-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Datadog Receiver Datadog API Key Clear Secret Info
+
+A [`clear_secret_info`](#datadog-receiver-datadog-api-key-clear-secret-info) block (within [`datadog_receiver.datadog_api_key`](#datadog-receiver-datadog-api-key)) supports the following:
+
+<a id="datadog-receiver-datadog-api-key-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#datadog-receiver-datadog-api-key-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="datadog-receiver-datadog-api-key-clear-secret-info-url"></a>&#x2022; [`url`](#datadog-receiver-datadog-api-key-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Datadog Receiver Use TLS
+
+An [`use_tls`](#datadog-receiver-use-tls) block (within [`datadog_receiver`](#datadog-receiver)) supports the following:
+
+<a id="datadog-receiver-use-tls-disable-verify-certificate"></a>&#x2022; [`disable_verify_certificate`](#datadog-receiver-use-tls-disable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-use-tls-disable-verify-hostname"></a>&#x2022; [`disable_verify_hostname`](#datadog-receiver-use-tls-disable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-use-tls-enable-verify-certificate"></a>&#x2022; [`enable_verify_certificate`](#datadog-receiver-use-tls-enable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-use-tls-enable-verify-hostname"></a>&#x2022; [`enable_verify_hostname`](#datadog-receiver-use-tls-enable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-use-tls-mtls-disabled"></a>&#x2022; [`mtls_disabled`](#datadog-receiver-use-tls-mtls-disabled) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-use-tls-mtls-enable"></a>&#x2022; [`mtls_enable`](#datadog-receiver-use-tls-mtls-enable) - Optional Block<br>mTLS Client Config. mTLS Client config allows configuration of mTLS client options<br>See [mTLS Enable](#datadog-receiver-use-tls-mtls-enable) below.
+
+<a id="datadog-receiver-use-tls-no-ca"></a>&#x2022; [`no_ca`](#datadog-receiver-use-tls-no-ca) - Optional Block<br>Enable this option
+
+<a id="datadog-receiver-use-tls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#datadog-receiver-use-tls-trusted-ca-url) - Optional String<br>Server CA Certificates. The URL or value for trusted Server CA certificate or certificate chain Certificates in PEM format including the PEM headers
+
+#### Datadog Receiver Use TLS mTLS Enable
+
+A [`mtls_enable`](#datadog-receiver-use-tls-mtls-enable) block (within [`datadog_receiver.use_tls`](#datadog-receiver-use-tls)) supports the following:
+
+<a id="datadog-receiver-use-tls-mtls-enable-certificate"></a>&#x2022; [`certificate`](#datadog-receiver-use-tls-mtls-enable-certificate) - Optional String<br>Client Certificate. Client certificate is PEM-encoded certificate or certificate-chain
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url"></a>&#x2022; [`key_url`](#datadog-receiver-use-tls-mtls-enable-key-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Key URL](#datadog-receiver-use-tls-mtls-enable-key-url) below.
+
+#### Datadog Receiver Use TLS mTLS Enable Key URL
+
+A [`key_url`](#datadog-receiver-use-tls-mtls-enable-key-url) block (within [`datadog_receiver.use_tls.mtls_enable`](#datadog-receiver-use-tls-mtls-enable)) supports the following:
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) below.
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info) below.
+
+#### Datadog Receiver Use TLS mTLS Enable Key URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) block (within [`datadog_receiver.use_tls.mtls_enable.key_url`](#datadog-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#datadog-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Datadog Receiver Use TLS mTLS Enable Key URL Clear Secret Info
+
+A [`clear_secret_info`](#datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info) block (within [`datadog_receiver.use_tls.mtls_enable.key_url`](#datadog-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url"></a>&#x2022; [`url`](#datadog-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### GCP Bucket Receiver
+
+A [`gcp_bucket_receiver`](#gcp-bucket-receiver) block supports the following:
+
+<a id="gcp-bucket-receiver-batch"></a>&#x2022; [`batch`](#gcp-bucket-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#gcp-bucket-receiver-batch) below.
+
+<a id="gcp-bucket-receiver-bucket"></a>&#x2022; [`bucket`](#gcp-bucket-receiver-bucket) - Optional String<br>GCP Bucket Name. GCP Bucket Name
+
+<a id="gcp-bucket-receiver-compression"></a>&#x2022; [`compression`](#gcp-bucket-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#gcp-bucket-receiver-compression) below.
+
+<a id="gcp-bucket-receiver-filename-options"></a>&#x2022; [`filename_options`](#gcp-bucket-receiver-filename-options) - Optional Block<br>Filename Options. Filename Options allow customization of filename and folder paths used by a destination endpoint bucket or file<br>See [Filename Options](#gcp-bucket-receiver-filename-options) below.
+
+<a id="gcp-bucket-receiver-gcp-cred"></a>&#x2022; [`gcp_cred`](#gcp-bucket-receiver-gcp-cred) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [GCP Cred](#gcp-bucket-receiver-gcp-cred) below.
+
+#### GCP Bucket Receiver Batch
+
+A [`batch`](#gcp-bucket-receiver-batch) block (within [`gcp_bucket_receiver`](#gcp-bucket-receiver)) supports the following:
+
+<a id="gcp-bucket-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#gcp-bucket-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="gcp-bucket-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#gcp-bucket-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="gcp-bucket-receiver-batch-max-events"></a>&#x2022; [`max_events`](#gcp-bucket-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="gcp-bucket-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#gcp-bucket-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="gcp-bucket-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#gcp-bucket-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="gcp-bucket-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#gcp-bucket-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### GCP Bucket Receiver Compression
+
+A [`compression`](#gcp-bucket-receiver-compression) block (within [`gcp_bucket_receiver`](#gcp-bucket-receiver)) supports the following:
+
+<a id="gcp-bucket-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#gcp-bucket-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="gcp-bucket-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#gcp-bucket-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="gcp-bucket-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#gcp-bucket-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### GCP Bucket Receiver Filename Options
+
+A [`filename_options`](#gcp-bucket-receiver-filename-options) block (within [`gcp_bucket_receiver`](#gcp-bucket-receiver)) supports the following:
+
+<a id="gcp-bucket-receiver-filename-options-custom-folder"></a>&#x2022; [`custom_folder`](#gcp-bucket-receiver-filename-options-custom-folder) - Optional String<br>Custom Folder. Use your own folder name as the name of the folder in the endpoint bucket or file The folder name must match `/^[a-z_]\[a-z0-9\-\._]*$/i`
+
+<a id="gcp-bucket-receiver-filename-options-log-type-folder"></a>&#x2022; [`log_type_folder`](#gcp-bucket-receiver-filename-options-log-type-folder) - Optional Block<br>Enable this option
+
+<a id="gcp-bucket-receiver-filename-options-no-folder"></a>&#x2022; [`no_folder`](#gcp-bucket-receiver-filename-options-no-folder) - Optional Block<br>Enable this option
+
+#### GCP Bucket Receiver GCP Cred
+
+A [`gcp_cred`](#gcp-bucket-receiver-gcp-cred) block (within [`gcp_bucket_receiver`](#gcp-bucket-receiver)) supports the following:
+
+<a id="gcp-bucket-receiver-gcp-cred-name"></a>&#x2022; [`name`](#gcp-bucket-receiver-gcp-cred-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="gcp-bucket-receiver-gcp-cred-namespace"></a>&#x2022; [`namespace`](#gcp-bucket-receiver-gcp-cred-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="gcp-bucket-receiver-gcp-cred-tenant"></a>&#x2022; [`tenant`](#gcp-bucket-receiver-gcp-cred-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### HTTP Receiver
+
+A [`http_receiver`](#http-receiver) block supports the following:
+
+<a id="http-receiver-auth-basic"></a>&#x2022; [`auth_basic`](#http-receiver-auth-basic) - Optional Block<br>Basic Authentication Credentials. Authentication parameters to access HTPP Log Receiver Endpoint<br>See [Auth Basic](#http-receiver-auth-basic) below.
+
+<a id="http-receiver-auth-none"></a>&#x2022; [`auth_none`](#http-receiver-auth-none) - Optional Block<br>Enable this option
+
+<a id="http-receiver-auth-token"></a>&#x2022; [`auth_token`](#http-receiver-auth-token) - Optional Block<br>Access Token. Authentication Token for access<br>See [Auth Token](#http-receiver-auth-token) below.
+
+<a id="http-receiver-batch"></a>&#x2022; [`batch`](#http-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#http-receiver-batch) below.
+
+<a id="http-receiver-compression"></a>&#x2022; [`compression`](#http-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#http-receiver-compression) below.
+
+<a id="http-receiver-no-tls"></a>&#x2022; [`no_tls`](#http-receiver-no-tls) - Optional Block<br>Enable this option
+
+<a id="http-receiver-uri"></a>&#x2022; [`uri`](#http-receiver-uri) - Optional String<br>HTTP URI. HTTP URI is the URI of the HTTP endpoint to send logs to, example: `HTTP://example.com:9000/logs`
+
+<a id="http-receiver-use-tls"></a>&#x2022; [`use_tls`](#http-receiver-use-tls) - Optional Block<br>TLS Parameters Endpoint. TLS Parameters for client connection to the endpoint<br>See [Use TLS](#http-receiver-use-tls) below.
+
+#### HTTP Receiver Auth Basic
+
+An [`auth_basic`](#http-receiver-auth-basic) block (within [`http_receiver`](#http-receiver)) supports the following:
+
+<a id="http-receiver-auth-basic-password"></a>&#x2022; [`password`](#http-receiver-auth-basic-password) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Password](#http-receiver-auth-basic-password) below.
+
+<a id="http-receiver-auth-basic-user-name"></a>&#x2022; [`user_name`](#http-receiver-auth-basic-user-name) - Optional String<br>User Name. HTTP Basic Auth User Name
+
+#### HTTP Receiver Auth Basic Password
+
+A [`password`](#http-receiver-auth-basic-password) block (within [`http_receiver.auth_basic`](#http-receiver-auth-basic)) supports the following:
+
+<a id="http-receiver-auth-basic-password-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#http-receiver-auth-basic-password-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#http-receiver-auth-basic-password-blindfold-secret-info) below.
+
+<a id="http-receiver-auth-basic-password-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#http-receiver-auth-basic-password-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#http-receiver-auth-basic-password-clear-secret-info) below.
+
+#### HTTP Receiver Auth Basic Password Blindfold Secret Info
+
+A [`blindfold_secret_info`](#http-receiver-auth-basic-password-blindfold-secret-info) block (within [`http_receiver.auth_basic.password`](#http-receiver-auth-basic-password)) supports the following:
+
+<a id="http-receiver-auth-basic-password-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#http-receiver-auth-basic-password-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="http-receiver-auth-basic-password-blindfold-secret-info-location"></a>&#x2022; [`location`](#http-receiver-auth-basic-password-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="http-receiver-auth-basic-password-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#http-receiver-auth-basic-password-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### HTTP Receiver Auth Basic Password Clear Secret Info
+
+A [`clear_secret_info`](#http-receiver-auth-basic-password-clear-secret-info) block (within [`http_receiver.auth_basic.password`](#http-receiver-auth-basic-password)) supports the following:
+
+<a id="http-receiver-auth-basic-password-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#http-receiver-auth-basic-password-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="http-receiver-auth-basic-password-clear-secret-info-url"></a>&#x2022; [`url`](#http-receiver-auth-basic-password-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### HTTP Receiver Auth Token
+
+An [`auth_token`](#http-receiver-auth-token) block (within [`http_receiver`](#http-receiver)) supports the following:
+
+<a id="http-receiver-auth-token-token"></a>&#x2022; [`token`](#http-receiver-auth-token-token) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Token](#http-receiver-auth-token-token) below.
+
+#### HTTP Receiver Auth Token Token
+
+A [`token`](#http-receiver-auth-token-token) block (within [`http_receiver.auth_token`](#http-receiver-auth-token)) supports the following:
+
+<a id="http-receiver-auth-token-token-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#http-receiver-auth-token-token-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#http-receiver-auth-token-token-blindfold-secret-info) below.
+
+<a id="http-receiver-auth-token-token-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#http-receiver-auth-token-token-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#http-receiver-auth-token-token-clear-secret-info) below.
+
+#### HTTP Receiver Auth Token Token Blindfold Secret Info
+
+A [`blindfold_secret_info`](#http-receiver-auth-token-token-blindfold-secret-info) block (within [`http_receiver.auth_token.token`](#http-receiver-auth-token-token)) supports the following:
+
+<a id="http-receiver-auth-token-token-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#http-receiver-auth-token-token-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="http-receiver-auth-token-token-blindfold-secret-info-location"></a>&#x2022; [`location`](#http-receiver-auth-token-token-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="http-receiver-auth-token-token-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#http-receiver-auth-token-token-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### HTTP Receiver Auth Token Token Clear Secret Info
+
+A [`clear_secret_info`](#http-receiver-auth-token-token-clear-secret-info) block (within [`http_receiver.auth_token.token`](#http-receiver-auth-token-token)) supports the following:
+
+<a id="http-receiver-auth-token-token-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#http-receiver-auth-token-token-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="http-receiver-auth-token-token-clear-secret-info-url"></a>&#x2022; [`url`](#http-receiver-auth-token-token-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### HTTP Receiver Batch
+
+A [`batch`](#http-receiver-batch) block (within [`http_receiver`](#http-receiver)) supports the following:
+
+<a id="http-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#http-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="http-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#http-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="http-receiver-batch-max-events"></a>&#x2022; [`max_events`](#http-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="http-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#http-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="http-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#http-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="http-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#http-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### HTTP Receiver Compression
+
+A [`compression`](#http-receiver-compression) block (within [`http_receiver`](#http-receiver)) supports the following:
+
+<a id="http-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#http-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="http-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#http-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="http-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#http-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### HTTP Receiver Use TLS
+
+An [`use_tls`](#http-receiver-use-tls) block (within [`http_receiver`](#http-receiver)) supports the following:
+
+<a id="http-receiver-use-tls-disable-verify-certificate"></a>&#x2022; [`disable_verify_certificate`](#http-receiver-use-tls-disable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="http-receiver-use-tls-disable-verify-hostname"></a>&#x2022; [`disable_verify_hostname`](#http-receiver-use-tls-disable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="http-receiver-use-tls-enable-verify-certificate"></a>&#x2022; [`enable_verify_certificate`](#http-receiver-use-tls-enable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="http-receiver-use-tls-enable-verify-hostname"></a>&#x2022; [`enable_verify_hostname`](#http-receiver-use-tls-enable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="http-receiver-use-tls-mtls-disabled"></a>&#x2022; [`mtls_disabled`](#http-receiver-use-tls-mtls-disabled) - Optional Block<br>Enable this option
+
+<a id="http-receiver-use-tls-mtls-enable"></a>&#x2022; [`mtls_enable`](#http-receiver-use-tls-mtls-enable) - Optional Block<br>mTLS Client Config. mTLS Client config allows configuration of mTLS client options<br>See [mTLS Enable](#http-receiver-use-tls-mtls-enable) below.
+
+<a id="http-receiver-use-tls-no-ca"></a>&#x2022; [`no_ca`](#http-receiver-use-tls-no-ca) - Optional Block<br>Enable this option
+
+<a id="http-receiver-use-tls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#http-receiver-use-tls-trusted-ca-url) - Optional String<br>Server CA Certificates. The URL or value for trusted Server CA certificate or certificate chain Certificates in PEM format including the PEM headers
+
+#### HTTP Receiver Use TLS mTLS Enable
+
+A [`mtls_enable`](#http-receiver-use-tls-mtls-enable) block (within [`http_receiver.use_tls`](#http-receiver-use-tls)) supports the following:
+
+<a id="http-receiver-use-tls-mtls-enable-certificate"></a>&#x2022; [`certificate`](#http-receiver-use-tls-mtls-enable-certificate) - Optional String<br>Client Certificate. Client certificate is PEM-encoded certificate or certificate-chain
+
+<a id="http-receiver-use-tls-mtls-enable-key-url"></a>&#x2022; [`key_url`](#http-receiver-use-tls-mtls-enable-key-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Key URL](#http-receiver-use-tls-mtls-enable-key-url) below.
+
+#### HTTP Receiver Use TLS mTLS Enable Key URL
+
+A [`key_url`](#http-receiver-use-tls-mtls-enable-key-url) block (within [`http_receiver.use_tls.mtls_enable`](#http-receiver-use-tls-mtls-enable)) supports the following:
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) below.
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#http-receiver-use-tls-mtls-enable-key-url-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#http-receiver-use-tls-mtls-enable-key-url-clear-secret-info) below.
+
+#### HTTP Receiver Use TLS mTLS Enable Key URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) block (within [`http_receiver.use_tls.mtls_enable.key_url`](#http-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#http-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### HTTP Receiver Use TLS mTLS Enable Key URL Clear Secret Info
+
+A [`clear_secret_info`](#http-receiver-use-tls-mtls-enable-key-url-clear-secret-info) block (within [`http_receiver.use_tls.mtls_enable.key_url`](#http-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#http-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="http-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url"></a>&#x2022; [`url`](#http-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Kafka Receiver
+
+A [`kafka_receiver`](#kafka-receiver) block supports the following:
+
+<a id="kafka-receiver-batch"></a>&#x2022; [`batch`](#kafka-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#kafka-receiver-batch) below.
+
+<a id="kafka-receiver-bootstrap-servers"></a>&#x2022; [`bootstrap_servers`](#kafka-receiver-bootstrap-servers) - Optional List<br>Kafka Bootstrap Servers List. List of host:port pairs of the Kafka brokers
+
+<a id="kafka-receiver-compression"></a>&#x2022; [`compression`](#kafka-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#kafka-receiver-compression) below.
+
+<a id="kafka-receiver-kafka-topic"></a>&#x2022; [`kafka_topic`](#kafka-receiver-kafka-topic) - Optional String<br>Kafka Topic. The Kafka topic name to write events to
+
+<a id="kafka-receiver-no-tls"></a>&#x2022; [`no_tls`](#kafka-receiver-no-tls) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls"></a>&#x2022; [`use_tls`](#kafka-receiver-use-tls) - Optional Block<br>TLS Parameters Endpoint. TLS Parameters for client connection to the endpoint<br>See [Use TLS](#kafka-receiver-use-tls) below.
+
+#### Kafka Receiver Batch
+
+A [`batch`](#kafka-receiver-batch) block (within [`kafka_receiver`](#kafka-receiver)) supports the following:
+
+<a id="kafka-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#kafka-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="kafka-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#kafka-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-batch-max-events"></a>&#x2022; [`max_events`](#kafka-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="kafka-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#kafka-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#kafka-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="kafka-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#kafka-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### Kafka Receiver Compression
+
+A [`compression`](#kafka-receiver-compression) block (within [`kafka_receiver`](#kafka-receiver)) supports the following:
+
+<a id="kafka-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#kafka-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#kafka-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#kafka-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### Kafka Receiver Use TLS
+
+An [`use_tls`](#kafka-receiver-use-tls) block (within [`kafka_receiver`](#kafka-receiver)) supports the following:
+
+<a id="kafka-receiver-use-tls-disable-verify-certificate"></a>&#x2022; [`disable_verify_certificate`](#kafka-receiver-use-tls-disable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls-disable-verify-hostname"></a>&#x2022; [`disable_verify_hostname`](#kafka-receiver-use-tls-disable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls-enable-verify-certificate"></a>&#x2022; [`enable_verify_certificate`](#kafka-receiver-use-tls-enable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls-enable-verify-hostname"></a>&#x2022; [`enable_verify_hostname`](#kafka-receiver-use-tls-enable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls-mtls-disabled"></a>&#x2022; [`mtls_disabled`](#kafka-receiver-use-tls-mtls-disabled) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls-mtls-enable"></a>&#x2022; [`mtls_enable`](#kafka-receiver-use-tls-mtls-enable) - Optional Block<br>mTLS Client Config. mTLS Client config allows configuration of mTLS client options<br>See [mTLS Enable](#kafka-receiver-use-tls-mtls-enable) below.
+
+<a id="kafka-receiver-use-tls-no-ca"></a>&#x2022; [`no_ca`](#kafka-receiver-use-tls-no-ca) - Optional Block<br>Enable this option
+
+<a id="kafka-receiver-use-tls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#kafka-receiver-use-tls-trusted-ca-url) - Optional String<br>Server CA Certificates. The URL or value for trusted Server CA certificate or certificate chain Certificates in PEM format including the PEM headers
+
+#### Kafka Receiver Use TLS mTLS Enable
+
+A [`mtls_enable`](#kafka-receiver-use-tls-mtls-enable) block (within [`kafka_receiver.use_tls`](#kafka-receiver-use-tls)) supports the following:
+
+<a id="kafka-receiver-use-tls-mtls-enable-certificate"></a>&#x2022; [`certificate`](#kafka-receiver-use-tls-mtls-enable-certificate) - Optional String<br>Client Certificate. Client certificate is PEM-encoded certificate or certificate-chain
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url"></a>&#x2022; [`key_url`](#kafka-receiver-use-tls-mtls-enable-key-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Key URL](#kafka-receiver-use-tls-mtls-enable-key-url) below.
+
+#### Kafka Receiver Use TLS mTLS Enable Key URL
+
+A [`key_url`](#kafka-receiver-use-tls-mtls-enable-key-url) block (within [`kafka_receiver.use_tls.mtls_enable`](#kafka-receiver-use-tls-mtls-enable)) supports the following:
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) below.
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info) below.
+
+#### Kafka Receiver Use TLS mTLS Enable Key URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) block (within [`kafka_receiver.use_tls.mtls_enable.key_url`](#kafka-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#kafka-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Kafka Receiver Use TLS mTLS Enable Key URL Clear Secret Info
+
+A [`clear_secret_info`](#kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info) block (within [`kafka_receiver.use_tls.mtls_enable.key_url`](#kafka-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url"></a>&#x2022; [`url`](#kafka-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### New Relic Receiver
+
+A [`new_relic_receiver`](#new-relic-receiver) block supports the following:
+
+<a id="new-relic-receiver-api-key"></a>&#x2022; [`api_key`](#new-relic-receiver-api-key) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [API Key](#new-relic-receiver-api-key) below.
+
+<a id="new-relic-receiver-eu"></a>&#x2022; [`eu`](#new-relic-receiver-eu) - Optional Block<br>Enable this option
+
+<a id="new-relic-receiver-us"></a>&#x2022; [`us`](#new-relic-receiver-us) - Optional Block<br>Enable this option
+
+#### New Relic Receiver API Key
+
+An [`api_key`](#new-relic-receiver-api-key) block (within [`new_relic_receiver`](#new-relic-receiver)) supports the following:
+
+<a id="new-relic-receiver-api-key-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#new-relic-receiver-api-key-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#new-relic-receiver-api-key-blindfold-secret-info) below.
+
+<a id="new-relic-receiver-api-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#new-relic-receiver-api-key-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#new-relic-receiver-api-key-clear-secret-info) below.
+
+#### New Relic Receiver API Key Blindfold Secret Info
+
+A [`blindfold_secret_info`](#new-relic-receiver-api-key-blindfold-secret-info) block (within [`new_relic_receiver.api_key`](#new-relic-receiver-api-key)) supports the following:
+
+<a id="new-relic-receiver-api-key-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#new-relic-receiver-api-key-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="new-relic-receiver-api-key-blindfold-secret-info-location"></a>&#x2022; [`location`](#new-relic-receiver-api-key-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="new-relic-receiver-api-key-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#new-relic-receiver-api-key-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### New Relic Receiver API Key Clear Secret Info
+
+A [`clear_secret_info`](#new-relic-receiver-api-key-clear-secret-info) block (within [`new_relic_receiver.api_key`](#new-relic-receiver-api-key)) supports the following:
+
+<a id="new-relic-receiver-api-key-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#new-relic-receiver-api-key-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="new-relic-receiver-api-key-clear-secret-info-url"></a>&#x2022; [`url`](#new-relic-receiver-api-key-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Ns List
+
+A [`ns_list`](#ns-list) block supports the following:
+
+<a id="ns-list-namespaces"></a>&#x2022; [`namespaces`](#ns-list-namespaces) - Optional List<br>namespaces. List of namespaces to stream logs for
+
+#### Qradar Receiver
+
+A [`qradar_receiver`](#qradar-receiver) block supports the following:
+
+<a id="qradar-receiver-batch"></a>&#x2022; [`batch`](#qradar-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#qradar-receiver-batch) below.
+
+<a id="qradar-receiver-compression"></a>&#x2022; [`compression`](#qradar-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#qradar-receiver-compression) below.
+
+<a id="qradar-receiver-no-tls"></a>&#x2022; [`no_tls`](#qradar-receiver-no-tls) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-uri"></a>&#x2022; [`uri`](#qradar-receiver-uri) - Optional String<br>Log Source Collector URL. Log Source Collector URL is the URL of the IBM QRadar Log Source Collector to send logs to, example: `HTTP://example.com:9000`
+
+<a id="qradar-receiver-use-tls"></a>&#x2022; [`use_tls`](#qradar-receiver-use-tls) - Optional Block<br>TLS Parameters Endpoint. TLS Parameters for client connection to the endpoint<br>See [Use TLS](#qradar-receiver-use-tls) below.
+
+#### Qradar Receiver Batch
+
+A [`batch`](#qradar-receiver-batch) block (within [`qradar_receiver`](#qradar-receiver)) supports the following:
+
+<a id="qradar-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#qradar-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="qradar-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#qradar-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-batch-max-events"></a>&#x2022; [`max_events`](#qradar-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="qradar-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#qradar-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#qradar-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="qradar-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#qradar-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### Qradar Receiver Compression
+
+A [`compression`](#qradar-receiver-compression) block (within [`qradar_receiver`](#qradar-receiver)) supports the following:
+
+<a id="qradar-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#qradar-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#qradar-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#qradar-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### Qradar Receiver Use TLS
+
+An [`use_tls`](#qradar-receiver-use-tls) block (within [`qradar_receiver`](#qradar-receiver)) supports the following:
+
+<a id="qradar-receiver-use-tls-disable-verify-certificate"></a>&#x2022; [`disable_verify_certificate`](#qradar-receiver-use-tls-disable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-use-tls-disable-verify-hostname"></a>&#x2022; [`disable_verify_hostname`](#qradar-receiver-use-tls-disable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-use-tls-enable-verify-certificate"></a>&#x2022; [`enable_verify_certificate`](#qradar-receiver-use-tls-enable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-use-tls-enable-verify-hostname"></a>&#x2022; [`enable_verify_hostname`](#qradar-receiver-use-tls-enable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-use-tls-mtls-disabled"></a>&#x2022; [`mtls_disabled`](#qradar-receiver-use-tls-mtls-disabled) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-use-tls-mtls-enable"></a>&#x2022; [`mtls_enable`](#qradar-receiver-use-tls-mtls-enable) - Optional Block<br>mTLS Client Config. mTLS Client config allows configuration of mTLS client options<br>See [mTLS Enable](#qradar-receiver-use-tls-mtls-enable) below.
+
+<a id="qradar-receiver-use-tls-no-ca"></a>&#x2022; [`no_ca`](#qradar-receiver-use-tls-no-ca) - Optional Block<br>Enable this option
+
+<a id="qradar-receiver-use-tls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#qradar-receiver-use-tls-trusted-ca-url) - Optional String<br>Server CA Certificates. The URL or value for trusted Server CA certificate or certificate chain Certificates in PEM format including the PEM headers
+
+#### Qradar Receiver Use TLS mTLS Enable
+
+A [`mtls_enable`](#qradar-receiver-use-tls-mtls-enable) block (within [`qradar_receiver.use_tls`](#qradar-receiver-use-tls)) supports the following:
+
+<a id="qradar-receiver-use-tls-mtls-enable-certificate"></a>&#x2022; [`certificate`](#qradar-receiver-use-tls-mtls-enable-certificate) - Optional String<br>Client Certificate. Client certificate is PEM-encoded certificate or certificate-chain
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url"></a>&#x2022; [`key_url`](#qradar-receiver-use-tls-mtls-enable-key-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Key URL](#qradar-receiver-use-tls-mtls-enable-key-url) below.
+
+#### Qradar Receiver Use TLS mTLS Enable Key URL
+
+A [`key_url`](#qradar-receiver-use-tls-mtls-enable-key-url) block (within [`qradar_receiver.use_tls.mtls_enable`](#qradar-receiver-use-tls-mtls-enable)) supports the following:
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) below.
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info) below.
+
+#### Qradar Receiver Use TLS mTLS Enable Key URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) block (within [`qradar_receiver.use_tls.mtls_enable.key_url`](#qradar-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#qradar-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Qradar Receiver Use TLS mTLS Enable Key URL Clear Secret Info
+
+A [`clear_secret_info`](#qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info) block (within [`qradar_receiver.use_tls.mtls_enable.key_url`](#qradar-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url"></a>&#x2022; [`url`](#qradar-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### S3 Receiver
+
+A [`s3_receiver`](#s3-receiver) block supports the following:
+
+<a id="s3-receiver-aws-cred"></a>&#x2022; [`aws_cred`](#s3-receiver-aws-cred) - Optional Block<br>Object reference. This type establishes a direct reference from one object(the referrer) to another(the referred). Such a reference is in form of tenant/namespace/name<br>See [AWS Cred](#s3-receiver-aws-cred) below.
+
+<a id="s3-receiver-aws-region"></a>&#x2022; [`aws_region`](#s3-receiver-aws-region) - Optional String<br>AWS Region. AWS Region Name
+
+<a id="s3-receiver-batch"></a>&#x2022; [`batch`](#s3-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#s3-receiver-batch) below.
+
+<a id="s3-receiver-bucket"></a>&#x2022; [`bucket`](#s3-receiver-bucket) - Optional String<br>S3 Bucket Name. S3 Bucket Name
+
+<a id="s3-receiver-compression"></a>&#x2022; [`compression`](#s3-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#s3-receiver-compression) below.
+
+<a id="s3-receiver-filename-options"></a>&#x2022; [`filename_options`](#s3-receiver-filename-options) - Optional Block<br>Filename Options. Filename Options allow customization of filename and folder paths used by a destination endpoint bucket or file<br>See [Filename Options](#s3-receiver-filename-options) below.
+
+#### S3 Receiver AWS Cred
+
+An [`aws_cred`](#s3-receiver-aws-cred) block (within [`s3_receiver`](#s3-receiver)) supports the following:
+
+<a id="s3-receiver-aws-cred-name"></a>&#x2022; [`name`](#s3-receiver-aws-cred-name) - Optional String<br>Name. When a configuration object(e.g. virtual_host) refers to another(e.g route) then name will hold the referred object's(e.g. route's) name
+
+<a id="s3-receiver-aws-cred-namespace"></a>&#x2022; [`namespace`](#s3-receiver-aws-cred-namespace) - Optional String<br>Namespace. When a configuration object(e.g. virtual_host) refers to another(e.g route) then namespace will hold the referred object's(e.g. route's) namespace
+
+<a id="s3-receiver-aws-cred-tenant"></a>&#x2022; [`tenant`](#s3-receiver-aws-cred-tenant) - Optional String<br>Tenant. When a configuration object(e.g. virtual_host) refers to another(e.g route) then tenant will hold the referred object's(e.g. route's) tenant
+
+#### S3 Receiver Batch
+
+A [`batch`](#s3-receiver-batch) block (within [`s3_receiver`](#s3-receiver)) supports the following:
+
+<a id="s3-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#s3-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="s3-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#s3-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="s3-receiver-batch-max-events"></a>&#x2022; [`max_events`](#s3-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="s3-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#s3-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="s3-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#s3-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="s3-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#s3-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### S3 Receiver Compression
+
+A [`compression`](#s3-receiver-compression) block (within [`s3_receiver`](#s3-receiver)) supports the following:
+
+<a id="s3-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#s3-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="s3-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#s3-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="s3-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#s3-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### S3 Receiver Filename Options
+
+A [`filename_options`](#s3-receiver-filename-options) block (within [`s3_receiver`](#s3-receiver)) supports the following:
+
+<a id="s3-receiver-filename-options-custom-folder"></a>&#x2022; [`custom_folder`](#s3-receiver-filename-options-custom-folder) - Optional String<br>Custom Folder. Use your own folder name as the name of the folder in the endpoint bucket or file The folder name must match `/^[a-z_]\[a-z0-9\-\._]*$/i`
+
+<a id="s3-receiver-filename-options-log-type-folder"></a>&#x2022; [`log_type_folder`](#s3-receiver-filename-options-log-type-folder) - Optional Block<br>Enable this option
+
+<a id="s3-receiver-filename-options-no-folder"></a>&#x2022; [`no_folder`](#s3-receiver-filename-options-no-folder) - Optional Block<br>Enable this option
+
+#### Splunk Receiver
+
+A [`splunk_receiver`](#splunk-receiver) block supports the following:
+
+<a id="splunk-receiver-batch"></a>&#x2022; [`batch`](#splunk-receiver-batch) - Optional Block<br>Batch Options. Batch Options allow tuning for how batches of logs are sent to an endpoint<br>See [Batch](#splunk-receiver-batch) below.
+
+<a id="splunk-receiver-compression"></a>&#x2022; [`compression`](#splunk-receiver-compression) - Optional Block<br>Compression Type. Compression Type<br>See [Compression](#splunk-receiver-compression) below.
+
+<a id="splunk-receiver-endpoint"></a>&#x2022; [`endpoint`](#splunk-receiver-endpoint) - Optional String<br>Splunk HEC Logs Endpoint. Splunk HEC Logs Endpoint, example: `HTTPS://HTTP-input-hec.splunkcloud.com` (Note: must not contain `/services/collector`)
+
+<a id="splunk-receiver-no-tls"></a>&#x2022; [`no_tls`](#splunk-receiver-no-tls) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-splunk-hec-token"></a>&#x2022; [`splunk_hec_token`](#splunk-receiver-splunk-hec-token) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Splunk Hec Token](#splunk-receiver-splunk-hec-token) below.
+
+<a id="splunk-receiver-use-tls"></a>&#x2022; [`use_tls`](#splunk-receiver-use-tls) - Optional Block<br>TLS Parameters Endpoint. TLS Parameters for client connection to the endpoint<br>See [Use TLS](#splunk-receiver-use-tls) below.
+
+#### Splunk Receiver Batch
+
+A [`batch`](#splunk-receiver-batch) block (within [`splunk_receiver`](#splunk-receiver)) supports the following:
+
+<a id="splunk-receiver-batch-max-bytes"></a>&#x2022; [`max_bytes`](#splunk-receiver-batch-max-bytes) - Optional Number<br>Max Bytes. Send batch to endpoint after the batch is equal to or larger than this many bytes
+
+<a id="splunk-receiver-batch-max-bytes-disabled"></a>&#x2022; [`max_bytes_disabled`](#splunk-receiver-batch-max-bytes-disabled) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-batch-max-events"></a>&#x2022; [`max_events`](#splunk-receiver-batch-max-events) - Optional Number<br>Max Events. Send batch to endpoint after this many log messages are in the batch
+
+<a id="splunk-receiver-batch-max-events-disabled"></a>&#x2022; [`max_events_disabled`](#splunk-receiver-batch-max-events-disabled) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-batch-timeout-seconds"></a>&#x2022; [`timeout_seconds`](#splunk-receiver-batch-timeout-seconds) - Optional String<br>Timeout Seconds. Send batch to the endpoint after this many seconds
+
+<a id="splunk-receiver-batch-timeout-seconds-default"></a>&#x2022; [`timeout_seconds_default`](#splunk-receiver-batch-timeout-seconds-default) - Optional Block<br>Enable this option
+
+#### Splunk Receiver Compression
+
+A [`compression`](#splunk-receiver-compression) block (within [`splunk_receiver`](#splunk-receiver)) supports the following:
+
+<a id="splunk-receiver-compression-compression-default"></a>&#x2022; [`compression_default`](#splunk-receiver-compression-compression-default) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-compression-compression-gzip"></a>&#x2022; [`compression_gzip`](#splunk-receiver-compression-compression-gzip) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-compression-compression-none"></a>&#x2022; [`compression_none`](#splunk-receiver-compression-compression-none) - Optional Block<br>Enable this option
+
+#### Splunk Receiver Splunk Hec Token
+
+A [`splunk_hec_token`](#splunk-receiver-splunk-hec-token) block (within [`splunk_receiver`](#splunk-receiver)) supports the following:
+
+<a id="splunk-receiver-splunk-hec-token-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#splunk-receiver-splunk-hec-token-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#splunk-receiver-splunk-hec-token-blindfold-secret-info) below.
+
+<a id="splunk-receiver-splunk-hec-token-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#splunk-receiver-splunk-hec-token-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#splunk-receiver-splunk-hec-token-clear-secret-info) below.
+
+#### Splunk Receiver Splunk Hec Token Blindfold Secret Info
+
+A [`blindfold_secret_info`](#splunk-receiver-splunk-hec-token-blindfold-secret-info) block (within [`splunk_receiver.splunk_hec_token`](#splunk-receiver-splunk-hec-token)) supports the following:
+
+<a id="splunk-receiver-splunk-hec-token-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#splunk-receiver-splunk-hec-token-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="splunk-receiver-splunk-hec-token-blindfold-secret-info-location"></a>&#x2022; [`location`](#splunk-receiver-splunk-hec-token-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="splunk-receiver-splunk-hec-token-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#splunk-receiver-splunk-hec-token-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Splunk Receiver Splunk Hec Token Clear Secret Info
+
+A [`clear_secret_info`](#splunk-receiver-splunk-hec-token-clear-secret-info) block (within [`splunk_receiver.splunk_hec_token`](#splunk-receiver-splunk-hec-token)) supports the following:
+
+<a id="splunk-receiver-splunk-hec-token-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#splunk-receiver-splunk-hec-token-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="splunk-receiver-splunk-hec-token-clear-secret-info-url"></a>&#x2022; [`url`](#splunk-receiver-splunk-hec-token-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Splunk Receiver Use TLS
+
+An [`use_tls`](#splunk-receiver-use-tls) block (within [`splunk_receiver`](#splunk-receiver)) supports the following:
+
+<a id="splunk-receiver-use-tls-disable-verify-certificate"></a>&#x2022; [`disable_verify_certificate`](#splunk-receiver-use-tls-disable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-use-tls-disable-verify-hostname"></a>&#x2022; [`disable_verify_hostname`](#splunk-receiver-use-tls-disable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-use-tls-enable-verify-certificate"></a>&#x2022; [`enable_verify_certificate`](#splunk-receiver-use-tls-enable-verify-certificate) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-use-tls-enable-verify-hostname"></a>&#x2022; [`enable_verify_hostname`](#splunk-receiver-use-tls-enable-verify-hostname) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-use-tls-mtls-disabled"></a>&#x2022; [`mtls_disabled`](#splunk-receiver-use-tls-mtls-disabled) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-use-tls-mtls-enable"></a>&#x2022; [`mtls_enable`](#splunk-receiver-use-tls-mtls-enable) - Optional Block<br>mTLS Client Config. mTLS Client config allows configuration of mTLS client options<br>See [mTLS Enable](#splunk-receiver-use-tls-mtls-enable) below.
+
+<a id="splunk-receiver-use-tls-no-ca"></a>&#x2022; [`no_ca`](#splunk-receiver-use-tls-no-ca) - Optional Block<br>Enable this option
+
+<a id="splunk-receiver-use-tls-trusted-ca-url"></a>&#x2022; [`trusted_ca_url`](#splunk-receiver-use-tls-trusted-ca-url) - Optional String<br>Server CA Certificates. The URL or value for trusted Server CA certificate or certificate chain Certificates in PEM format including the PEM headers
+
+#### Splunk Receiver Use TLS mTLS Enable
+
+A [`mtls_enable`](#splunk-receiver-use-tls-mtls-enable) block (within [`splunk_receiver.use_tls`](#splunk-receiver-use-tls)) supports the following:
+
+<a id="splunk-receiver-use-tls-mtls-enable-certificate"></a>&#x2022; [`certificate`](#splunk-receiver-use-tls-mtls-enable-certificate) - Optional String<br>Client Certificate. Client certificate is PEM-encoded certificate or certificate-chain
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url"></a>&#x2022; [`key_url`](#splunk-receiver-use-tls-mtls-enable-key-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Key URL](#splunk-receiver-use-tls-mtls-enable-key-url) below.
+
+#### Splunk Receiver Use TLS mTLS Enable Key URL
+
+A [`key_url`](#splunk-receiver-use-tls-mtls-enable-key-url) block (within [`splunk_receiver.use_tls.mtls_enable`](#splunk-receiver-use-tls-mtls-enable)) supports the following:
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) below.
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info) below.
+
+#### Splunk Receiver Use TLS mTLS Enable Key URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info) block (within [`splunk_receiver.use_tls.mtls_enable.key_url`](#splunk-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#splunk-receiver-use-tls-mtls-enable-key-url-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Splunk Receiver Use TLS mTLS Enable Key URL Clear Secret Info
+
+A [`clear_secret_info`](#splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info) block (within [`splunk_receiver.use_tls.mtls_enable.key_url`](#splunk-receiver-use-tls-mtls-enable-key-url)) supports the following:
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url"></a>&#x2022; [`url`](#splunk-receiver-use-tls-mtls-enable-key-url-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Sumo Logic Receiver
+
+A [`sumo_logic_receiver`](#sumo-logic-receiver) block supports the following:
+
+<a id="sumo-logic-receiver-url"></a>&#x2022; [`url`](#sumo-logic-receiver-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [URL](#sumo-logic-receiver-url) below.
+
+#### Sumo Logic Receiver URL
+
+An [`url`](#sumo-logic-receiver-url) block (within [`sumo_logic_receiver`](#sumo-logic-receiver)) supports the following:
+
+<a id="sumo-logic-receiver-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#sumo-logic-receiver-url-blindfold-secret-info) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#sumo-logic-receiver-url-blindfold-secret-info) below.
+
+<a id="sumo-logic-receiver-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#sumo-logic-receiver-url-clear-secret-info) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#sumo-logic-receiver-url-clear-secret-info) below.
+
+#### Sumo Logic Receiver URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#sumo-logic-receiver-url-blindfold-secret-info) block (within [`sumo_logic_receiver.url`](#sumo-logic-receiver-url)) supports the following:
+
+<a id="sumo-logic-receiver-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#sumo-logic-receiver-url-blindfold-secret-info-decryption-provider) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+
+<a id="sumo-logic-receiver-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#sumo-logic-receiver-url-blindfold-secret-info-location) - Optional String<br>Location. Location is the uri_ref. It could be in URL format for string:/// Or it could be a path if the store provider is an HTTP/HTTPS location
+
+<a id="sumo-logic-receiver-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#sumo-logic-receiver-url-blindfold-secret-info-store-provider) - Optional String<br>Store Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+#### Sumo Logic Receiver URL Clear Secret Info
+
+A [`clear_secret_info`](#sumo-logic-receiver-url-clear-secret-info) block (within [`sumo_logic_receiver.url`](#sumo-logic-receiver-url)) supports the following:
+
+<a id="sumo-logic-receiver-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#sumo-logic-receiver-url-clear-secret-info-provider-ref) - Optional String<br>Provider. Name of the Secret Management Access object that contains information about the store to get encrypted bytes This field needs to be provided only if the URL scheme is not string:///
+
+<a id="sumo-logic-receiver-url-clear-secret-info-url"></a>&#x2022; [`url`](#sumo-logic-receiver-url-clear-secret-info-url) - Optional String<br>URL. URL of the secret. Currently supported URL schemes is string:///. For string:/// scheme, Secret needs to be encoded Base64 format. When asked for this secret, caller will get Secret bytes after Base64 decoding
+
+#### Timeouts
+
+A [`timeouts`](#timeouts) block supports the following:
+
+<a id="timeouts-create"></a>&#x2022; [`create`](#timeouts-create) - Optional String (Defaults to `10 minutes`)<br>Used when creating the resource
+
+<a id="timeouts-delete"></a>&#x2022; [`delete`](#timeouts-delete) - Optional String (Defaults to `10 minutes`)<br>Used when deleting the resource
+
+<a id="timeouts-read"></a>&#x2022; [`read`](#timeouts-read) - Optional String (Defaults to `5 minutes`)<br>Used when retrieving the resource
+
+<a id="timeouts-update"></a>&#x2022; [`update`](#timeouts-update) - Optional String (Defaults to `10 minutes`)<br>Used when updating the resource
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_global_log_receiver.example system/example
+```