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

v1.14 regression: google_compute_disk "zone" default value from project not working now #1626

Closed
Chupaka opened this issue Jun 8, 2018 · 1 comment
Labels

Comments

@Chupaka
Copy link
Contributor

Chupaka commented Jun 8, 2018

Terraform Version

Terraform v0.11.7

  • provider.google v1.(13|14).0

Affected Resource(s)

  • google_compute_disk

Terraform Configuration Files

provider "google" {
  credentials = "${file("~/.config/gcloud/terraform-apalon-poc-admin.json")}"
  project     = "apalon-poc-39d7f1fb"
  region      = "us-east1"
  zone        = "us-east1-b"

  version = "~> 1.(13|14).0"
}

resource "google_compute_disk" "test" {
  name  = "test-disk"
  size  = "1"
}

Expected Behavior

With provider.google v1.13.0:

$ terraform apply

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  + google_compute_disk.test
      id:                         <computed>
      disk_encryption_key_sha256: <computed>
      label_fingerprint:          <computed>
      name:                       "test-disk"
      project:                    <computed>
      self_link:                  <computed>
      size:                       "1"
      type:                       "pd-standard"
      users.#:                    <computed>
      zone:                       <computed>


Plan: 1 to add, 0 to change, 0 to destroy.

Actual Behavior

With provider.google v1.14.0:

$ terraform apply

Error: google_compute_disk.test: "zone": required field is not set
@ghost
Copy link

ghost commented Nov 18, 2018

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost unassigned rosbo Nov 18, 2018
@ghost ghost locked and limited conversation to collaborators Nov 18, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants