Joey Marianer

Reviving this ancient issue to comment that this would be particularly helpful for module developers. Normally when changing the internals of a module you don't need to rerun `terraform init`,...

Not sure how to run tests against other versions of Vault. (I'm also not sure my change is even correct, but that's a different story :) )

The Terraform provider invalidates the metadata whenever there's a change to the values or to a number of other fields, see . Unfortunately, Terraform doesn't let a provider invalidate a...

Of course, a few hours after making that change I found out it was incompatible with some modules that we use, and that's not surprising at all. I'm not sure...

Can anyone speak to whether this is a limitation in Terraform or in the SDK (or in protocol 5, which seems unlikely)? I'm wondering if porting to use a different...

I'm no expert but I think this might be as simple as the following patch: ``` diff --git a/vault/resource_kv_secret.go b/vault/resource_kv_secret.go index 0d666d6f..1e10c6b2 100644 --- a/vault/resource_kv_secret.go +++ b/vault/resource_kv_secret.go @@ -108,6 +108,15...

This looks like a one-liner to me (add to the validation function in `resource_kubernetes_persistent_volume.go:90`), but I don't have an environment I can test it in.

Makes sense and thanks. I didn't know about that list, and thought it was already past alpha for some reason. Would you like me to close out this issue or...

Hi all and happy new year! My company isn't using Terraform for k8s anymore, so I don't see myself making this PR. As I mentioned earlier, it's probably a very...

Ah, I didn't realize `ForceNew` was a thing, though I probably should have. In any case, unfortunately the non-empty plan does persist when I upgrade to v0.85. It should be...