Failing Example: vault

[aareet]

The vault example is currently failing during validation (https://github.com/hashicorp/terraform-provider-kubernetes-alpha/runs/707258125?check_suite_focus=true):

When applying changes to kubernetes_manifest.service-server, provider
"registry.terraform.io/-/kubernetes-alpha" produced an unexpected new value
for .object: wrong final value type: attribute "kind": string required.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.


Error: Provider produced inconsistent result after apply

When applying changes to kubernetes_manifest.service-injector, provider
"registry.terraform.io/-/kubernetes-alpha" produced an unexpected new value
for .object: wrong final value type: attribute "apiVersion": string required.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

##[error]Process completed with exit code 1.

Note that this error message is misleading - it is the clusterIP attribute that is the unexpected new value. This should be fixed by #34. Once it is, re-enable the example by removing the .skip-checks setting.

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

[btomasini]

I am seeting similar issue:

For the following hcl:

resource "kubernetes_manifest" "build-namespace" {

  provider = kubernetes-alpha

  manifest = {
    apiVersion = "v1"
    kind       = "Namespace"
    metadata   = {
      name = "build"
    }
  }
}

I get the following output on apply:

kubernetes_manifest.build-namespace: Creating...

Error: Provider produced inconsistent result after apply

When applying changes to kubernetes_manifest.build-namespace, provider
"registry.terraform.io/-/kubernetes-alpha" produced an unexpected new value
for .object: wrong final value type: attribute "apiVersion": string required.

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

[btomasini]

Here is a selected output section from the run which errored:

https://gist.github.com/btomasini/5951bd9a2731435b3f587d5f65de207a

[dak1n1]

Here are the results from today's test, using a locally compiled version of terraform core that contains this fix hashicorp/terraform#25774 and the local-plan branch of kubernetes-alpha:
https://gist.githubusercontent.com/dak1n1/36ea527ed1d292c9a96e24b22e6b43b2/raw/3965e47f42813bb973c522a071d9c3f0964ffe96/gistfile1.txt

I think this has made the error message less obscure, so that the root cause can be worked on:

When applying changes to kubernetes_manifest.cluster-role-binding-server,
provider "registry.terraform.io/hashicorp/kubernetes-alpha" produced an
unexpected new value:

.object.metadata.namespace: was cty.StringVal("default"), but now null

This is a bug in the provider, which should be reported in the provider's own
issue tracker.

[alexsomesan]

I think the issue here is that clusterrolebinding is not a namespaced resource and the manifest for it is trying to set a namespace. Removing the namespace might improve things.

On Wed, Oct 14, 2020 at 9:53 PM Stef Forrester ***@***.***> wrote: Here are the results from today's test, using a locally compiled version of terraform core that contains this fix hashicorp/terraform#25774 <hashicorp/terraform#25774> and the local-plan branch of kubernetes-alpha: https://gist.githubusercontent.com/dak1n1/36ea527ed1d292c9a96e24b22e6b43b2/raw/3965e47f42813bb973c522a071d9c3f0964ffe96/gistfile1.txt I think this has made the error message less obscure, so that the root cause can be worked on: When applying changes to kubernetes_manifest.cluster-role-binding-server, provider "registry.terraform.io/hashicorp/kubernetes-alpha" produced an unexpected new value: .object.metadata.namespace: was cty.StringVal("default"), but now null This is a bug in the provider, which should be reported in the provider's own issue tracker. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#35 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIL5G4P7P2FS4SUSDLURNDSKX6S7ANCNFSM4NJZWVLQ> .

-- — Sent from my phone.

[dak1n1]

Thanks @alexsomesan ! That fixed it. Here is a PR to remove the namespaces from the example. #128

It runs now, but it still requires a pre-released version of terraform core and the local-plan branch of this repo. So this issue will probably have to stay open until terraform 0.14 is released.

[aareet]

Terraform 0.14 is now release, and #128 is merged, so I will close this.

[dak1n1]

I think this one actually is supposed to stay open until this file is removed: https://github.com/hashicorp/terraform-provider-kubernetes-alpha/blob/master/examples/vault/.skip_checks that is, according to the first comment on this issue.

[ghost]

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!