You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not having the value set (which is the general/popular case; it is rare to set TLS configuration information unless you're going across hosts) results in the following prompt every time terraform plan or terraform apply is run:
$ terraform plan
provider.docker.cert_path
Path to directory with Docker TLS config
Enter a value:
Pressing enter (leaving the value blank) allows Terraform to get on with it.
This is probably not an error specific to the Docker provider; @phinze suggested that this might be the first time there is a provider configuration value that is optional, so it's just exposing an existing bug. Regardless, it's marked as optional in the provider code, so it should not be prompting for it.
The text was updated successfully, but these errors were encountered:
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.
ghost
locked and limited conversation to collaborators
May 3, 2020
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Not having the value set (which is the general/popular case; it is rare to set TLS configuration information unless you're going across hosts) results in the following prompt every time
terraform plan
orterraform apply
is run:Pressing enter (leaving the value blank) allows Terraform to get on with it.
This is probably not an error specific to the Docker provider; @phinze suggested that this might be the first time there is a provider configuration value that is optional, so it's just exposing an existing bug. Regardless, it's marked as optional in the provider code, so it should not be prompting for it.
The text was updated successfully, but these errors were encountered: