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

alpha1: when optional bool in set is NOT SET, error on plan #19215

Closed
mitchellh opened this issue Oct 29, 2018 · 3 comments · Fixed by #19253
Closed

alpha1: when optional bool in set is NOT SET, error on plan #19215

mitchellh opened this issue Oct 29, 2018 · 3 comments · Fixed by #19253
Labels
Milestone

Comments

@mitchellh
Copy link
Contributor

Terraform Version

Terraform v0.12.0-dev (009534d1016cd3b1d0d911f151520b04f8db453a)
+ provider.docker v1.1.0

Terraform Configuration Files

provider "docker" {
   host = "unix:///var/run/docker.sock"
}

resource "docker_container" "consul-primary-srv1" {
  image = "consul:1.3.0"
  name = "hello"

  volumes {
    volume_name = "hello"
    container_path = "/consul/data"
  }
}

Debug Output

https://gist.github.com/mitchellh/f9553f5a51b095b38119f72cd2a32803

Expected Behavior

The plan should succeed.

Actual Behavior

There is an error about read_only not being set but that is an optional field that defaults to "false".

This works in 0.11.

Steps to Reproduce

  1. terraform init
  2. terraform plan

Additional Context

The Docker provider was recompiled for 0.12 at this commit: hashicorp/terraform-provider-docker@9d293c1

@mitchellh
Copy link
Contributor Author

For HashiCorp folks, I posted the compiled Docker provider for 0.12 here: https://hashicorp.slack.com/archives/C03N5JEC3/p1540842043071900?thread_ts=1540841612.069100&cid=C03N5JEC3

@mitchellh
Copy link
Contributor Author

OH YEAH

@ghost
Copy link

ghost commented Mar 31, 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 Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants