@robinmordasiewicz/f5xc-terraform-mcp 3.5.1 → 3.6.0

package/dist/docs/resources/alert_policy.md

@@ -72,11 +72,11 @@ resource "f5xc_alert_policy" "example" {
 
 ### Spec Argument Reference
 
-<a id="notification-parameters"></a>&#x2022; [`notification_parameters`](#notification-parameters) - Optional Block  Defaults to `null`<br>Notification Parameters. Set of notification parameters to decide how and when the alert notifications should be sent to the receivers<br>See [Notification Parameters](#notification-parameters) below for details.
+<a id="notification-parameters"></a>&#x2022; [`notification_parameters`](#notification-parameters) - Optional Block  Defaults to `null`<br>Set of notification parameters to decide how and when the alert notifications should be sent to the receivers<br>See [Notification Parameters](#notification-parameters) below for details.
 
-<a id="receivers"></a>&#x2022; [`receivers`](#receivers) - Optional Block<br>Alert Receivers. List of Alert Receivers where the alerts will be sent<br>See [Receivers](#receivers) below for details.
+<a id="receivers"></a>&#x2022; [`receivers`](#receivers) - Optional Block<br>List of Alert Receivers where the alerts will be sent<br>See [Receivers](#receivers) below for details.
 
-<a id="routes"></a>&#x2022; [`routes`](#routes) - Optional Block<br>Policy Rules. Set of routes to match the incoming alert. The routes are evaluated in the specified order and terminates on the first match<br>See [Routes](#routes) below for details.
+<a id="routes"></a>&#x2022; [`routes`](#routes) - Optional Block<br>Set of routes to match the incoming alert. The routes are evaluated in the specified order and terminates on the first match<br>See [Routes](#routes) below for details.
 
 <a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
 
@@ -92,67 +92,67 @@ In addition to all arguments above, the following attributes are exported:
 
 A [`notification_parameters`](#notification-parameters) block supports the following:
 
-<a id="notification-parameters-custom"></a>&#x2022; [`custom`](#notification-parameters-custom) - Optional Block<br>Custom Group By. Specify list of custom labels to group/aggregate the alerts<br>See [Custom](#notification-parameters-custom) below.
+<a id="notification-parameters-custom"></a>&#x2022; [`custom`](#notification-parameters-custom) - Optional Block<br>Specify list of custom labels to group/aggregate the alerts<br>See [Custom](#notification-parameters-custom) below.
 
-<a id="notification-parameters-default"></a>&#x2022; [`default`](#notification-parameters-default) - Optional Block<br>Enable this option
+<a id="notification-parameters-default"></a>&#x2022; [`default`](#notification-parameters-default) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="notification-parameters-group-interval"></a>&#x2022; [`group_interval`](#notification-parameters-group-interval) - Optional String<br>Notify Interval for a Group. Group Interval is used to specify how long to wait before sending a notification about new alerts that are added to the group for which an initial notification has already been sent. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval defaults to '1m'
+<a id="notification-parameters-group-interval"></a>&#x2022; [`group_interval`](#notification-parameters-group-interval) - Optional String<br>Group Interval is used to specify how long to wait before sending a notification about new alerts that are added to the group for which an initial notification has already been sent. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval
 
-<a id="notification-parameters-group-wait"></a>&#x2022; [`group_wait`](#notification-parameters-group-wait) - Optional String<br>Wait to Notify. Time value used to specify how long to initially wait for an inhibiting alert to arrive or collect more alerts for the same group. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_wait defaults to '30s'
+<a id="notification-parameters-group-wait"></a>&#x2022; [`group_wait`](#notification-parameters-group-wait) - Optional String<br>Time value used to specify how long to initially wait for an inhibiting alert to arrive or collect more alerts for the same group. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_wait defaults to '30s'
 
-<a id="notification-parameters-individual"></a>&#x2022; [`individual`](#notification-parameters-individual) - Optional Block<br>Enable this option
+<a id="notification-parameters-individual"></a>&#x2022; [`individual`](#notification-parameters-individual) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="notification-parameters-repeat-interval"></a>&#x2022; [`repeat_interval`](#notification-parameters-repeat-interval) - Optional String<br>Notify Interval For a Alert. Repeat Interval is used to specify how long to wait before sending a notification again if it has already been sent successfully. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval defaults to '4h'
+<a id="notification-parameters-repeat-interval"></a>&#x2022; [`repeat_interval`](#notification-parameters-repeat-interval) - Optional String<br>Repeat Interval is used to specify how long to wait before sending a notification again if it has already been sent successfully. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval defaults to '4h'
 
-<a id="notification-parameters-ves-io-group"></a>&#x2022; [`ves_io_group`](#notification-parameters-ves-io-group) - Optional Block<br>Enable this option
+<a id="notification-parameters-ves-io-group"></a>&#x2022; [`ves_io_group`](#notification-parameters-ves-io-group) - Optional Block<br>Can be used for messages where no values are needed
 
 #### Notification Parameters Custom
 
 A [`custom`](#notification-parameters-custom) block (within [`notification_parameters`](#notification-parameters)) supports the following:
 
-<a id="notification-parameters-custom-labels"></a>&#x2022; [`labels`](#notification-parameters-custom-labels) - Optional List<br>Labels. Name of labels to group/aggregate the alerts
+<a id="notification-parameters-custom-labels"></a>&#x2022; [`labels`](#notification-parameters-custom-labels) - Optional List<br>Name of labels to group/aggregate the alerts
 
 #### Receivers
 
 A [`receivers`](#receivers) block supports the following:
 
-<a id="receivers-kind"></a>&#x2022; [`kind`](#receivers-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="receivers-kind"></a>&#x2022; [`kind`](#receivers-kind) - Optional String<br>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="receivers-name"></a>&#x2022; [`name`](#receivers-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="receivers-name"></a>&#x2022; [`name`](#receivers-name) - Optional String<br>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="receivers-namespace"></a>&#x2022; [`namespace`](#receivers-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="receivers-namespace"></a>&#x2022; [`namespace`](#receivers-namespace) - Optional String<br>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="receivers-tenant"></a>&#x2022; [`tenant`](#receivers-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="receivers-tenant"></a>&#x2022; [`tenant`](#receivers-tenant) - Optional String<br>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="receivers-uid"></a>&#x2022; [`uid`](#receivers-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
+<a id="receivers-uid"></a>&#x2022; [`uid`](#receivers-uid) - Optional String<br>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
 
 #### Routes
 
 A [`routes`](#routes) block supports the following:
 
-<a id="routes-alertname"></a>&#x2022; [`alertname`](#routes-alertname) - Optional String  Defaults to `SITE_CUSTOMER_TUNNEL_INTERFACE_DOWN`<br>Possible values are `SITE_CUSTOMER_TUNNEL_INTERFACE_DOWN`, `SITE_PHYSICAL_INTERFACE_DOWN`, `TUNNELS_TO_CUSTOMER_SITE_DOWN`, `SERVICE_SERVER_ERROR`, `SERVICE_CLIENT_ERROR`, `SERVICE_HEALTH_LOW`, `SERVICE_UNAVAILABLE`, `SERVICE_SERVER_ERROR_PER_SOURCE_SITE`, `SERVICE_CLIENT_ERROR_PER_SOURCE_SITE`, `SERVICE_ENDPOINT_HEALTHCHECK_FAILURE`, `SYNTHETIC_MONITOR_HEALTH_CRITICAL`, `MALICIOUS_USER_DETECTED`, `WAF_TOO_MANY_ATTACKS`, `API_SECURITY_TOO_MANY_ATTACKS`, `SERVICE_POLICY_TOO_MANY_ATTACKS`, `WAF_TOO_MANY_MALICIOUS_BOTS`, `BOT_DEFENSE_TOO_MANY_SECURITY_EVENTS`, `THREAT_CAMPAIGN`, `VES_CLIENT_SIDE_DEFENSE_SUSPICIOUS_DOMAIN`, `VES_CLIENT_SIDE_DEFENSE_SENSITIVE_FIELD_READ`, `ERROR_RATE_ANOMALY`, `REQUEST_RATE_ANOMALY`, `REQUEST_THROUGHPUT_ANOMALY`, `RESPONSE_LATENCY_ANOMALY`, `RESPONSE_THROUGHPUT_ANOMALY`, `TLS_AUTOMATIC_CERTIFICATE_RENEWAL_FAILURE`, `TLS_AUTOMATIC_CERTIFICATE_RENEWAL_STILL_FAILING`, `TLS_AUTOMATIC_CERTIFICATE_EXPIRED`, `TLS_CUSTOM_CERTIFICATE_EXPIRING`, `TLS_CUSTOM_CERTIFICATE_EXPIRING_SOON`, `TLS_CUSTOM_CERTIFICATE_EXPIRED`, `L7DDOS`, `DNS_ZONE_IGNORED_DUPLICATE_RECORD`, `API_SECURITY_UNUSED_API_DETECTED`, `API_SECURITY_SHADOW_API_DETECTED`, `API_SECURITY_SENSITIVE_DATA_IN_RESPONSE_DETECTED`, `API_SECURITY_RISK_SCORE_HIGH_DETECTED`, `ROUTED_DDOS_ALERT_NOTIFICATION`, `ROUTED_DDOS_MITIGATION_NOTIFICATION`<br>[Enum: SITE_CUSTOMER_TUNNEL_INTERFACE_DOWN|SITE_PHYSICAL_INTERFACE_DOWN|TUNNELS_TO_CUSTOMER_SITE_DOWN|SERVICE_SERVER_ERROR|SERVICE_CLIENT_ERROR|SERVICE_HEALTH_LOW|SERVICE_UNAVAILABLE|SERVICE_SERVER_ERROR_PER_SOURCE_SITE|SERVICE_CLIENT_ERROR_PER_SOURCE_SITE|SERVICE_ENDPOINT_HEALTHCHECK_FAILURE|SYNTHETIC_MONITOR_HEALTH_CRITICAL|MALICIOUS_USER_DETECTED|WAF_TOO_MANY_ATTACKS|API_SECURITY_TOO_MANY_ATTACKS|SERVICE_POLICY_TOO_MANY_ATTACKS|WAF_TOO_MANY_MALICIOUS_BOTS|BOT_DEFENSE_TOO_MANY_SECURITY_EVENTS|THREAT_CAMPAIGN|VES_CLIENT_SIDE_DEFENSE_SUSPICIOUS_DOMAIN|VES_CLIENT_SIDE_DEFENSE_SENSITIVE_FIELD_READ|ERROR_RATE_ANOMALY|REQUEST_RATE_ANOMALY|REQUEST_THROUGHPUT_ANOMALY|RESPONSE_LATENCY_ANOMALY|RESPONSE_THROUGHPUT_ANOMALY|TLS_AUTOMATIC_CERTIFICATE_RENEWAL_FAILURE|TLS_AUTOMATIC_CERTIFICATE_RENEWAL_STILL_FAILING|TLS_AUTOMATIC_CERTIFICATE_EXPIRED|TLS_CUSTOM_CERTIFICATE_EXPIRING|TLS_CUSTOM_CERTIFICATE_EXPIRING_SOON|TLS_CUSTOM_CERTIFICATE_EXPIRED|L7DDOS|DNS_ZONE_IGNORED_DUPLICATE_RECORD|API_SECURITY_UNUSED_API_DETECTED|API_SECURITY_SHADOW_API_DETECTED|API_SECURITY_SENSITIVE_DATA_IN_RESPONSE_DETECTED|API_SECURITY_RISK_SCORE_HIGH_DETECTED|ROUTED_DDOS_ALERT_NOTIFICATION|ROUTED_DDOS_MITIGATION_NOTIFICATION] AlertName. List of Alert Names Customer tunnel interface down Physical Interface down Tunnel Interfaces to Customer Site Down Virutal Host server error Virtual Host client error Service Health Low Service Unavailable Virtual Host server error Virtual Host client error Endpoint Healthcheck failure Synthetic monitor health critical Malicious user detected Virtual Host WAF security events detected Virtual Host API security events detected Virtual Host Service Policy security events detected Virtual Host Many Malicious Bots based WAF security events detected Virtual Host Many Malicious Bots based Bot Defense security events detected Virtual Host Many Threat campaign based WAF security events detected Suspicious domain identified by Client-Side Defense service Client-Side Defense has identified a suspicious script that is reading sensitive form field Error rate anomaly detected Request rate anomaly detected Request throughput anomaly detected Response latency anomaly detected Response throughput anomaly detected TLS Automatic Certificate renewal is failing TLS Automatic Certificate renewal is still failing after multiple retries TLS Automatic Certificate has expired TLS Custom Certificate will expire in less than 28 days TLS Custom Certificate will expire in less than 15 days TLS Custom Certificate has expired DDOS security event detected DNS Zone Ignored a Duplicate Record Create Request Unused APIs Detected Shadow APIs Detected Endpoints With Sensitive Data In Response Detected High Risk Score Endpoints Detected A routed DDOS traffic anomaly has been detected A routed DDOS mitigation has been implemented to block malicious traffic
+<a id="routes-alertname"></a>&#x2022; [`alertname`](#routes-alertname) - Optional String  Defaults to `SITE_CUSTOMER_TUNNEL_INTERFACE_DOWN`<br>Possible values are `SITE_CUSTOMER_TUNNEL_INTERFACE_DOWN`, `SITE_PHYSICAL_INTERFACE_DOWN`, `TUNNELS_TO_CUSTOMER_SITE_DOWN`, `SERVICE_SERVER_ERROR`, `SERVICE_CLIENT_ERROR`, `SERVICE_HEALTH_LOW`, `SERVICE_UNAVAILABLE`, `SERVICE_SERVER_ERROR_PER_SOURCE_SITE`, `SERVICE_CLIENT_ERROR_PER_SOURCE_SITE`, `SERVICE_ENDPOINT_HEALTHCHECK_FAILURE`, `SYNTHETIC_MONITOR_HEALTH_CRITICAL`, `MALICIOUS_USER_DETECTED`, `WAF_TOO_MANY_ATTACKS`, `API_SECURITY_TOO_MANY_ATTACKS`, `SERVICE_POLICY_TOO_MANY_ATTACKS`, `WAF_TOO_MANY_MALICIOUS_BOTS`, `BOT_DEFENSE_TOO_MANY_SECURITY_EVENTS`, `THREAT_CAMPAIGN`, `VES_CLIENT_SIDE_DEFENSE_SUSPICIOUS_DOMAIN`, `VES_CLIENT_SIDE_DEFENSE_SENSITIVE_FIELD_READ`, `ERROR_RATE_ANOMALY`, `REQUEST_RATE_ANOMALY`, `REQUEST_THROUGHPUT_ANOMALY`, `RESPONSE_LATENCY_ANOMALY`, `RESPONSE_THROUGHPUT_ANOMALY`, `TLS_AUTOMATIC_CERTIFICATE_RENEWAL_FAILURE`, `TLS_AUTOMATIC_CERTIFICATE_RENEWAL_STILL_FAILING`, `TLS_AUTOMATIC_CERTIFICATE_EXPIRED`, `TLS_CUSTOM_CERTIFICATE_EXPIRING`, `TLS_CUSTOM_CERTIFICATE_EXPIRING_SOON`, `TLS_CUSTOM_CERTIFICATE_EXPIRED`, `L7DDOS`, `DNS_ZONE_IGNORED_DUPLICATE_RECORD`, `API_SECURITY_UNUSED_API_DETECTED`, `API_SECURITY_SHADOW_API_DETECTED`, `API_SECURITY_SENSITIVE_DATA_IN_RESPONSE_DETECTED`, `API_SECURITY_RISK_SCORE_HIGH_DETECTED`, `ROUTED_DDOS_ALERT_NOTIFICATION`, `ROUTED_DDOS_MITIGATION_NOTIFICATION`<br>[Enum: SITE_CUSTOMER_TUNNEL_INTERFACE_DOWN|SITE_PHYSICAL_INTERFACE_DOWN|TUNNELS_TO_CUSTOMER_SITE_DOWN|SERVICE_SERVER_ERROR|SERVICE_CLIENT_ERROR|SERVICE_HEALTH_LOW|SERVICE_UNAVAILABLE|SERVICE_SERVER_ERROR_PER_SOURCE_SITE|SERVICE_CLIENT_ERROR_PER_SOURCE_SITE|SERVICE_ENDPOINT_HEALTHCHECK_FAILURE|SYNTHETIC_MONITOR_HEALTH_CRITICAL|MALICIOUS_USER_DETECTED|WAF_TOO_MANY_ATTACKS|API_SECURITY_TOO_MANY_ATTACKS|SERVICE_POLICY_TOO_MANY_ATTACKS|WAF_TOO_MANY_MALICIOUS_BOTS|BOT_DEFENSE_TOO_MANY_SECURITY_EVENTS|THREAT_CAMPAIGN|VES_CLIENT_SIDE_DEFENSE_SUSPICIOUS_DOMAIN|VES_CLIENT_SIDE_DEFENSE_SENSITIVE_FIELD_READ|ERROR_RATE_ANOMALY|REQUEST_RATE_ANOMALY|REQUEST_THROUGHPUT_ANOMALY|RESPONSE_LATENCY_ANOMALY|RESPONSE_THROUGHPUT_ANOMALY|TLS_AUTOMATIC_CERTIFICATE_RENEWAL_FAILURE|TLS_AUTOMATIC_CERTIFICATE_RENEWAL_STILL_FAILING|TLS_AUTOMATIC_CERTIFICATE_EXPIRED|TLS_CUSTOM_CERTIFICATE_EXPIRING|TLS_CUSTOM_CERTIFICATE_EXPIRING_SOON|TLS_CUSTOM_CERTIFICATE_EXPIRED|L7DDOS|DNS_ZONE_IGNORED_DUPLICATE_RECORD|API_SECURITY_UNUSED_API_DETECTED|API_SECURITY_SHADOW_API_DETECTED|API_SECURITY_SENSITIVE_DATA_IN_RESPONSE_DETECTED|API_SECURITY_RISK_SCORE_HIGH_DETECTED|ROUTED_DDOS_ALERT_NOTIFICATION|ROUTED_DDOS_MITIGATION_NOTIFICATION] List of Alert Names Customer tunnel interface down Physical Interface down Tunnel Interfaces to Customer Site Down Virutal Host server error Virtual Host client error Service Health Low Service Unavailable Virtual Host server error Virtual Host client error Endpoint Healthcheck failure Synthetic
 
-<a id="routes-alertname-regex"></a>&#x2022; [`alertname_regex`](#routes-alertname-regex) - Optional String<br>Matching RegEx of Alertname. Regular Expression match for the alertname
+<a id="routes-alertname-regex"></a>&#x2022; [`alertname_regex`](#routes-alertname-regex) - Optional String<br>Regular Expression match for the alertname
 
-<a id="routes-any"></a>&#x2022; [`any`](#routes-any) - Optional Block<br>Enable this option
+<a id="routes-any"></a>&#x2022; [`any`](#routes-any) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="routes-custom"></a>&#x2022; [`custom`](#routes-custom) - Optional Block<br>Custom Matcher. A set of matchers an alert has to fulfill to match the route<br>See [Custom](#routes-custom) below.
+<a id="routes-custom"></a>&#x2022; [`custom`](#routes-custom) - Optional Block<br>Set of matchers an alert has to fulfill to match the route<br>See [Custom](#routes-custom) below.
 
-<a id="routes-dont-send"></a>&#x2022; [`dont_send`](#routes-dont-send) - Optional Block<br>Enable this option
+<a id="routes-dont-send"></a>&#x2022; [`dont_send`](#routes-dont-send) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="routes-group"></a>&#x2022; [`group`](#routes-group) - Optional Block<br>Group Matcher. Select one or more known group names to match the incoming alert<br>See [Group](#routes-group) below.
+<a id="routes-group"></a>&#x2022; [`group`](#routes-group) - Optional Block<br>Select one or more known group names to match the incoming alert<br>See [Group](#routes-group) below.
 
-<a id="routes-notification-parameters"></a>&#x2022; [`notification_parameters`](#routes-notification-parameters) - Optional Block<br>Notification Parameters. Set of notification parameters to decide how and when the alert notifications should be sent to the receivers<br>See [Notification Parameters](#routes-notification-parameters) below.
+<a id="routes-notification-parameters"></a>&#x2022; [`notification_parameters`](#routes-notification-parameters) - Optional Block<br>Set of notification parameters to decide how and when the alert notifications should be sent to the receivers<br>See [Notification Parameters](#routes-notification-parameters) below.
 
-<a id="routes-send"></a>&#x2022; [`send`](#routes-send) - Optional Block<br>Enable this option
+<a id="routes-send"></a>&#x2022; [`send`](#routes-send) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="routes-severity"></a>&#x2022; [`severity`](#routes-severity) - Optional Block<br>Severity Matcher. Select one or more severity levels to match the incoming alert<br>See [Severity](#routes-severity) below.
+<a id="routes-severity"></a>&#x2022; [`severity`](#routes-severity) - Optional Block<br>Select one or more severity levels to match the incoming alert<br>See [Severity](#routes-severity) below.
 
 #### Routes Custom
 
 A [`custom`](#routes-custom) block (within [`routes`](#routes)) supports the following:
 
-<a id="routes-custom-alertlabel"></a>&#x2022; [`alertlabel`](#routes-custom-alertlabel) - Optional Block<br>AlertLabel. AlertLabel to configure the alert policy rule
+<a id="routes-custom-alertlabel"></a>&#x2022; [`alertlabel`](#routes-custom-alertlabel) - Optional Block<br>AlertLabel to configure the alert policy rule
 
 <a id="routes-custom-alertname"></a>&#x2022; [`alertname`](#routes-custom-alertname) - Optional Block<br>Label Matcher<br>See [Alertname](#routes-custom-alertname) below.
 
@@ -164,25 +164,25 @@ A [`custom`](#routes-custom) block (within [`routes`](#routes)) supports the fol
 
 An [`alertname`](#routes-custom-alertname) block (within [`routes.custom`](#routes-custom)) supports the following:
 
-<a id="routes-custom-alertname-exact-match"></a>&#x2022; [`exact_match`](#routes-custom-alertname-exact-match) - Optional String<br>Exact Match. Equality match value for the label
+<a id="routes-custom-alertname-exact-match"></a>&#x2022; [`exact_match`](#routes-custom-alertname-exact-match) - Optional String<br>Equality match value for the label
 
-<a id="routes-custom-alertname-regex-match"></a>&#x2022; [`regex_match`](#routes-custom-alertname-regex-match) - Optional String<br>RegEx Match. Regular expression match value for the label
+<a id="routes-custom-alertname-regex-match"></a>&#x2022; [`regex_match`](#routes-custom-alertname-regex-match) - Optional String<br>Regular expression match value for the label
 
 #### Routes Custom Group
 
 A [`group`](#routes-custom-group) block (within [`routes.custom`](#routes-custom)) supports the following:
 
-<a id="routes-custom-group-exact-match"></a>&#x2022; [`exact_match`](#routes-custom-group-exact-match) - Optional String<br>Exact Match. Equality match value for the label
+<a id="routes-custom-group-exact-match"></a>&#x2022; [`exact_match`](#routes-custom-group-exact-match) - Optional String<br>Equality match value for the label
 
-<a id="routes-custom-group-regex-match"></a>&#x2022; [`regex_match`](#routes-custom-group-regex-match) - Optional String<br>RegEx Match. Regular expression match value for the label
+<a id="routes-custom-group-regex-match"></a>&#x2022; [`regex_match`](#routes-custom-group-regex-match) - Optional String<br>Regular expression match value for the label
 
 #### Routes Custom Severity
 
 A [`severity`](#routes-custom-severity) block (within [`routes.custom`](#routes-custom)) supports the following:
 
-<a id="routes-custom-severity-exact-match"></a>&#x2022; [`exact_match`](#routes-custom-severity-exact-match) - Optional String<br>Exact Match. Equality match value for the label
+<a id="routes-custom-severity-exact-match"></a>&#x2022; [`exact_match`](#routes-custom-severity-exact-match) - Optional String<br>Equality match value for the label
 
-<a id="routes-custom-severity-regex-match"></a>&#x2022; [`regex_match`](#routes-custom-severity-regex-match) - Optional String<br>RegEx Match. Regular expression match value for the label
+<a id="routes-custom-severity-regex-match"></a>&#x2022; [`regex_match`](#routes-custom-severity-regex-match) - Optional String<br>Regular expression match value for the label
 
 #### Routes Group
 
@@ -194,25 +194,25 @@ A [`group`](#routes-group) block (within [`routes`](#routes)) supports the follo
 
 A [`notification_parameters`](#routes-notification-parameters) block (within [`routes`](#routes)) supports the following:
 
-<a id="routes-notification-parameters-custom"></a>&#x2022; [`custom`](#routes-notification-parameters-custom) - Optional Block<br>Custom Group By. Specify list of custom labels to group/aggregate the alerts<br>See [Custom](#routes-notification-parameters-custom) below.
+<a id="routes-notification-parameters-custom"></a>&#x2022; [`custom`](#routes-notification-parameters-custom) - Optional Block<br>Specify list of custom labels to group/aggregate the alerts<br>See [Custom](#routes-notification-parameters-custom) below.
 
-<a id="routes-notification-parameters-default"></a>&#x2022; [`default`](#routes-notification-parameters-default) - Optional Block<br>Enable this option
+<a id="routes-notification-parameters-default"></a>&#x2022; [`default`](#routes-notification-parameters-default) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="interval-b0bcc1"></a>&#x2022; [`group_interval`](#interval-b0bcc1) - Optional String<br>Notify Interval for a Group. Group Interval is used to specify how long to wait before sending a notification about new alerts that are added to the group for which an initial notification has already been sent. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval defaults to '1m'
+<a id="interval-b0bcc1"></a>&#x2022; [`group_interval`](#interval-b0bcc1) - Optional String<br>Group Interval is used to specify how long to wait before sending a notification about new alerts that are added to the group for which an initial notification has already been sent. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval
 
-<a id="wait-34a75e"></a>&#x2022; [`group_wait`](#wait-34a75e) - Optional String<br>Wait to Notify. Time value used to specify how long to initially wait for an inhibiting alert to arrive or collect more alerts for the same group. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_wait defaults to '30s'
+<a id="wait-34a75e"></a>&#x2022; [`group_wait`](#wait-34a75e) - Optional String<br>Time value used to specify how long to initially wait for an inhibiting alert to arrive or collect more alerts for the same group. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_wait defaults to '30s'
 
-<a id="individual-096c32"></a>&#x2022; [`individual`](#individual-096c32) - Optional Block<br>Enable this option
+<a id="individual-096c32"></a>&#x2022; [`individual`](#individual-096c32) - Optional Block<br>Can be used for messages where no values are needed
 
-<a id="interval-4b248a"></a>&#x2022; [`repeat_interval`](#interval-4b248a) - Optional String<br>Notify Interval For a Alert. Repeat Interval is used to specify how long to wait before sending a notification again if it has already been sent successfully. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval defaults to '4h'
+<a id="interval-4b248a"></a>&#x2022; [`repeat_interval`](#interval-4b248a) - Optional String<br>Repeat Interval is used to specify how long to wait before sending a notification again if it has already been sent successfully. Format: [0-9]\[smhd], where s - seconds, m - minutes, h - hours, d - days If not specified, group_interval defaults to '4h'
 
-<a id="group-12b5ad"></a>&#x2022; [`ves_io_group`](#group-12b5ad) - Optional Block<br>Enable this option
+<a id="group-12b5ad"></a>&#x2022; [`ves_io_group`](#group-12b5ad) - Optional Block<br>Can be used for messages where no values are needed
 
 #### Routes Notification Parameters Custom
 
 A [`custom`](#routes-notification-parameters-custom) block (within [`routes.notification_parameters`](#routes-notification-parameters)) supports the following:
 
-<a id="labels-bf3226"></a>&#x2022; [`labels`](#labels-bf3226) - Optional List<br>Labels. Name of labels to group/aggregate the alerts
+<a id="labels-bf3226"></a>&#x2022; [`labels`](#labels-bf3226) - Optional List<br>Name of labels to group/aggregate the alerts
 
 #### Routes Severity
 

package/dist/docs/resources/alert_receiver.md

@@ -60,11 +60,11 @@ resource "f5xc_alert_receiver" "example" {
 
 -> **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="opsgenie"></a>[`opsgenie`](#opsgenie) - Optional Block<br>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 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 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.
+<br><br>&#x2022; <a id="webhook"></a>[`webhook`](#webhook) - Optional Block<br>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.
 
@@ -86,109 +86,109 @@ An [`email`](#email) block supports the following:
 
 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-api-key"></a>&#x2022; [`api_key`](#opsgenie-api-key) - Optional Block<br>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
+<a id="opsgenie-url"></a>&#x2022; [`url`](#opsgenie-url) - Optional String<br>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-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#opsgenie-api-key-blindfold-secret-info) - Optional Block<br>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.
+<a id="opsgenie-api-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#opsgenie-api-key-clear-secret-info) - Optional Block<br>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="provider-ecad4c"></a>&#x2022; [`decryption_provider`](#provider-ecad4c) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+<a id="provider-ecad4c"></a>&#x2022; [`decryption_provider`](#provider-ecad4c) - Optional String<br>Name of the Secret Management Access object that contains information about the backend Secret Management service
 
-<a id="location-8a2de8"></a>&#x2022; [`location`](#location-8a2de8) - 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="location-8a2de8"></a>&#x2022; [`location`](#location-8a2de8) - Optional String<br>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="provider-135329"></a>&#x2022; [`store_provider`](#provider-135329) - 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:///
+<a id="provider-135329"></a>&#x2022; [`store_provider`](#provider-135329) - Optional String<br>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="ref-3e8ac3"></a>&#x2022; [`provider_ref`](#ref-3e8ac3) - 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="ref-3e8ac3"></a>&#x2022; [`provider_ref`](#ref-3e8ac3) - Optional String<br>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
+<a id="opsgenie-api-key-clear-secret-info-url"></a>&#x2022; [`url`](#opsgenie-api-key-clear-secret-info-url) - Optional String<br>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-routing-key"></a>&#x2022; [`routing_key`](#pagerduty-routing-key) - Optional Block<br>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
+<a id="pagerduty-url"></a>&#x2022; [`url`](#pagerduty-url) - Optional String<br>URL to send API requests to
 
 #### Pagerduty Routing Key
 
 A [`routing_key`](#pagerduty-routing-key) block (within [`pagerduty`](#pagerduty)) supports the following:
 
-<a id="info-338522"></a>&#x2022; [`blindfold_secret_info`](#info-338522) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-338522) below.
+<a id="info-338522"></a>&#x2022; [`blindfold_secret_info`](#info-338522) - Optional Block<br>BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-338522) 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.
+<a id="pagerduty-routing-key-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#pagerduty-routing-key-clear-secret-info) - Optional Block<br>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`](#info-338522) block (within [`pagerduty.routing_key`](#pagerduty-routing-key)) supports the following:
 
-<a id="provider-dbb438"></a>&#x2022; [`decryption_provider`](#provider-dbb438) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+<a id="provider-dbb438"></a>&#x2022; [`decryption_provider`](#provider-dbb438) - Optional String<br>Name of the Secret Management Access object that contains information about the backend Secret Management service
 
-<a id="location-6bc59d"></a>&#x2022; [`location`](#location-6bc59d) - 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="location-6bc59d"></a>&#x2022; [`location`](#location-6bc59d) - Optional String<br>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="provider-273f68"></a>&#x2022; [`store_provider`](#provider-273f68) - 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:///
+<a id="provider-273f68"></a>&#x2022; [`store_provider`](#provider-273f68) - Optional String<br>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="ref-67e62e"></a>&#x2022; [`provider_ref`](#ref-67e62e) - 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="ref-67e62e"></a>&#x2022; [`provider_ref`](#ref-67e62e) - Optional String<br>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="url-13757a"></a>&#x2022; [`url`](#url-13757a) - 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
+<a id="url-13757a"></a>&#x2022; [`url`](#url-13757a) - Optional String<br>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-channel"></a>&#x2022; [`channel`](#slack-channel) - Optional String<br>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.
+<a id="slack-url"></a>&#x2022; [`url`](#slack-url) - Optional Block<br>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-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#slack-url-blindfold-secret-info) - Optional Block<br>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.
+<a id="slack-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#slack-url-clear-secret-info) - Optional Block<br>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="provider-c71574"></a>&#x2022; [`decryption_provider`](#provider-c71574) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+<a id="provider-c71574"></a>&#x2022; [`decryption_provider`](#provider-c71574) - Optional String<br>Name of the Secret Management Access object that contains information about the backend Secret Management service
 
-<a id="location-d25688"></a>&#x2022; [`location`](#location-d25688) - 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="location-d25688"></a>&#x2022; [`location`](#location-d25688) - Optional String<br>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="provider-14e49e"></a>&#x2022; [`store_provider`](#provider-14e49e) - 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:///
+<a id="provider-14e49e"></a>&#x2022; [`store_provider`](#provider-14e49e) - Optional String<br>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="ref-008757"></a>&#x2022; [`provider_ref`](#ref-008757) - 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="ref-008757"></a>&#x2022; [`provider_ref`](#ref-008757) - Optional String<br>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
+<a id="slack-url-clear-secret-info-url"></a>&#x2022; [`url`](#slack-url-clear-secret-info-url) - Optional String<br>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]
+<a id="sms-contact-number"></a>&#x2022; [`contact_number`](#sms-contact-number) - Optional String<br>Contact number of the user in ITU E.164 format [+]\[country code][subscriber number including area code]
 
 #### Timeouts
 
@@ -208,7 +208,7 @@ 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.
+<a id="webhook-url"></a>&#x2022; [`url`](#webhook-url) - Optional Block<br>SecretType is used in an object to indicate a sensitive/confidential field<br>See [URL](#webhook-url) below.
 
 #### Webhook HTTP Config
 
@@ -216,33 +216,33 @@ A [`http_config`](#webhook-http-config) block (within [`webhook`](#webhook)) sup
 
 <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-basic-auth"></a>&#x2022; [`basic_auth`](#webhook-http-config-basic-auth) - Optional Block<br>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-follow-redirects"></a>&#x2022; [`follow_redirects`](#webhook-http-config-follow-redirects) - Optional Bool<br>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-authorization"></a>&#x2022; [`no_authorization`](#webhook-http-config-no-authorization) - Optional Block<br>Can be used for messages where no values are needed
 
-<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-no-tls"></a>&#x2022; [`no_tls`](#webhook-http-config-no-tls) - Optional Block<br>Can be used for messages where no values are needed
 
-<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.
+<a id="webhook-http-config-use-tls"></a>&#x2022; [`use_tls`](#webhook-http-config-use-tls) - Optional Block<br>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.
+<a id="webhook-http-config-auth-token-token"></a>&#x2022; [`token`](#webhook-http-config-auth-token-token) - Optional Block<br>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="info-cf9560"></a>&#x2022; [`blindfold_secret_info`](#info-cf9560) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-cf9560) below.
+<a id="info-cf9560"></a>&#x2022; [`blindfold_secret_info`](#info-cf9560) - Optional Block<br>BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-cf9560) below.
 
-<a id="info-a3e44e"></a>&#x2022; [`clear_secret_info`](#info-a3e44e) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-a3e44e) below.
+<a id="info-a3e44e"></a>&#x2022; [`clear_secret_info`](#info-a3e44e) - Optional Block<br>ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-a3e44e) below.
 
 #### Webhook HTTP Config Auth Token Token Blindfold Secret Info
 
@@ -256,17 +256,17 @@ A [`token`](#webhook-http-config-auth-token-token) block (within [`webhook.http_
 
 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-password"></a>&#x2022; [`password`](#webhook-http-config-basic-auth-password) - Optional Block<br>SecretType is used in an object to indicate a sensitive/confidential field<br>See [Password](#webhook-http-config-basic-auth-password) below.
 
-<a id="name-8da031"></a>&#x2022; [`user_name`](#name-8da031) - Optional String<br>User Name. HTTP Basic Auth User Name
+<a id="name-8da031"></a>&#x2022; [`user_name`](#name-8da031) - Optional String<br>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="info-f1b0b0"></a>&#x2022; [`blindfold_secret_info`](#info-f1b0b0) - Optional Block<br>Blindfold Secret. BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-f1b0b0) below.
+<a id="info-f1b0b0"></a>&#x2022; [`blindfold_secret_info`](#info-f1b0b0) - Optional Block<br>BlindfoldSecretInfoType specifies information about the Secret managed by F5XC Secret Management<br>See [Blindfold Secret Info](#info-f1b0b0) below.
 
-<a id="info-71ce91"></a>&#x2022; [`clear_secret_info`](#info-71ce91) - Optional Block<br>In-Clear Secret. ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-71ce91) below.
+<a id="info-71ce91"></a>&#x2022; [`clear_secret_info`](#info-71ce91) - Optional Block<br>ClearSecretInfoType specifies information about the Secret that is not encrypted<br>See [Clear Secret Info](#info-71ce91) below.
 
 #### Webhook HTTP Config Basic Auth Password Blindfold Secret Info
 
@@ -290,17 +290,17 @@ A [`client_cert_obj`](#webhook-http-config-client-cert-obj) block (within [`webh
 
 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-disable-sni"></a>&#x2022; [`disable_sni`](#webhook-http-config-use-tls-disable-sni) - Optional Block<br>Can be used for messages where no values are needed
 
-<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-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] 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-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] 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-sni"></a>&#x2022; [`sni`](#webhook-http-config-use-tls-sni) - Optional String<br>SNI value to be used
 
 <a id="verification-b3e5f0"></a>&#x2022; [`use_server_verification`](#verification-b3e5f0) - Optional Block<br>TLS Validation Context for Servers. Upstream TLS Validation Context<br>See [Use Server Verification](#verification-b3e5f0) below.
 
-<a id="trusted-ca-138b8e"></a>&#x2022; [`volterra_trusted_ca`](#trusted-ca-138b8e) - Optional Block<br>Enable this option
+<a id="trusted-ca-138b8e"></a>&#x2022; [`volterra_trusted_ca`](#trusted-ca-138b8e) - Optional Block<br>Can be used for messages where no values are needed
 
 #### Webhook HTTP Config Use TLS Use Server Verification
 
@@ -318,27 +318,27 @@ An [`use_tls`](#webhook-http-config-use-tls) block (within [`webhook.http_config
 
 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-blindfold-secret-info"></a>&#x2022; [`blindfold_secret_info`](#webhook-url-blindfold-secret-info) - Optional Block<br>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.
+<a id="webhook-url-clear-secret-info"></a>&#x2022; [`clear_secret_info`](#webhook-url-clear-secret-info) - Optional Block<br>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="provider-f9e163"></a>&#x2022; [`decryption_provider`](#provider-f9e163) - Optional String<br>Decryption Provider. Name of the Secret Management Access object that contains information about the backend Secret Management service
+<a id="provider-f9e163"></a>&#x2022; [`decryption_provider`](#provider-f9e163) - Optional String<br>Name of the Secret Management Access object that contains information about the backend Secret Management service
 
-<a id="location-3da6df"></a>&#x2022; [`location`](#location-3da6df) - 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="location-3da6df"></a>&#x2022; [`location`](#location-3da6df) - Optional String<br>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="provider-dc4a55"></a>&#x2022; [`store_provider`](#provider-dc4a55) - 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:///
+<a id="provider-dc4a55"></a>&#x2022; [`store_provider`](#provider-dc4a55) - Optional String<br>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="ref-16bc23"></a>&#x2022; [`provider_ref`](#ref-16bc23) - 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="ref-16bc23"></a>&#x2022; [`provider_ref`](#ref-16bc23) - Optional String<br>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
+<a id="webhook-url-clear-secret-info-url"></a>&#x2022; [`url`](#webhook-url-clear-secret-info-url) - Optional String<br>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
 
 ---