Update upstream specifications to their latest version

.github/workflows/terratest-chainsaw_kyverno_io_test_v1alpha2_manifest.yml

@@ -0,0 +1,40 @@
+# SPDX-FileCopyrightText: The terraform-provider-k8s Authors
+# SPDX-License-Identifier: 0BSD
+
+name: ChainsawKyvernoIoTestV1Alpha2Manifest
+on:
+  pull_request:
+    branches: [ main ]
+    paths:
+      - examples/data-sources/k8s_chainsaw_kyverno_io_test_v1alpha2_manifest/**
+      - internal/provider/chainsaw_kyverno_io_v1alpha2/chainsaw_kyverno_io_test_v1alpha2_manifest.go
+      - internal/provider/chainsaw_kyverno_io_v1alpha2/chainsaw_kyverno_io_test_v1alpha2_manifest_test.go
+      - terratest/chainsaw_kyverno_io_v1alpha2/chainsaw_kyverno_io_test_v1alpha2_manifest_test.go
+jobs:
+  terraform:
+    name: Test with Terraform
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        name: Checkout
+        uses: actions/checkout@v4
+      - id: setup_go
+        name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version-file: go.mod
+          cache: true
+      - id: setup_terraform
+        name: Setup Terraform
+        uses: hashicorp/setup-terraform@v3
+        with:
+          terraform_wrapper: false
+      - id: install
+        name: Install Provider
+        run: make install
+      - id: tests
+        name: Run Unit Tests
+        run: go test -v -timeout=120s -count=1 ./internal/provider/chainsaw_kyverno_io_v1alpha2/chainsaw_kyverno_io_test_v1alpha2_manifest_test.go
+      - id: terratest
+        name: Run Terratest Tests
+        run: go test -v -timeout=120s -count=1 -run TestChainsawKyvernoIoTestV1Alpha2Manifest ./terratest/chainsaw_kyverno_io_v1alpha2

.github/workflows/terratest-lerentis_uploadfilter24_eu_bitwarden_secret_v1beta6_manifest.yml

@@ -0,0 +1,40 @@
+# SPDX-FileCopyrightText: The terraform-provider-k8s Authors
+# SPDX-License-Identifier: 0BSD
+
+name: LerentisUploadfilter24EuBitwardenSecretV1Beta6Manifest
+on:
+  pull_request:
+    branches: [ main ]
+    paths:
+      - examples/data-sources/k8s_lerentis_uploadfilter24_eu_bitwarden_secret_v1beta6_manifest/**
+      - internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_secret_v1beta6_manifest.go
+      - internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_secret_v1beta6_manifest_test.go
+      - terratest/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_secret_v1beta6_manifest_test.go
+jobs:
+  terraform:
+    name: Test with Terraform
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        name: Checkout
+        uses: actions/checkout@v4
+      - id: setup_go
+        name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version-file: go.mod
+          cache: true
+      - id: setup_terraform
+        name: Setup Terraform
+        uses: hashicorp/setup-terraform@v3
+        with:
+          terraform_wrapper: false
+      - id: install
+        name: Install Provider
+        run: make install
+      - id: tests
+        name: Run Unit Tests
+        run: go test -v -timeout=120s -count=1 ./internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_secret_v1beta6_manifest_test.go
+      - id: terratest
+        name: Run Terratest Tests
+        run: go test -v -timeout=120s -count=1 -run TestLerentisUploadfilter24EuBitwardenSecretV1Beta6Manifest ./terratest/lerentis_uploadfilter24_eu_v1beta6

.github/workflows/terratest-lerentis_uploadfilter24_eu_bitwarden_template_v1beta6_manifest.yml

@@ -0,0 +1,40 @@
+# SPDX-FileCopyrightText: The terraform-provider-k8s Authors
+# SPDX-License-Identifier: 0BSD
+
+name: LerentisUploadfilter24EuBitwardenTemplateV1Beta6Manifest
+on:
+  pull_request:
+    branches: [ main ]
+    paths:
+      - examples/data-sources/k8s_lerentis_uploadfilter24_eu_bitwarden_template_v1beta6_manifest/**
+      - internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_template_v1beta6_manifest.go
+      - internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_template_v1beta6_manifest_test.go
+      - terratest/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_template_v1beta6_manifest_test.go
+jobs:
+  terraform:
+    name: Test with Terraform
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        name: Checkout
+        uses: actions/checkout@v4
+      - id: setup_go
+        name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version-file: go.mod
+          cache: true
+      - id: setup_terraform
+        name: Setup Terraform
+        uses: hashicorp/setup-terraform@v3
+        with:
+          terraform_wrapper: false
+      - id: install
+        name: Install Provider
+        run: make install
+      - id: tests
+        name: Run Unit Tests
+        run: go test -v -timeout=120s -count=1 ./internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_bitwarden_template_v1beta6_manifest_test.go
+      - id: terratest
+        name: Run Terratest Tests
+        run: go test -v -timeout=120s -count=1 -run TestLerentisUploadfilter24EuBitwardenTemplateV1Beta6Manifest ./terratest/lerentis_uploadfilter24_eu_v1beta6

.github/workflows/terratest-lerentis_uploadfilter24_eu_registry_credential_v1beta6_manifest.yml

@@ -0,0 +1,40 @@
+# SPDX-FileCopyrightText: The terraform-provider-k8s Authors
+# SPDX-License-Identifier: 0BSD
+
+name: LerentisUploadfilter24EuRegistryCredentialV1Beta6Manifest
+on:
+  pull_request:
+    branches: [ main ]
+    paths:
+      - examples/data-sources/k8s_lerentis_uploadfilter24_eu_registry_credential_v1beta6_manifest/**
+      - internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_registry_credential_v1beta6_manifest.go
+      - internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_registry_credential_v1beta6_manifest_test.go
+      - terratest/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_registry_credential_v1beta6_manifest_test.go
+jobs:
+  terraform:
+    name: Test with Terraform
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        name: Checkout
+        uses: actions/checkout@v4
+      - id: setup_go
+        name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version-file: go.mod
+          cache: true
+      - id: setup_terraform
+        name: Setup Terraform
+        uses: hashicorp/setup-terraform@v3
+        with:
+          terraform_wrapper: false
+      - id: install
+        name: Install Provider
+        run: make install
+      - id: tests
+        name: Run Unit Tests
+        run: go test -v -timeout=120s -count=1 ./internal/provider/lerentis_uploadfilter24_eu_v1beta6/lerentis_uploadfilter24_eu_registry_credential_v1beta6_manifest_test.go
+      - id: terratest
+        name: Run Terratest Tests
+        run: go test -v -timeout=120s -count=1 -run TestLerentisUploadfilter24EuRegistryCredentialV1Beta6Manifest ./terratest/lerentis_uploadfilter24_eu_v1beta6

.github/workflows/terratest-operator_cryostat_io_cryostat_v1beta2_manifest.yml

@@ -0,0 +1,40 @@
+# SPDX-FileCopyrightText: The terraform-provider-k8s Authors
+# SPDX-License-Identifier: 0BSD
+
+name: OperatorCryostatIoCryostatV1Beta2Manifest
+on:
+  pull_request:
+    branches: [ main ]
+    paths:
+      - examples/data-sources/k8s_operator_cryostat_io_cryostat_v1beta2_manifest/**
+      - internal/provider/operator_cryostat_io_v1beta2/operator_cryostat_io_cryostat_v1beta2_manifest.go
+      - internal/provider/operator_cryostat_io_v1beta2/operator_cryostat_io_cryostat_v1beta2_manifest_test.go
+      - terratest/operator_cryostat_io_v1beta2/operator_cryostat_io_cryostat_v1beta2_manifest_test.go
+jobs:
+  terraform:
+    name: Test with Terraform
+    runs-on: ubuntu-latest
+    steps:
+      - id: checkout
+        name: Checkout
+        uses: actions/checkout@v4
+      - id: setup_go
+        name: Set up Go
+        uses: actions/setup-go@v5
+        with:
+          go-version-file: go.mod
+          cache: true
+      - id: setup_terraform
+        name: Setup Terraform
+        uses: hashicorp/setup-terraform@v3
+        with:
+          terraform_wrapper: false
+      - id: install
+        name: Install Provider
+        run: make install
+      - id: tests
+        name: Run Unit Tests
+        run: go test -v -timeout=120s -count=1 ./internal/provider/operator_cryostat_io_v1beta2/operator_cryostat_io_cryostat_v1beta2_manifest_test.go
+      - id: terratest
+        name: Run Terratest Tests
+        run: go test -v -timeout=120s -count=1 -run TestOperatorCryostatIoCryostatV1Beta2Manifest ./terratest/operator_cryostat_io_v1beta2

docs/data-sources/acid_zalan_do_postgresql_v1_manifest.md

@@ -141,6 +141,7 @@ Required:
 Optional:
 
 - `iops` (Number)
+- `is_sub_path_expr` (Boolean)
 - `selector` (Attributes) (see [below for nested schema](#nestedatt--spec--volume--selector))
 - `storage_class` (String)
 - `sub_path` (String)
@@ -180,6 +181,7 @@ Required:
 
 Optional:
 
+- `is_sub_path_expr` (Boolean)
 - `sub_path` (String)
 - `target_containers` (List of String)
 

docs/data-sources/acme_cert_manager_io_challenge_v1_manifest.md

@@ -445,10 +445,10 @@ Required:
 Optional:
 
 - `group` (String) Group is the group of the referent.When unspecified, 'gateway.networking.k8s.io' is inferred.To set the core API group (such as for a 'Service' kind referent),Group must be explicitly set to '' (empty string).Support: Core
-- `kind` (String) Kind is kind of the referent.There are two kinds of parent resources with 'Core' support:* Gateway (Gateway conformance profile)* Service (Mesh conformance profile, experimental, ClusterIP Services only)Support for other resources is Implementation-Specific.
+- `kind` (String) Kind is kind of the referent.There are two kinds of parent resources with 'Core' support:* Gateway (Gateway conformance profile)* Service (Mesh conformance profile, ClusterIP Services only)Support for other resources is Implementation-Specific.
 - `namespace` (String) Namespace is the namespace of the referent. When unspecified, this refersto the local namespace of the Route.Note that there are specific rules for ParentRefs which cross namespaceboundaries. Cross-namespace references are only valid if they are explicitlyallowed by something in the namespace they are referring to. For example:Gateway has the AllowedRoutes field, and ReferenceGrant provides ageneric way to enable any other kind of cross-namespace reference.<gateway:experimental:description>ParentRefs from a Route to a Service in the same namespace are 'producer'routes, which apply default routing rules to inbound connections fromany namespace to the Service.ParentRefs from a Route to a Service in a different namespace are'consumer' routes, and these routing rules are only applied to outboundconnections originating from the same namespace as the Route, for whichthe intended destination of the connections are a Service targeted as aParentRef of the Route.</gateway:experimental:description>Support: Core
-- `port` (Number) Port is the network port this Route targets. It can be interpreteddifferently based on the type of parent resource.When the parent resource is a Gateway, this targets all listenerslistening on the specified port that also support this kind of Route(andselect this Route). It's not recommended to set 'Port' unless thenetworking behaviors specified in a Route must apply to a specific portas opposed to a listener(s) whose port(s) may be changed. When both Portand SectionName are specified, the name and port of the selected listenermust match both specified values.<gateway:experimental:description>When the parent resource is a Service, this targets a specific port in theService spec. When both Port (experimental) and SectionName are specified,the name and port of the selected port must match both specified values.</gateway:experimental:description>Implementations MAY choose to support other parent resources.Implementations supporting other types of parent resources MUST clearlydocument how/if Port is interpreted.For the purpose of status, an attachment is considered successful aslong as the parent resource accepts it partially. For example, Gatewaylisteners can restrict which Routes can attach to them by Route kind,namespace, or hostname. If 1 of 2 Gateway listeners accept attachmentfrom the referencing Route, the Route MUST be considered successfullyattached. If no Gateway listeners accept attachment from this Route,the Route MUST be considered detached from the Gateway.Support: Extended<gateway:experimental>
-- `section_name` (String) SectionName is the name of a section within the target resource. In thefollowing resources, SectionName is interpreted as the following:* Gateway: Listener Name. When both Port (experimental) and SectionNameare specified, the name and port of the selected listener must matchboth specified values.* Service: Port Name. When both Port (experimental) and SectionNameare specified, the name and port of the selected listener must matchboth specified values. Note that attaching Routes to Services as Parentsis part of experimental Mesh support and is not supported for any otherpurpose.Implementations MAY choose to support attaching Routes to other resources.If that is the case, they MUST clearly document how SectionName isinterpreted.When unspecified (empty string), this will reference the entire resource.For the purpose of status, an attachment is considered successful if atleast one section in the parent resource accepts it. For example, Gatewaylisteners can restrict which Routes can attach to them by Route kind,namespace, or hostname. If 1 of 2 Gateway listeners accept attachment fromthe referencing Route, the Route MUST be considered successfullyattached. If no Gateway listeners accept attachment from this Route, theRoute MUST be considered detached from the Gateway.Support: Core
+- `port` (Number) Port is the network port this Route targets. It can be interpreteddifferently based on the type of parent resource.When the parent resource is a Gateway, this targets all listenerslistening on the specified port that also support this kind of Route(andselect this Route). It's not recommended to set 'Port' unless thenetworking behaviors specified in a Route must apply to a specific portas opposed to a listener(s) whose port(s) may be changed. When both Portand SectionName are specified, the name and port of the selected listenermust match both specified values.<gateway:experimental:description>When the parent resource is a Service, this targets a specific port in theService spec. When both Port (experimental) and SectionName are specified,the name and port of the selected port must match both specified values.</gateway:experimental:description>Implementations MAY choose to support other parent resources.Implementations supporting other types of parent resources MUST clearlydocument how/if Port is interpreted.For the purpose of status, an attachment is considered successful aslong as the parent resource accepts it partially. For example, Gatewaylisteners can restrict which Routes can attach to them by Route kind,namespace, or hostname. If 1 of 2 Gateway listeners accept attachmentfrom the referencing Route, the Route MUST be considered successfullyattached. If no Gateway listeners accept attachment from this Route,the Route MUST be considered detached from the Gateway.Support: Extended
+- `section_name` (String) SectionName is the name of a section within the target resource. In thefollowing resources, SectionName is interpreted as the following:* Gateway: Listener name. When both Port (experimental) and SectionNameare specified, the name and port of the selected listener must matchboth specified values.* Service: Port name. When both Port (experimental) and SectionNameare specified, the name and port of the selected listener must matchboth specified values.Implementations MAY choose to support attaching Routes to other resources.If that is the case, they MUST clearly document how SectionName isinterpreted.When unspecified (empty string), this will reference the entire resource.For the purpose of status, an attachment is considered successful if atleast one section in the parent resource accepts it. For example, Gatewaylisteners can restrict which Routes can attach to them by Route kind,namespace, or hostname. If 1 of 2 Gateway listeners accept attachment fromthe referencing Route, the Route MUST be considered successfullyattached. If no Gateway listeners accept attachment from this Route, theRoute MUST be considered detached from the Gateway.Support: Core
 
 
 
@@ -897,7 +897,7 @@ Optional:
 
 Optional:
 
-- `name` (String) Name of the referent.More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#namesTODO: Add other useful fields. apiVersion, kind, uid?
+- `name` (String) Name of the referent.This field is effectively required, but due to backwards compatibility isallowed to be empty. Instances of this type with an empty value here arealmost certainly wrong.TODO: Add other useful fields. apiVersion, kind, uid?More info: https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#namesTODO: Drop 'kubebuilder:default' when controller-gen doesn't need it https://github.com/kubernetes-sigs/kubebuilder/issues/3896.
 
 
 <a id="nestedatt--spec--solver--http01--ingress--pod_template--spec--tolerations"></a>