igoooor

That sounds really great! A workaround I've used meanwhile is to use a hook and manually decrypt the secret file, and use the decrypted file as **valuesFiles: []**

it happens to us too :(

to be specific, in my case it happens during `Refreshing state` and my provider looks like this ``` provider "kubernetes" { load_config_file = false host = "https://${data.google_container_cluster.this.0.endpoint}" client_certificate = data.google_container_cluster.this.0.master_auth.0.client_certificate...

in my case I get the localhost error yes, when refreshing only ``` Error: Get http://localhost/api/v1/namespaces/xxx: dial tcp 127.0.0.1:80: connect: connection refused ``` If I replace my provider config and...

This only happens to me since I update to terraform 13 today. I stayed on terraform 12 until now because of some other stuff, and I never had this problem....

It is already present, before starting the terraform command.

it works via kubeconfig and via parameters set for `host`, `client_certificate`, etc.. but it does not work when `host`, `client_certificate`, etc.. are set from the `data.google_container_cluster.this` And again, it only...

it also happens when I'm using a resource instead of a data. Of course not the first time I apply when it creates the cluster, but afterwards if I apply...

Do we have an ETA for this feature? or anyone found an alternative in the meantime?

@grampelberg yes but I don't manage to make it work. Let's take this example: ``` ksync create -p my-pod $(pwd)/docroot /home/www-data/docroot ``` I want to ignore `docroot/vendor` folder Should I...