re-generate

Signed-off-by: Sebastian Hoß <[email protected]>

docs/data-sources/acmpca_services_k8s_aws_certificate_authority_activation_v1alpha1_manifest.md

@@ -62,6 +62,7 @@ Optional:
 - `certificate_authority_arn` (String) The Amazon Resource Name (ARN) that was returned when you called CreateCertificateAuthority (https://docs.aws.amazon.com/privateca/latest/APIReference/API_CreateCertificateAuthority.html). This must be of the form: arn:aws:acm-pca:region:account:certificate-authority/12345678-1234-1234-1234-123456789012
 - `certificate_authority_ref` (Attributes) AWSResourceReferenceWrapper provides a wrapper around *AWSResourceReference type to provide more user friendly syntax for references using 'from' field Ex: APIIDRef: from: name: my-api (see [below for nested schema](#nestedatt--spec--certificate_authority_ref))
 - `certificate_chain` (Attributes) SecretKeyReference combines a k8s corev1.SecretReference with a specific key within the referred-to Secret (see [below for nested schema](#nestedatt--spec--certificate_chain))
+- `complete_certificate_chain_output` (Attributes) SecretKeyReference combines a k8s corev1.SecretReference with a specific key within the referred-to Secret (see [below for nested schema](#nestedatt--spec--complete_certificate_chain_output))
 - `status` (String)
 
 <a id="nestedatt--spec--certificate"></a>
@@ -105,3 +106,16 @@ Optional:
 
 - `name` (String) name is unique within a namespace to reference a secret resource.
 - `namespace` (String) namespace defines the space within which the secret name must be unique.
+
+
+<a id="nestedatt--spec--complete_certificate_chain_output"></a>
+### Nested Schema for `spec.complete_certificate_chain_output`
+
+Required:
+
+- `key` (String) Key is the key within the secret
+
+Optional:
+
+- `name` (String) name is unique within a namespace to reference a secret resource.
+- `namespace` (String) namespace defines the space within which the secret name must be unique.

docs/data-sources/apps_kubeblocks_io_cluster_definition_v1_manifest.md

@@ -0,0 +1,88 @@
+---
+# generated by https://github.com/hashicorp/terraform-plugin-docs
+page_title: "k8s_apps_kubeblocks_io_cluster_definition_v1_manifest Data Source - terraform-provider-k8s"
+subcategory: "apps.kubeblocks.io"
+description: |-
+  ClusterDefinition defines the topology for databases or storage systems, offering a variety of topological configurations to meet diverse deployment needs and scenarios. It includes a list of Components, each linked to a ComponentDefinition, which enhances reusability and reduce redundancy. For example, widely used components such as etcd and Zookeeper can be defined once and reused across multiple ClusterDefinitions, simplifying the setup of new systems. Additionally, ClusterDefinition also specifies the sequence of startup, upgrade, and shutdown for Components, ensuring a controlled and predictable management of component lifecycles.
+---
+
+# k8s_apps_kubeblocks_io_cluster_definition_v1_manifest (Data Source)
+
+ClusterDefinition defines the topology for databases or storage systems, offering a variety of topological configurations to meet diverse deployment needs and scenarios. It includes a list of Components, each linked to a ComponentDefinition, which enhances reusability and reduce redundancy. For example, widely used components such as etcd and Zookeeper can be defined once and reused across multiple ClusterDefinitions, simplifying the setup of new systems. Additionally, ClusterDefinition also specifies the sequence of startup, upgrade, and shutdown for Components, ensuring a controlled and predictable management of component lifecycles.
+
+## Example Usage
+
+```terraform
+data "k8s_apps_kubeblocks_io_cluster_definition_v1_manifest" "example" {
+  metadata = {
+    name = "some-name"
+
+  }
+}
+```
+
+<!-- schema generated by tfplugindocs -->
+## Schema
+
+### Required
+
+- `metadata` (Attributes) Data that helps uniquely identify this object. See https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#metadata for more details. (see [below for nested schema](#nestedatt--metadata))
+
+### Optional
+
+- `spec` (Attributes) ClusterDefinitionSpec defines the desired state of ClusterDefinition. (see [below for nested schema](#nestedatt--spec))
+
+### Read-Only
+
+- `yaml` (String) The generated manifest in YAML format.
+
+<a id="nestedatt--metadata"></a>
+### Nested Schema for `metadata`
+
+Required:
+
+- `name` (String) Unique identifier for this object. See https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#names for more details.
+
+Optional:
+
+- `annotations` (Map of String) Keys and values that can be used by external tooling to store and retrieve arbitrary metadata about this object. See https://kubernetes.io/docs/concepts/overview/working-with-objects/annotations/ for more details.
+- `labels` (Map of String) Keys and values that can be used to organize and categorize objects. See https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/ for more details.
+
+
+<a id="nestedatt--spec"></a>
+### Nested Schema for `spec`
+
+Optional:
+
+- `topologies` (Attributes List) Topologies defines all possible topologies within the cluster. (see [below for nested schema](#nestedatt--spec--topologies))
+
+<a id="nestedatt--spec--topologies"></a>
+### Nested Schema for `spec.topologies`
+
+Required:
+
+- `components` (Attributes List) Components specifies the components in the topology. (see [below for nested schema](#nestedatt--spec--topologies--components))
+- `name` (String) Name is the unique identifier for the cluster topology. Cannot be updated.
+
+Optional:
+
+- `default` (Boolean) Default indicates whether this topology serves as the default configuration. When set to true, this topology is automatically used unless another is explicitly specified.
+- `orders` (Attributes) Specifies the sequence in which components within a cluster topology are started, stopped, and upgraded. This ordering is crucial for maintaining the correct dependencies and operational flow across components. (see [below for nested schema](#nestedatt--spec--topologies--orders))
+
+<a id="nestedatt--spec--topologies--components"></a>
+### Nested Schema for `spec.topologies.components`
+
+Required:
+
+- `comp_def` (String) Specifies the exact name, name prefix, or regular expression pattern for matching the name of the ComponentDefinition custom resource (CR) that defines the Component's characteristics and behavior. The system selects the ComponentDefinition CR with the latest version that matches the pattern. This approach allows: 1. Precise selection by providing the exact name of a ComponentDefinition CR. 2. Flexible and automatic selection of the most up-to-date ComponentDefinition CR by specifying a name prefix or regular expression pattern. Once set, this field cannot be updated.
+- `name` (String) Defines the unique identifier of the component within the cluster topology. It follows IANA Service naming rules and is used as part of the Service's DNS name. The name must start with a lowercase letter, can contain lowercase letters, numbers, and hyphens, and must end with a lowercase letter or number. Cannot be updated once set.
+
+
+<a id="nestedatt--spec--topologies--orders"></a>
+### Nested Schema for `spec.topologies.orders`
+
+Optional:
+
+- `provision` (List of String) Specifies the order for creating and initializing components. This is designed for components that depend on one another. Components without dependencies can be grouped together. Components that can be provisioned independently or have no dependencies can be listed together in the same stage, separated by commas.
+- `terminate` (List of String) Outlines the order for stopping and deleting components. This sequence is designed for components that require a graceful shutdown or have interdependencies. Components that can be terminated independently or have no dependencies can be listed together in the same stage, separated by commas.
+- `update` (List of String) Update determines the order for updating components' specifications, such as image upgrades or resource scaling. This sequence is designed for components that have dependencies or require specific update procedures. Components that can be updated independently or have no dependencies can be listed together in the same stage, separated by commas.