@robinmordasiewicz/f5xc-terraform-mcp 2.3.0 → 2.4.3

package/dist/docs/resources/alert_receiver.md

@@ -0,0 +1,394 @@
+---
+page_title: "f5xc_alert_receiver Resource - terraform-provider-f5xc"
+subcategory: "Monitoring"
+description: |-
+  [Category: Monitoring] [Namespace: required] Manages a Alert Receiver resource in F5 Distributed Cloud for alert notification endpoints.
+---
+
+# f5xc_alert_receiver (Resource)
+
+[Category: Monitoring] [Namespace: required] Manages a Alert Receiver resource in F5 Distributed Cloud for alert notification endpoints.
+
+~> **Note** Please refer to [Alert Receiver API docs](https://docs.cloud.f5.com/docs-v2/api/alert-receiver) to learn more.
+
+## Example Usage
+
+```terraform
+# Alert Receiver Resource Example
+# [Category: Monitoring] [Namespace: required] Manages a Alert Receiver resource in F5 Distributed Cloud for alert notification endpoints.
+
+# Basic Alert Receiver configuration
+resource "f5xc_alert_receiver" "example" {
+  name      = "example-alert-receiver"
+  namespace = "shared"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  # Alert Receiver configuration
+  # Slack configuration
+  slack {
+    url = "`https://your-slack-webhook-url"`
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the Alert Receiver. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the Alert 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="email"></a>[`email`](#email) - Optional Block<br>Email Configuration<br>See [Email](#email) below for details.
+<br><br>&#x2022; <a id="opsgenie"></a>[`opsgenie`](#opsgenie) - Optional Block<br>OpsGenie Config. OpsGenie configuration to send alert notifications<br>See [Opsgenie](#opsgenie) below for details.
+<br><br>&#x2022; <a id="pagerduty"></a>[`pagerduty`](#pagerduty) - Optional Block<br>PagerDuty Config. PagerDuty configuration to send alert notifications<br>See [Pagerduty](#pagerduty) below for details.
+<br><br>&#x2022; <a id="slack"></a>[`slack`](#slack) - Optional Block<br>Slack Config. Slack configuration to send alert notifications<br>See [Slack](#slack) below for details.
+<br><br>&#x2022; <a id="sms"></a>[`sms`](#sms) - Optional Block<br>SMS Configuration<br>See [Sms](#sms) below for details.
+<br><br>&#x2022; <a id="webhook"></a>[`webhook`](#webhook) - Optional Block<br>Webhook Config. Webhook configuration to send alert notifications<br>See [Webhook](#webhook) below for details.
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
+
+### 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
+
+---
+
+#### Email
+
+An [`email`](#email) block supports the following:
+
+<a id="email-email"></a>&#x2022; [`email`](#email-email) - Optional String<br>Email. Email ID of the user
+
+#### Opsgenie
+
+An [`opsgenie`](#opsgenie) block supports the following:
+
+<a id="opsgenie-api-key"></a>&#x2022; [`api_key`](#opsgenie-api-key) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [API Key](#opsgenie-api-key) below.
+
+<a id="opsgenie-url"></a>&#x2022; [`url`](#opsgenie-url) - Optional String<br>API URL. URL to send API requests to
+
+#### Opsgenie API Key
+
+An [`api_key`](#opsgenie-api-key) block (within [`opsgenie`](#opsgenie)) supports the following:
+
+<a id="opsgenie-api-key-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#opsgenie-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](#opsgenie-api-key-blindfold-secret-info) below.
+
+<a id="opsgenie-api-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#opsgenie-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](#opsgenie-api-key-clear-secret-info) below.
+
+#### Opsgenie API Key Blindfold Secret Info
+
+A [`blindfold_secret_info`](#opsgenie-api-key-blindfold-secret-info) block (within [`opsgenie.api_key`](#opsgenie-api-key)) supports the following:
+
+<a id="opsgenie-api-key-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#opsgenie-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="opsgenie-api-key-blindfold-secret-info-location"></a>&#x2022; [`location`](#opsgenie-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="opsgenie-api-key-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#opsgenie-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:///
+
+#### Opsgenie API Key Clear Secret Info
+
+A [`clear_secret_info`](#opsgenie-api-key-clear-secret-info) block (within [`opsgenie.api_key`](#opsgenie-api-key)) supports the following:
+
+<a id="opsgenie-api-key-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#opsgenie-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="opsgenie-api-key-clear-secret-info-url"></a>&#x2022; [`url`](#opsgenie-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
+
+#### Pagerduty
+
+A [`pagerduty`](#pagerduty) block supports the following:
+
+<a id="pagerduty-routing-key"></a>&#x2022; [`routing_key`](#pagerduty-routing-key) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Routing Key](#pagerduty-routing-key) below.
+
+<a id="pagerduty-url"></a>&#x2022; [`url`](#pagerduty-url) - Optional String<br>Pager Duty URL. URL to send API requests to
+
+#### Pagerduty Routing Key
+
+A [`routing_key`](#pagerduty-routing-key) block (within [`pagerduty`](#pagerduty)) supports the following:
+
+<a id="pagerduty-routing-key-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#pagerduty-routing-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](#pagerduty-routing-key-blindfold-secret-info) below.
+
+<a id="pagerduty-routing-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#pagerduty-routing-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](#pagerduty-routing-key-clear-secret-info) below.
+
+#### Pagerduty Routing Key Blindfold Secret Info
+
+A [`blindfold_secret_info`](#pagerduty-routing-key-blindfold-secret-info) block (within [`pagerduty.routing_key`](#pagerduty-routing-key)) supports the following:
+
+<a id="pagerduty-routing-key-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#pagerduty-routing-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="pagerduty-routing-key-blindfold-secret-info-location"></a>&#x2022; [`location`](#pagerduty-routing-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="pagerduty-routing-key-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#pagerduty-routing-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:///
+
+#### Pagerduty Routing Key Clear Secret Info
+
+A [`clear_secret_info`](#pagerduty-routing-key-clear-secret-info) block (within [`pagerduty.routing_key`](#pagerduty-routing-key)) supports the following:
+
+<a id="pagerduty-routing-key-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#pagerduty-routing-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="pagerduty-routing-key-clear-secret-info-url"></a>&#x2022; [`url`](#pagerduty-routing-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
+
+#### Slack
+
+A [`slack`](#slack) block supports the following:
+
+<a id="slack-channel"></a>&#x2022; [`channel`](#slack-channel) - Optional String<br>Channel. Channel or user to send notifications to
+
+<a id="slack-url"></a>&#x2022; [`url`](#slack-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [URL](#slack-url) below.
+
+#### Slack URL
+
+An [`url`](#slack-url) block (within [`slack`](#slack)) supports the following:
+
+<a id="slack-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#slack-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](#slack-url-blindfold-secret-info) below.
+
+<a id="slack-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#slack-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](#slack-url-clear-secret-info) below.
+
+#### Slack URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#slack-url-blindfold-secret-info) block (within [`slack.url`](#slack-url)) supports the following:
+
+<a id="slack-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#slack-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="slack-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#slack-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="slack-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#slack-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:///
+
+#### Slack URL Clear Secret Info
+
+A [`clear_secret_info`](#slack-url-clear-secret-info) block (within [`slack.url`](#slack-url)) supports the following:
+
+<a id="slack-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#slack-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="slack-url-clear-secret-info-url"></a>&#x2022; [`url`](#slack-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
+
+#### Sms
+
+A [`sms`](#sms) block supports the following:
+
+<a id="sms-contact-number"></a>&#x2022; [`contact_number`](#sms-contact-number) - Optional String<br>Contact Number. Contact number of the user in ITU E.164 format [+]\[country code][subscriber number including area code]
+
+#### 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
+
+#### Webhook
+
+A [`webhook`](#webhook) block supports the following:
+
+<a id="webhook-http-config"></a>&#x2022; [`http_config`](#webhook-http-config) - Optional Block<br>HTTP Configuration. Configuration for HTTP endpoint<br>See [HTTP Config](#webhook-http-config) below.
+
+<a id="webhook-url"></a>&#x2022; [`url`](#webhook-url) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [URL](#webhook-url) below.
+
+#### Webhook HTTP Config
+
+A [`http_config`](#webhook-http-config) block (within [`webhook`](#webhook)) supports the following:
+
+<a id="webhook-http-config-auth-token"></a>&#x2022; [`auth_token`](#webhook-http-config-auth-token) - Optional Block<br>Access Token. Authentication Token for access<br>See [Auth Token](#webhook-http-config-auth-token) below.
+
+<a id="webhook-http-config-basic-auth"></a>&#x2022; [`basic_auth`](#webhook-http-config-basic-auth) - Optional Block<br>Basic Authorization Credentials. Authorization parameters to access HTPP alert Receiver Endpoint<br>See [Basic Auth](#webhook-http-config-basic-auth) below.
+
+<a id="webhook-http-config-client-cert-obj"></a>&#x2022; [`client_cert_obj`](#webhook-http-config-client-cert-obj) - Optional Block<br>Client Certificate Object. Configuration for client certificate<br>See [Client Cert Obj](#webhook-http-config-client-cert-obj) below.
+
+<a id="webhook-http-config-enable-http2"></a>&#x2022; [`enable_http2`](#webhook-http-config-enable-http2) - Optional Bool<br>Enable HTTP2. Configure to use HTTP2 protocol
+
+<a id="webhook-http-config-follow-redirects"></a>&#x2022; [`follow_redirects`](#webhook-http-config-follow-redirects) - Optional Bool<br>Follow Redirects. Configure whether HTTP requests follow HTTP 3xx redirects
+
+<a id="webhook-http-config-no-authorization"></a>&#x2022; [`no_authorization`](#webhook-http-config-no-authorization) - Optional Block<br>Enable this option
+
+<a id="webhook-http-config-no-tls"></a>&#x2022; [`no_tls`](#webhook-http-config-no-tls) - Optional Block<br>Enable this option
+
+<a id="webhook-http-config-use-tls"></a>&#x2022; [`use_tls`](#webhook-http-config-use-tls) - Optional Block<br>TLS Config. Configures the token request's TLS settings<br>See [Use TLS](#webhook-http-config-use-tls) below.
+
+#### Webhook HTTP Config Auth Token
+
+An [`auth_token`](#webhook-http-config-auth-token) block (within [`webhook.http_config`](#webhook-http-config)) supports the following:
+
+<a id="webhook-http-config-auth-token-token"></a>&#x2022; [`token`](#webhook-http-config-auth-token-token) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Token](#webhook-http-config-auth-token-token) below.
+
+#### Webhook HTTP Config Auth Token Token
+
+A [`token`](#webhook-http-config-auth-token-token) block (within [`webhook.http_config.auth_token`](#webhook-http-config-auth-token)) supports the following:
+
+<a id="webhook-http-config-auth-token-token-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#webhook-http-config-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](#webhook-http-config-auth-token-token-blindfold-secret-info) below.
+
+<a id="webhook-http-config-auth-token-token-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#webhook-http-config-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](#webhook-http-config-auth-token-token-clear-secret-info) below.
+
+#### Webhook HTTP Config Auth Token Token Blindfold Secret Info
+
+A [`blindfold_secret_info`](#webhook-http-config-auth-token-token-blindfold-secret-info) block (within [`webhook.http_config.auth_token.token`](#webhook-http-config-auth-token-token)) supports the following:
+
+<a id="webhook-http-config-auth-token-token-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#webhook-http-config-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="webhook-http-config-auth-token-token-blindfold-secret-info-location"></a>&#x2022; [`location`](#webhook-http-config-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="webhook-http-config-auth-token-token-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#webhook-http-config-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:///
+
+#### Webhook HTTP Config Auth Token Token Clear Secret Info
+
+A [`clear_secret_info`](#webhook-http-config-auth-token-token-clear-secret-info) block (within [`webhook.http_config.auth_token.token`](#webhook-http-config-auth-token-token)) supports the following:
+
+<a id="webhook-http-config-auth-token-token-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#webhook-http-config-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="webhook-http-config-auth-token-token-clear-secret-info-url"></a>&#x2022; [`url`](#webhook-http-config-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
+
+#### Webhook HTTP Config Basic Auth
+
+A [`basic_auth`](#webhook-http-config-basic-auth) block (within [`webhook.http_config`](#webhook-http-config)) supports the following:
+
+<a id="webhook-http-config-basic-auth-password"></a>&#x2022; [`password`](#webhook-http-config-basic-auth-password) - Optional Block<br>Secret. SecretType is used in an object to indicate a sensitive/confidential field<br>See [Password](#webhook-http-config-basic-auth-password) below.
+
+<a id="webhook-http-config-basic-auth-user-name"></a>&#x2022; [`user_name`](#webhook-http-config-basic-auth-user-name) - Optional String<br>User Name. HTTP Basic Auth User Name
+
+#### Webhook HTTP Config Basic Auth Password
+
+A [`password`](#webhook-http-config-basic-auth-password) block (within [`webhook.http_config.basic_auth`](#webhook-http-config-basic-auth)) supports the following:
+
+<a id="webhook-http-config-basic-auth-password-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#webhook-http-config-basic-auth-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](#webhook-http-config-basic-auth-password-blindfold-secret-info) below.
+
+<a id="webhook-http-config-basic-auth-password-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#webhook-http-config-basic-auth-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](#webhook-http-config-basic-auth-password-clear-secret-info) below.
+
+#### Webhook HTTP Config Basic Auth Password Blindfold Secret Info
+
+A [`blindfold_secret_info`](#webhook-http-config-basic-auth-password-blindfold-secret-info) block (within [`webhook.http_config.basic_auth.password`](#webhook-http-config-basic-auth-password)) supports the following:
+
+<a id="webhook-http-config-basic-auth-password-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#webhook-http-config-basic-auth-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="webhook-http-config-basic-auth-password-blindfold-secret-info-location"></a>&#x2022; [`location`](#webhook-http-config-basic-auth-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="webhook-http-config-basic-auth-password-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#webhook-http-config-basic-auth-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:///
+
+#### Webhook HTTP Config Basic Auth Password Clear Secret Info
+
+A [`clear_secret_info`](#webhook-http-config-basic-auth-password-clear-secret-info) block (within [`webhook.http_config.basic_auth.password`](#webhook-http-config-basic-auth-password)) supports the following:
+
+<a id="webhook-http-config-basic-auth-password-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#webhook-http-config-basic-auth-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="webhook-http-config-basic-auth-password-clear-secret-info-url"></a>&#x2022; [`url`](#webhook-http-config-basic-auth-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
+
+#### Webhook HTTP Config Client Cert Obj
+
+A [`client_cert_obj`](#webhook-http-config-client-cert-obj) block (within [`webhook.http_config`](#webhook-http-config)) supports the following:
+
+<a id="webhook-http-config-client-cert-obj-use-tls-obj"></a>&#x2022; [`use_tls_obj`](#webhook-http-config-client-cert-obj-use-tls-obj) - Optional Block<br>Certificate Object. Reference to client certificate object<br>See [Use TLS Obj](#webhook-http-config-client-cert-obj-use-tls-obj) below.
+
+#### Webhook HTTP Config Client Cert Obj Use TLS Obj
+
+An [`use_tls_obj`](#webhook-http-config-client-cert-obj-use-tls-obj) block (within [`webhook.http_config.client_cert_obj`](#webhook-http-config-client-cert-obj)) supports the following:
+
+<a id="webhook-http-config-client-cert-obj-use-tls-obj-kind"></a>&#x2022; [`kind`](#webhook-http-config-client-cert-obj-use-tls-obj-kind) - Optional String<br>Kind. When a configuration object(e.g. virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="webhook-http-config-client-cert-obj-use-tls-obj-name"></a>&#x2022; [`name`](#webhook-http-config-client-cert-obj-use-tls-obj-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="webhook-http-config-client-cert-obj-use-tls-obj-namespace"></a>&#x2022; [`namespace`](#webhook-http-config-client-cert-obj-use-tls-obj-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="webhook-http-config-client-cert-obj-use-tls-obj-tenant"></a>&#x2022; [`tenant`](#webhook-http-config-client-cert-obj-use-tls-obj-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
+
+<a id="webhook-http-config-client-cert-obj-use-tls-obj-uid"></a>&#x2022; [`uid`](#webhook-http-config-client-cert-obj-use-tls-obj-uid) - Optional String<br>UID. When a configuration object(e.g. virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. route's) uid
+
+#### Webhook HTTP Config Use TLS
+
+An [`use_tls`](#webhook-http-config-use-tls) block (within [`webhook.http_config`](#webhook-http-config)) supports the following:
+
+<a id="webhook-http-config-use-tls-disable-sni"></a>&#x2022; [`disable_sni`](#webhook-http-config-use-tls-disable-sni) - Optional Block<br>Enable this option
+
+<a id="webhook-http-config-use-tls-max-version"></a>&#x2022; [`max_version`](#webhook-http-config-use-tls-max-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+<a id="webhook-http-config-use-tls-min-version"></a>&#x2022; [`min_version`](#webhook-http-config-use-tls-min-version) - Optional String  Defaults to `TLS_AUTO`<br>Possible values are `TLS_AUTO`, `TLSv1_0`, `TLSv1_1`, `TLSv1_2`, `TLSv1_3`<br>[Enum: TLS_AUTO|TLSv1_0|TLSv1_1|TLSv1_2|TLSv1_3] TLS Protocol. TlsProtocol is enumeration of supported TLS versions F5 Distributed Cloud will choose the optimal TLS version
+
+<a id="webhook-http-config-use-tls-sni"></a>&#x2022; [`sni`](#webhook-http-config-use-tls-sni) - Optional String<br>SNI Value. SNI value to be used
+
+<a id="webhook-http-config-use-tls-use-server-verification"></a>&#x2022; [`use_server_verification`](#webhook-http-config-use-tls-use-server-verification) - Optional Block<br>TLS Validation Context for Servers. Upstream TLS Validation Context<br>See [Use Server Verification](#webhook-http-config-use-tls-use-server-verification) below.
+
+<a id="webhook-http-config-use-tls-volterra-trusted-ca"></a>&#x2022; [`volterra_trusted_ca`](#webhook-http-config-use-tls-volterra-trusted-ca) - Optional Block<br>Enable this option
+
+#### Webhook HTTP Config Use TLS Use Server Verification
+
+An [`use_server_verification`](#webhook-http-config-use-tls-use-server-verification) block (within [`webhook.http_config.use_tls`](#webhook-http-config-use-tls)) supports the following:
+
+<a id="webhook-http-config-use-tls-use-server-verification-ca-cert-obj"></a>&#x2022; [`ca_cert_obj`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj) - Optional Block<br>CA Certificate Object. Configuration for CA certificate<br>See [CA Cert Obj](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj) below.
+
+#### Webhook HTTP Config Use TLS Use Server Verification CA Cert Obj
+
+A [`ca_cert_obj`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj) block (within [`webhook.http_config.use_tls.use_server_verification`](#webhook-http-config-use-tls-use-server-verification)) supports the following:
+
+<a id="webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca"></a>&#x2022; [`trusted_ca`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca) - Optional Block<br>Certificate Object. Reference to client certificate object<br>See [Trusted CA](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca) below.
+
+#### Webhook HTTP Config Use TLS Use Server Verification CA Cert Obj Trusted CA
+
+A [`trusted_ca`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca) block (within [`webhook.http_config.use_tls.use_server_verification.ca_cert_obj`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj)) supports the following:
+
+<a id="webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-kind"></a>&#x2022; [`kind`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-kind) - Optional String<br>Kind. When a configuration object(e.g. virtual_host) refers to another(e.g route) then kind will hold the referred object's kind (e.g. 'route')
+
+<a id="webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-name"></a>&#x2022; [`name`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-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="webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-namespace"></a>&#x2022; [`namespace`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-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="webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-tenant"></a>&#x2022; [`tenant`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-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
+
+<a id="webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-uid"></a>&#x2022; [`uid`](#webhook-http-config-use-tls-use-server-verification-ca-cert-obj-trusted-ca-uid) - Optional String<br>UID. When a configuration object(e.g. virtual_host) refers to another(e.g route) then uid will hold the referred object's(e.g. route's) uid
+
+#### Webhook URL
+
+An [`url`](#webhook-url) block (within [`webhook`](#webhook)) supports the following:
+
+<a id="webhook-url-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#webhook-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](#webhook-url-blindfold-secret-info) below.
+
+<a id="webhook-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#webhook-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](#webhook-url-clear-secret-info) below.
+
+#### Webhook URL Blindfold Secret Info
+
+A [`blindfold_secret_info`](#webhook-url-blindfold-secret-info) block (within [`webhook.url`](#webhook-url)) supports the following:
+
+<a id="webhook-url-blindfold-secret-info-decryption-provider"></a>&#x2022; [`decryption_provider`](#webhook-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="webhook-url-blindfold-secret-info-location"></a>&#x2022; [`location`](#webhook-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="webhook-url-blindfold-secret-info-store-provider"></a>&#x2022; [`store_provider`](#webhook-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:///
+
+#### Webhook URL Clear Secret Info
+
+A [`clear_secret_info`](#webhook-url-clear-secret-info) block (within [`webhook.url`](#webhook-url)) supports the following:
+
+<a id="webhook-url-clear-secret-info-provider-ref"></a>&#x2022; [`provider_ref`](#webhook-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="webhook-url-clear-secret-info-url"></a>&#x2022; [`url`](#webhook-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
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_alert_receiver.example system/example
+```

package/dist/docs/resources/allowed_tenant.md

@@ -0,0 +1,104 @@
+---
+page_title: "f5xc_allowed_tenant Resource - terraform-provider-f5xc"
+subcategory: "Organization"
+description: |-
+  [Category: Organization] [Namespace: not_required] Manages allowed_tenant config instance. Name of the object is name of the tenant that is allowed to manage. in F5 Distributed Cloud.
+---
+
+# f5xc_allowed_tenant (Resource)
+
+[Category: Organization] [Namespace: not_required] Manages allowed_tenant config instance. Name of the object is name of the tenant that is allowed to manage. in F5 Distributed Cloud.
+
+~> **Note** Please refer to [Allowed Tenant API docs](https://docs.cloud.f5.com/docs-v2/api/tenant-management-allowed-tenant) to learn more.
+
+## Example Usage
+
+```terraform
+# Allowed Tenant Resource Example
+# [Category: Organization] [Namespace: not_required] Manages allowed_tenant config instance. Name of the object is name of the tenant that is allowed to manage. in F5 Distributed Cloud.
+
+# Basic Allowed Tenant configuration
+resource "f5xc_allowed_tenant" "example" {
+  name      = "example-allowed-tenant"
+  namespace = "staging"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  # Resource-specific configuration
+  # Allowed Groups. List of references to allowed user_group ...
+  allowed_groups {
+    # Configure allowed_groups settings
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the Allowed Tenant. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the Allowed Tenant 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
+
+<a id="allowed-groups"></a>&#x2022; [`allowed_groups`](#allowed-groups) - Optional Block<br>Allowed Groups. List of references to allowed user_group objects for access in to tenant. Admin can use this to control API access by users from from original tenant into an allowed tenant. User access from original tenant into an allowed tenant will be associated to underlying roles in this user_group<br>See [Allowed Groups](#allowed-groups) below for details.
+
+<a id="tenant-id"></a>&#x2022; [`tenant_id`](#tenant-id) - Optional String<br>Allowed Tenant ID. Specify the Tenant ID of the Original Tenant which is allowed to manage. NOTE: this is the name of the tenant configuration obj. not UID
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
+
+### 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
+
+---
+
+#### Allowed Groups
+
+An [`allowed_groups`](#allowed-groups) block supports the following:
+
+<a id="allowed-groups-name"></a>&#x2022; [`name`](#allowed-groups-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="allowed-groups-namespace"></a>&#x2022; [`namespace`](#allowed-groups-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="allowed-groups-tenant"></a>&#x2022; [`tenant`](#allowed-groups-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
+
+#### 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_allowed_tenant.example system/example
+```