attributes with DynamicPseudoType are not obeying unknown and sensitive metadata when rendered

[liamcervante]

Terraform Version

1.4.*

Terraform Configuration Files

resource "kubernetes_manifest" "manifest" {
    manifest = {
        "apiVersion" = "v1"
        "kind" = "Secret"
        "metadata" = {
            "name" = "certificates"
            "namespace" = tfcoremock_simple_resource.resource.id
        }
        "data" = {
            "ca-certificates.crt" = sensitive("sensitive value")
        }
    }
}

Debug Output

n/a

Expected Behavior

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # kubernetes_manifest.manifest will be created
  + resource "kubernetes_manifest" "manifest" {
      + manifest = {
          + apiVersion = "v1"
          + data       = {
              + "ca-certificates.crt" = (sensitive value)
            }
          + kind       = "Secret"
          + metadata   = {
              + name      = "certificates"
              + namespace = "certificates"
            }
        }
      + object   = {
          + apiVersion = "v1"
          + data       = {
              + "ca-certificates.crt" = "sensitive value"
            }
          + immutable  = (known after apply)
          + kind       = "Secret"
          + metadata   = {
              + annotations                = (known after apply)
              + creationTimestamp          = (known after apply)
              + deletionGracePeriodSeconds = (known after apply)
              + deletionTimestamp          = (known after apply)
              + finalizers                 = (known after apply)
              + generateName               = (known after apply)
              + generation                 = (known after apply)
              + labels                     = (known after apply)
              + managedFields              = (known after apply)
              + name                       = "certificates"
              + namespace                  = "certificates"
              + ownerReferences            = (known after apply)
              + resourceVersion            = (known after apply)
              + selfLink                   = (known after apply)
              + uid                        = (known after apply)
            }
          + stringData = (known after apply)
          + type       = (known after apply)
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions if you run "terraform apply" now.

Actual Behavior

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with
the following symbols:
  + create

Terraform will perform the following actions:

  # kubernetes_manifest.manifest will be created
  + resource "kubernetes_manifest" "manifest" {
      + manifest = {
          + apiVersion = "v1"
          + data       = {
              + "ca-certificates.crt" = "sensitive value"
            }
          + kind       = "Secret"
          + metadata   = {
              + name      = "certificates"
              + namespace = "certificates"
            }
        }
      + object   = {
          + apiVersion = "v1"
          + data       = {
              + "ca-certificates.crt" = "sensitive value"
            }
          + kind       = "Secret"
          + metadata   = {
              + name      = "certificates"
              + namespace = "certificates"
            }
        }
    }

Plan: 1 to add, 0 to change, 0 to destroy.

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Note: You didn't use the -out option to save this plan, so Terraform can't guarantee to take exactly these actions
if you run "terraform apply" now.

Steps to Reproduce

terraform init
terraform apply

Additional Context

No response

References

hashicorp/terraform-provider-kubernetes#2073

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.