@robinmordasiewicz/f5xc-terraform-mcp 3.0.1 → 3.1.0

package/dist/docs/resources/contact.md

@@ -0,0 +1,187 @@
+---
+page_title: "f5xc_contact Resource - terraform-provider-f5xc"
+subcategory: "Organization"
+description: |-
+  Manages new customer's contact detail record with us, including address and phone number. in F5 Distributed Cloud.
+---
+
+# f5xc_contact (Resource)
+
+Manages new customer's contact detail record with us, including address and phone number. in F5 Distributed Cloud.
+
+~> **Note** For more information about this resource, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
+
+## Example Usage
+
+```terraform
+# Contact Resource Example
+# Manages new customer's contact detail record with us, including address and phone number. in F5 Distributed Cloud.
+
+# Basic Contact configuration
+resource "f5xc_contact" "example" {
+  name      = "example-contact"
+  namespace = "staging"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the Contact. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the Contact 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="address1"></a>&#x2022; [`address1`](#address1) - Optional String<br>Address Line 1
+
+<a id="address2"></a>&#x2022; [`address2`](#address2) - Optional String<br>Address Line 2
+
+<a id="city"></a>&#x2022; [`city`](#city) - Optional String<br>City
+
+<a id="contact-type"></a>&#x2022; [`contact_type`](#contact-type) - Optional String  Defaults to `MAILING`<br>Possible values are `MAILING`, `BILLING`, `PAYMENT`<br>[Enum: MAILING|BILLING|PAYMENT] Contact Type. Determines the contact type Indicates snail mail address (used for correspondence) Indicates billing address (this address will appear on invoices) Indicates contact used for a payment method (this address is used when charging a payment method)
+
+<a id="country"></a>&#x2022; [`country`](#country) - Optional String<br>Country
+
+<a id="county"></a>&#x2022; [`county`](#county) - Optional String<br>County
+
+<a id="phone-number"></a>&#x2022; [`phone_number`](#phone-number) - Optional String<br>Phone Number
+
+<a id="state"></a>&#x2022; [`state`](#state) - Optional String<br>State
+
+<a id="state-code"></a>&#x2022; [`state_code`](#state-code) - Optional String<br>State Code
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
+
+<a id="zip-code"></a>&#x2022; [`zip_code`](#zip-code) - Optional String<br>ZIP code
+
+### 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
+
+---
+
+#### 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
+
+---
+
+## Common Types
+
+The following type definitions are used throughout this resource. See the full definition here rather than repeated inline.
+
+### Object Reference {#common-object-reference}
+
+Object references establish a direct reference from one configuration object to another in F5 Distributed Cloud. References use the format `tenant/namespace/name`.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `name` | String | Name of the referenced object |
+| `namespace` | String | Namespace containing the referenced object |
+| `tenant` | String | Tenant of the referenced object (system-managed) |
+
+### Transformers {#common-transformers}
+
+Transformers apply transformations to input values before matching. Multiple transformers can be applied in order.
+
+| Value | Description |
+| ----- | ----------- |
+| `LOWER_CASE` | Convert to lowercase |
+| `UPPER_CASE` | Convert to uppercase |
+| `BASE64_DECODE` | Decode base64 content |
+| `NORMALIZE_PATH` | Normalize URL path |
+| `REMOVE_WHITESPACE` | Remove whitespace characters |
+| `URL_DECODE` | Decode URL-encoded characters |
+| `TRIM_LEFT` | Trim leading whitespace |
+| `TRIM_RIGHT` | Trim trailing whitespace |
+| `TRIM` | Trim both leading and trailing whitespace |
+
+### HTTP Methods {#common-http-methods}
+
+HTTP methods used for request matching.
+
+| Value | Description |
+| ----- | ----------- |
+| `ANY` | Match any HTTP method |
+| `GET` | HTTP GET request |
+| `HEAD` | HTTP HEAD request |
+| `POST` | HTTP POST request |
+| `PUT` | HTTP PUT request |
+| `DELETE` | HTTP DELETE request |
+| `CONNECT` | HTTP CONNECT request |
+| `OPTIONS` | HTTP OPTIONS request |
+| `TRACE` | HTTP TRACE request |
+| `PATCH` | HTTP PATCH request |
+| `COPY` | HTTP COPY request (WebDAV) |
+
+### TLS Fingerprints {#common-tls-fingerprints}
+
+TLS fingerprint categories for malicious client detection.
+
+| Value | Description |
+| ----- | ----------- |
+| `TLS_FINGERPRINT_NONE` | No fingerprint matching |
+| `ANY_MALICIOUS_FINGERPRINT` | Match any known malicious fingerprint |
+| `ADWARE` | Adware-associated fingerprints |
+| `DRIDEX` | Dridex malware fingerprints |
+| `GOOTKIT` | Gootkit malware fingerprints |
+| `RANSOMWARE` | Ransomware-associated fingerprints |
+| `TRICKBOT` | Trickbot malware fingerprints |
+
+### IP Threat Categories {#common-ip-threat-categories}
+
+IP address threat categories for security filtering.
+
+| Value | Description |
+| ----- | ----------- |
+| `SPAM_SOURCES` | Known spam sources |
+| `WINDOWS_EXPLOITS` | Windows exploit sources |
+| `WEB_ATTACKS` | Web attack sources |
+| `BOTNETS` | Known botnet IPs |
+| `SCANNERS` | Network scanner IPs |
+| `REPUTATION` | Poor reputation IPs |
+| `PHISHING` | Phishing-related IPs |
+| `PROXY` | Anonymous proxy IPs |
+| `MOBILE_THREATS` | Mobile threat sources |
+| `TOR_PROXY` | Tor exit nodes |
+| `DENIAL_OF_SERVICE` | DoS attack sources |
+| `NETWORK` | Known bad network ranges |
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_contact.example system/example
+```

package/dist/docs/resources/customer_support.md

@@ -0,0 +1,253 @@
+---
+page_title: "f5xc_customer_support Resource - terraform-provider-f5xc"
+subcategory: "Organization"
+description: |-
+  Manages new customer support ticket in our customer support provider system. in F5 Distributed Cloud.
+---
+
+# f5xc_customer_support (Resource)
+
+Manages new customer support ticket in our customer support provider system. in F5 Distributed Cloud.
+
+~> **Note** For more information about this resource, please refer to the [F5 XC API Documentation](https://docs.cloud.f5.com/docs/api/).
+
+## Example Usage
+
+```terraform
+# Customer Support Resource Example
+# Manages new customer support ticket in our customer support provider system. in F5 Distributed Cloud.
+
+# Basic Customer Support configuration
+resource "f5xc_customer_support" "example" {
+  name      = "example-customer-support"
+  namespace = "staging"
+
+  labels = {
+    environment = "production"
+    managed_by  = "terraform"
+  }
+
+  annotations = {
+    "owner" = "platform-team"
+  }
+
+  # Resource-specific configuration
+  # Comments. Comments are all public comments on an issue. T...
+  comments {
+    # Configure comments settings
+  }
+  # Attachments details. Information about any attachments (s...
+  attachments_info {
+    # Configure attachments_info settings
+  }
+  # Ticket which this one relates to. Optional reference to a...
+  relates_to {
+    # Configure relates_to settings
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Argument Reference
+
+### Metadata Argument Reference
+
+<a id="name"></a>&#x2022; [`name`](#name) - Required String<br>Name of the Customer Support. Must be unique within the namespace
+
+<a id="namespace"></a>&#x2022; [`namespace`](#namespace) - Required String<br>Namespace where the Customer Support 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="category"></a>&#x2022; [`category`](#category) - Optional String<br>Category. ticket area further narrows down the ticket - infrastructure, application, dashboards can be examples
+
+<a id="comments"></a>&#x2022; [`comments`](#comments) - Optional Block<br>Comments. Comments are all public comments on an issue. They'RE usually conversation between the support personnel and the customer<br>See [Comments](#comments) below for details.
+
+<a id="description-spec"></a>&#x2022; [`description_spec`](#description-spec) - Optional String<br>Description. customer's description of the issue (free text)
+
+<a id="ongoing"></a>&#x2022; [`ongoing`](#ongoing) - Optional Bool<br>Ongoing. Ongoing is a flag that indicates whether the issue is ongoing or not
+
+<a id="priority"></a>&#x2022; [`priority`](#priority) - Optional String  Defaults to `PRIORITY_UNKNOWN`<br>Possible values are `PRIORITY_UNKNOWN`, `PRIORITY_NORMAL`, `PRIORITY_HIGH`, `PRIORITY_URGENT`<br>[Enum: PRIORITY_UNKNOWN|PRIORITY_NORMAL|PRIORITY_HIGH|PRIORITY_URGENT] Priority. Support ticket priority helps understand importance of the ticket and focus more on more critical issues. Unknown/empty priority Normal priority issue High priority issue Urgent priority issue
+
+<a id="product-data"></a>&#x2022; [`product_data`](#product-data) - Optional String<br>Product Data. Product data is a free text field that can be used to describe the issue in more detail
+
+<a id="relates-to"></a>&#x2022; [`relates_to`](#relates-to) - Optional Block<br>Ticket which this one relates to. Optional reference to any original ticket in case the ticket being created is a followup<br>See [Relates To](#relates-to) below for details.
+
+<a id="service"></a>&#x2022; [`service`](#service) - Optional String  Defaults to `SS_UNKNOWN`<br>Possible values are `SS_UNKNOWN`, `SS_ACCOUNT_PROTECTION`, `SS_ADMINISTRATION`, `SS_APPLICATION_TRAFFIC_INSIGHT`, `SS_AUDIT_LOGS_AND_ALERTS`, `SS_AUTHENTICATION_INTELLIGENCE`, `SS_BILLING`, `SS_CLIENT_SIDE_DEFENSE`, `SS_CLOUD_AND_EDGE_SITES`, `SS_DDOS_AND_TRANSIT_SERVICES`, `SS_DISTRIBUTED_APPS`, `SS_DNS_MANAGEMENT`, `SS_LOAD_BALANCERS`, `SS_SHARED_CONFIGURATION`, `SS_WEB_APP_AND_API_PROTECTION`, `SS_OTHER`, `SS_BOT_DEFENSE`, `SS_CDN`, `SS_OBSERVABILITY`, `SS_DELEGATED_ACCESS`, `SS_MULTI_CLOUD_NETWORK_CONNECT`, `SS_MULTI_CLOUD_APP_CONNECT`, `SS_BIG_IP_APM`, `SS_DATA_INTELLIGENCE`, `SS_NGINX_ONE`, `SS_WEB_APP_SCANNING`, `SS_ROUTED_DDOS`, `SS_MOBILE_APP_SHIELD`<br>[Enum: SS_UNKNOWN|SS_ACCOUNT_PROTECTION|SS_ADMINISTRATION|SS_APPLICATION_TRAFFIC_INSIGHT|SS_AUDIT_LOGS_AND_ALERTS|SS_AUTHENTICATION_INTELLIGENCE|SS_BILLING|SS_CLIENT_SIDE_DEFENSE|SS_CLOUD_AND_EDGE_SITES|SS_DDOS_AND_TRANSIT_SERVICES|SS_DISTRIBUTED_APPS|SS_DNS_MANAGEMENT|SS_LOAD_BALANCERS|SS_SHARED_CONFIGURATION|SS_WEB_APP_AND_API_PROTECTION|SS_OTHER|SS_BOT_DEFENSE|SS_CDN|SS_OBSERVABILITY|SS_DELEGATED_ACCESS|SS_MULTI_CLOUD_NETWORK_CONNECT|SS_MULTI_CLOUD_APP_CONNECT|SS_BIG_IP_APM|SS_DATA_INTELLIGENCE|SS_NGINX_ONE|SS_WEB_APP_SCANNING|SS_ROUTED_DDOS|SS_MOBILE_APP_SHIELD] Support Service. Indicates the list of support service Unknown Support Service Account Protection Support Service Administration Support Service Application Traffic Insight Support Service Audit Logs & Alerts Support Service Authentication Intelligence Support Service Billing Support Service Client Side Defense Support Service Cloud & Edge Sites Support Service deprecated: use SS_MULTI_CLOUD_NETWORK_CONNECT instead DDOS & Transit Support Service Deprecated: use SS_ROUTED_DDOS instead Distributed Apps Support Service DNS Management Support Service LoadBalancers Support Service deprecated: use SS_MULTI_CLOUD_APP_CONNECT instead Shared Configuration Support Service Web App & API Protection Support Service Other Support Service Bot Defense Support Service Content delivery network Support Service Observability Support Service Delegated Access Support Service Networking & security across clouds, edge and on-premises Connect apps across clouds, edge and on-premises using Load Balancers BIG-IP Access Policy Manager (APM) Data Intelligence Support Service NGINX One Support Service Web App Scanning Support Service Routed DDOS Support Service Mobile App Shield protects mobile apps from reverse engineering, tampering and malware
+
+<a id="status"></a>&#x2022; [`status`](#status) - Optional String  Defaults to `STATUS_UNKNOWN`<br>Possible values are `STATUS_UNKNOWN`, `STATUS_NEW`, `STATUS_OPEN`, `STATUS_PENDING`, `STATUS_ONHOLD`, `STATUS_SOLVED`, `STATUS_CLOSED`, `STATUS_FAILED`<br>[Enum: STATUS_UNKNOWN|STATUS_NEW|STATUS_OPEN|STATUS_PENDING|STATUS_ONHOLD|STATUS_SOLVED|STATUS_CLOSED|STATUS_FAILED] Support Ticket Status. State of the ticket so the customers know if the problem is being looked into Unknown or empty support ticket status Indicates a new ticket, waiting to be assigned to an agent Indicates an open issues, actively being looked into Indicates a pending issue, an open issue not actively being looked into Indicates on issue that on-hold, waiting for more information Indicates a solved issue, waiting for customer's confirmation Indicates a closed issue, resolved and customer approved Indicates a failed ticket, a failed ticket didn't make it into Zendesk and a customer should create new one instead
+
+<a id="subject"></a>&#x2022; [`subject`](#subject) - Optional String<br>Subject. subject of the ticket
+
+<a id="timeline"></a>&#x2022; [`timeline`](#timeline) - Optional String<br>Timeline. Timeline is a free text field that can be used to describe the issue in more detail
+
+<a id="timeouts"></a>&#x2022; [`timeouts`](#timeouts) - Optional Block<br>See [Timeouts](#timeouts) below for details.
+
+<a id="topic"></a>&#x2022; [`topic`](#topic) - Optional String  Defaults to `TOPIC_UNKNOWN`<br>Possible values are `TOPIC_UNKNOWN`, `ACCOUNT_SUPPORT_TOPIC_ACCESS_REQUEST`, `ACCOUNT_SUPPORT_TOPIC_ACCOUNT`, `ACCOUNT_SUPPORT_TOPIC_BILLING`, `ACCOUNT_SUPPORT_TOPIC_BILLING_PLAN_CHANGE`, `ACCOUNT_SUPPORT_TOPIC_PUBLIC_IP`, `ACCOUNT_SUPPORT_TOPIC_QUOTA_INCREASE`, `ACCOUNT_SUPPORT_TOPIC_RMA`, `ACCOUNT_SUPPORT_TOPIC_TAX_EXEMPT_VERIFICATION`, `ACCOUNT_SUPPORT_TOPIC_OTHERS`, `TECHNICAL_SUPPORT_TOPIC_CONFIGURATION_CHANGES`, `TECHNICAL_SUPPORT_TOPIC_ERROR_MESSAGE`, `TECHNICAL_SUPPORT_TOPIC_NEW_CONFIGURATION`, `TECHNICAL_SUPPORT_TOPIC_PRODUCT_QUESTION`, `TECHNICAL_SUPPORT_TOPIC_TROUBLESHOOTING`, `TECHNICAL_SUPPORT_TOPIC_OTHERS`, `INCIDENT_SUPPORT_TOPIC_LATENCY`, `INCIDENT_SUPPORT_TOPIC_PERFORMANCE_DEGRADATION`, `INCIDENT_SUPPORT_TOPIC_PARTIAL_OUTAGE`, `INCIDENT_SUPPORT_TOPIC_COMPLETE_OUTAGE`, `INCIDENT_SUPPORT_TOPIC_OTHERS`, `TASK_TOPIC_PLAN_TRANSITION`, `PROBLEM_TOPIC_SUPPORT_ALERT`, `QUESTION_TOPIC_INFRASTRUCTURE`, `TECHNICAL_SUPPORT_TOPIC_DELEGATED_DOMAIN_MIGRATION`<br>[Enum: TOPIC_UNKNOWN|ACCOUNT_SUPPORT_TOPIC_ACCESS_REQUEST|ACCOUNT_SUPPORT_TOPIC_ACCOUNT|ACCOUNT_SUPPORT_TOPIC_BILLING|ACCOUNT_SUPPORT_TOPIC_BILLING_PLAN_CHANGE|ACCOUNT_SUPPORT_TOPIC_PUBLIC_IP|ACCOUNT_SUPPORT_TOPIC_QUOTA_INCREASE|ACCOUNT_SUPPORT_TOPIC_RMA|ACCOUNT_SUPPORT_TOPIC_TAX_EXEMPT_VERIFICATION|ACCOUNT_SUPPORT_TOPIC_OTHERS|TECHNICAL_SUPPORT_TOPIC_CONFIGURATION_CHANGES|TECHNICAL_SUPPORT_TOPIC_ERROR_MESSAGE|TECHNICAL_SUPPORT_TOPIC_NEW_CONFIGURATION|TECHNICAL_SUPPORT_TOPIC_PRODUCT_QUESTION|TECHNICAL_SUPPORT_TOPIC_TROUBLESHOOTING|TECHNICAL_SUPPORT_TOPIC_OTHERS|INCIDENT_SUPPORT_TOPIC_LATENCY|INCIDENT_SUPPORT_TOPIC_PERFORMANCE_DEGRADATION|INCIDENT_SUPPORT_TOPIC_PARTIAL_OUTAGE|INCIDENT_SUPPORT_TOPIC_COMPLETE_OUTAGE|INCIDENT_SUPPORT_TOPIC_OTHERS|TASK_TOPIC_PLAN_TRANSITION|PROBLEM_TOPIC_SUPPORT_ALERT|QUESTION_TOPIC_INFRASTRUCTURE|TECHNICAL_SUPPORT_TOPIC_DELEGATED_DOMAIN_MIGRATION] Support Topic. Support Topic indicates the list of topics for service tickets Unknown/empty priority ACCOUNT_SUPPORT_TOPIC_ACCESS_REQUEST ACCOUNT_SUPPORT_TOPIC_ACCOUNT ACCOUNT_SUPPORT_TOPIC_BILLING ACCOUNT_SUPPORT_TOPIC_BILLING_PLAN_CHANGE ACCOUNT_SUPPORT_TOPIC_PUBLIC_IP ACCOUNT_SUPPORT_TOPIC_QUOTA_INCREASE ACCOUNT_SUPPORT_TOPIC_RMA ACCOUNT_SUPPORT_TOPIC_TAX_EXEMPT_VERIFICATION ACCOUNT_SUPPORT_TOPIC_OTHERS TECHNICAL_SUPPORT_TOPIC_CONFIGURATION_CHANGES TECHNICAL_SUPPORT_TOPIC_ERROR_MESSAGE TECHNICAL_SUPPORT_TOPIC_NEW_CONFIGURATION TECHNICAL_SUPPORT_TOPIC_PRODUCT_QUESTION TECHNICAL_SUPPORT_TOPIC_TROUBLESHOOTING TECHNICAL_SUPPORT_TOPIC_OTHERS INCIDENT_SUPPORT_TOPIC_LATENCY INCIDENT_SUPPORT_TOPIC_PERFORMANCE_DEGRADATION INCIDENT_SUPPORT_TOPIC_PARTIAL_OUTAGE INCIDENT_SUPPORT_TOPIC_COMPLETE_OUTAGE INCIDENT_SUPPORT_TOPIC_OTHERS TASK_TOPIC_PLAN_TRANSITION PROBLEM_TOPIC_SUPPORT_ALERT QUESTION_TOPIC_INFRASTRUCTURE TECHNICAL_SUPPORT_TOPIC_DELEGATED_DOMAIN_MIGRATION
+
+<a id="tp-id"></a>&#x2022; [`tp_id`](#tp-id) - Optional String<br>Third Party ID. ID assigned to this ticket by our support provider
+
+<a id="type"></a>&#x2022; [`type`](#type) - Optional String  Defaults to `TYPE_UNKNOWN`<br>Possible values are `TYPE_UNKNOWN`, `TYPE_PROBLEM`, `TYPE_TASK`, `TYPE_QUESTION`, `TYPE_INCIDENT`, `TYPE_TECHNICAL_SUPPORT`, `TYPE_ACCOUNT_SUPPORT`, `TYPE_INCIDENT_SUPPORT`<br>[Enum: TYPE_UNKNOWN|TYPE_PROBLEM|TYPE_TASK|TYPE_QUESTION|TYPE_INCIDENT|TYPE_TECHNICAL_SUPPORT|TYPE_ACCOUNT_SUPPORT|TYPE_INCIDENT_SUPPORT] Support Ticket. Several types of issues are supported, such as problems, questions. Unknown or empty ticket type Indicates a problem (e.g. misconfiguration) Indicates a task (a request to do something) Indicates a question (billing, services related) Indicates an incident (something is not working) Indicates a technical support ticket Indicates an account support ticket Indicates an Incident support ticket
+
+### 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
+
+---
+
+#### Comments
+
+A [`comments`](#comments) block supports the following:
+
+<a id="comments-attachment-ids"></a>&#x2022; [`attachment_ids`](#comments-attachment-ids) - Optional List<br>Attachment IDs. Third party ID of any attachment related to this ticket comment
+
+<a id="comments-attachments-info"></a>&#x2022; [`attachments_info`](#comments-attachments-info) - Optional Block<br>Attachments details. Information about any attachments (such as screenshots, plain text files) the comment can have<br>See [Attachments Info](#comments-attachments-info) below.
+
+<a id="comments-author-email"></a>&#x2022; [`author_email`](#comments-author-email) - Optional String<br>Email. Email of the author of the comment
+
+<a id="comments-author-name"></a>&#x2022; [`author_name`](#comments-author-name) - Optional String<br>Author. Author of the comment (as a name)
+
+<a id="comments-created-at"></a>&#x2022; [`created_at`](#comments-created-at) - Optional String<br>At. Comment creation time
+
+<a id="comments-html"></a>&#x2022; [`html`](#comments-html) - Optional String<br>Comment. Comment body as HTML
+
+<a id="comments-plain-text"></a>&#x2022; [`plain_text`](#comments-plain-text) - Optional String<br>Comment. Comment body as plain text
+
+#### Comments Attachments Info
+
+An [`attachments_info`](#comments-attachments-info) block (within [`comments`](#comments)) supports the following:
+
+<a id="comments-attachments-info-attachment"></a>&#x2022; [`attachment`](#comments-attachments-info-attachment) - Optional String<br>Attachment data. Any binary attachment (such as screenshots, plain text files, PDFs) encoded as base64 if used over HTTP
+
+<a id="comments-attachments-info-content-type"></a>&#x2022; [`content_type`](#comments-attachments-info-content-type) - Optional String<br>Content type. Mime content type of the attachment. Helps the UI to properly display the data
+
+<a id="comments-attachments-info-filename"></a>&#x2022; [`filename`](#comments-attachments-info-filename) - Optional String<br>Filename. Filename of the attachment as provided by the caller
+
+<a id="comments-attachments-info-tp-id"></a>&#x2022; [`tp_id`](#comments-attachments-info-tp-id) - Optional String<br>3rd party ID. Optional ID as assigned by the 3rd party actually storing the data
+
+#### Relates To
+
+A [`relates_to`](#relates-to) block supports the following:
+
+<a id="relates-to-kind"></a>&#x2022; [`kind`](#relates-to-kind) - Optional String<br>Object reference kind
+
+<a id="relates-to-name"></a>&#x2022; [`name`](#relates-to-name) - Optional String<br>Object reference name
+
+<a id="relates-to-namespace"></a>&#x2022; [`namespace`](#relates-to-namespace) - Optional String<br>Object reference namespace
+
+<a id="relates-to-tenant"></a>&#x2022; [`tenant`](#relates-to-tenant) - Optional String<br>Object reference tenant
+
+<a id="relates-to-uid"></a>&#x2022; [`uid`](#relates-to-uid) - Optional String<br>Object reference UID
+
+#### 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
+
+---
+
+## Common Types
+
+The following type definitions are used throughout this resource. See the full definition here rather than repeated inline.
+
+### Object Reference {#common-object-reference}
+
+Object references establish a direct reference from one configuration object to another in F5 Distributed Cloud. References use the format `tenant/namespace/name`.
+
+| Field | Type | Description |
+| ----- | ---- | ----------- |
+| `name` | String | Name of the referenced object |
+| `namespace` | String | Namespace containing the referenced object |
+| `tenant` | String | Tenant of the referenced object (system-managed) |
+
+### Transformers {#common-transformers}
+
+Transformers apply transformations to input values before matching. Multiple transformers can be applied in order.
+
+| Value | Description |
+| ----- | ----------- |
+| `LOWER_CASE` | Convert to lowercase |
+| `UPPER_CASE` | Convert to uppercase |
+| `BASE64_DECODE` | Decode base64 content |
+| `NORMALIZE_PATH` | Normalize URL path |
+| `REMOVE_WHITESPACE` | Remove whitespace characters |
+| `URL_DECODE` | Decode URL-encoded characters |
+| `TRIM_LEFT` | Trim leading whitespace |
+| `TRIM_RIGHT` | Trim trailing whitespace |
+| `TRIM` | Trim both leading and trailing whitespace |
+
+### HTTP Methods {#common-http-methods}
+
+HTTP methods used for request matching.
+
+| Value | Description |
+| ----- | ----------- |
+| `ANY` | Match any HTTP method |
+| `GET` | HTTP GET request |
+| `HEAD` | HTTP HEAD request |
+| `POST` | HTTP POST request |
+| `PUT` | HTTP PUT request |
+| `DELETE` | HTTP DELETE request |
+| `CONNECT` | HTTP CONNECT request |
+| `OPTIONS` | HTTP OPTIONS request |
+| `TRACE` | HTTP TRACE request |
+| `PATCH` | HTTP PATCH request |
+| `COPY` | HTTP COPY request (WebDAV) |
+
+### TLS Fingerprints {#common-tls-fingerprints}
+
+TLS fingerprint categories for malicious client detection.
+
+| Value | Description |
+| ----- | ----------- |
+| `TLS_FINGERPRINT_NONE` | No fingerprint matching |
+| `ANY_MALICIOUS_FINGERPRINT` | Match any known malicious fingerprint |
+| `ADWARE` | Adware-associated fingerprints |
+| `DRIDEX` | Dridex malware fingerprints |
+| `GOOTKIT` | Gootkit malware fingerprints |
+| `RANSOMWARE` | Ransomware-associated fingerprints |
+| `TRICKBOT` | Trickbot malware fingerprints |
+
+### IP Threat Categories {#common-ip-threat-categories}
+
+IP address threat categories for security filtering.
+
+| Value | Description |
+| ----- | ----------- |
+| `SPAM_SOURCES` | Known spam sources |
+| `WINDOWS_EXPLOITS` | Windows exploit sources |
+| `WEB_ATTACKS` | Web attack sources |
+| `BOTNETS` | Known botnet IPs |
+| `SCANNERS` | Network scanner IPs |
+| `REPUTATION` | Poor reputation IPs |
+| `PHISHING` | Phishing-related IPs |
+| `PROXY` | Anonymous proxy IPs |
+| `MOBILE_THREATS` | Mobile threat sources |
+| `TOR_PROXY` | Tor exit nodes |
+| `DENIAL_OF_SERVICE` | DoS attack sources |
+| `NETWORK` | Known bad network ranges |
+
+## Import
+
+Import is supported using the following syntax:
+
+```shell
+# Import using namespace/name format
+terraform import f5xc_customer_support.example system/example
+```