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

account_file is not defined but got error: provider.google: "account_file": [REMOVED] Use the credentials field instead #12766

Closed
sirmax123 opened this issue Mar 16, 2017 · 5 comments

Comments

@sirmax123
Copy link

I'm trying to apply simple configuration after update to terraform 0.9.0 and got the following error:

terraform  plan
provider.google.account_file
  Enter a value:

provider.google.credentials
  Enter a value:

1 error(s) occurred:

* provider.google: "account_file": [REMOVED] Use the credentials field instead
bash-3.2$ terraform  version
Terraform v0.9.0

My .tf file is :

provider "google" {
    project     = "project"
    region      = "us-central1"
}

resource "google_compute_health_check" "test-health-check" {
    name               = "health-check"
    check_interval_sec = 5
    timeout_sec        = 5

    tcp_health_check {
        port = "8500"
    }
}

(and no other files in folder)

For both values during terraform plan I use as answer to variable requests.

This .tf file worked fine before update and I do not have account_file defined in .tf

@danawillow
Copy link
Contributor

I believe this is fixed in #12729. @paddyforan, anything people should do in the meantime?

@cblecker
Copy link
Contributor

I'm experiencing this one too, making 0.9.0 useless for my google resources. :(

@paddycarver
Copy link
Contributor

Hi! Sorry for the issues. This is a bug in the GCP provider for Terraform 0.9.0. It only exists in the GCP provider, and only for Terraform 0.9.0. For terraform import, the known workaround is to just hit Enter when prompted to the account_file input. For terraform plan and terraform apply, there is no known workaround at this time.

We will be issuing a 0.9.1 release with a fix soon, and are investigating the underlying problems that led to this issue. Apologies for any trouble this has caused.

@stack72
Copy link
Contributor

stack72 commented Mar 18, 2017

Closed via #12729

and released in Terraform 0.9.1

@stack72 stack72 closed this as completed Mar 18, 2017
@ghost
Copy link

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

No branches or pull requests

6 participants