Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

When optional provider.docker.cert_path is empty, plan/apply always prompt #1432

Closed
jefferai opened this issue Apr 8, 2015 · 1 comment · Fixed by #1456
Closed

When optional provider.docker.cert_path is empty, plan/apply always prompt #1432

jefferai opened this issue Apr 8, 2015 · 1 comment · Fixed by #1456

Comments

@jefferai
Copy link
Member

jefferai commented Apr 8, 2015

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.

@ghost
Copy link

ghost commented May 3, 2020

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 ghost locked and limited conversation to collaborators May 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants