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.

Sign up for GitHub

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

Jump to bottom

terraform plan issue on recently clone repo #101

Open
pdomineaux opened this issue Dec 29, 2021 · 2 comments · May be fixed by #103
Open

terraform plan issue on recently clone repo #101

pdomineaux opened this issue Dec 29, 2021 · 2 comments · May be fixed by #103

Comments

@pdomineaux
Copy link

What did you expect to happen?
I expected to see the terraform execution plan and see what ressources will be deployed

What actually happened?
I got an error saying that some arguments are missing

Output

terraform plan --var "billing_account=$BILLING_ACCOUNT" --var "org_id=$ORG_ID"

Error: Missing required argument

  on gcp.tf line 278, in resource "google_container_cluster" "vault":
 278:     workload_metadata_config {

The argument "mode" is required, but no definition was found.


Error: Unsupported argument

  on gcp.tf line 279, in resource "google_container_cluster" "vault":
 279:       node_metadata = "SECURE"

An argument named "node_metadata" is not expected here.


Error: Unsupported argument

  on gcp.tf line 293, in resource "google_container_cluster" "vault":
 293:     username = ""

An argument named "username" is not expected here.


Error: Unsupported argument

  on gcp.tf line 294, in resource "google_container_cluster" "vault":
 294:     password = ""

An argument named "password" is not expected here.

Additional context
I just clone the repo and set the required variables: billing_account and org_id

terraform --version
Terraform v0.12.31
+ provider.google v3.90.1
+ provider.google-beta v4.5.0
+ provider.kubernetes v2.7.1
+ provider.random v3.1.0
+ provider.tls v3.1.0
@bradub
Copy link

bradub commented Jan 10, 2022

@pdomineaux hello, did you manage to bypass those issues?

@pdomineaux
Copy link
Author

@pdomineaux hello, did you manage to bypass those issues?

Nope, I still don't have a solution to this problem. Any clue?

@elefeint elefeint linked a pull request Oct 5, 2022 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Adapt scripts to avoid fields removed in provider v4.0.0 elefeint/vault-on-gke
2 participants
@pdomineaux @bradub