"argument named region not expected here"

[mco-gh]

Problem

In line 79 of setup.sh, this build command:

gcloud builds submit ./terraform --project="$OPS_PROJECT" \
    80      --config=./ops/terraform.cloudbuild.yaml \
    81      --substitutions=_ENV="ops",_STATE_GCS_BUCKET_NAME=$STATE_GCS_BUCKET_NAME,_TF_SERVICE_ACCT=$TERRAFORM_SERVICE_ACCOUNT

is failing with the following TF errors:

Starting Step #2 - "tf plan"
Step #2 - "tf plan": Already have image: hashicorp/terraform:1.0.0
Step #2 - "tf plan": ╷
Step #2 - "tf plan": │ Error: Unsupported argument
Step #2 - "tf plan": │ 
Step #2 - "tf plan": │   on main.tf line 4, in module "quizrd_ops":
Step #2 - "tf plan": │    4:   region          = var.region
Step #2 - "tf plan": │ 
Step #2 - "tf plan": │ An argument named "region" is not expected here.
Step #2 - "tf plan": ╵
Step #2 - "tf plan": ╷
Step #2 - "tf plan": │ Error: Unsupported argument
Step #2 - "tf plan": │ 
Step #2 - "tf plan": │   on main.tf line 5, in module "quizrd_ops":
Step #2 - "tf plan": │    5:   setup_cd_system = var.setup_cd_system
Step #2 - "tf plan": │ 
Step #2 - "tf plan": │ An argument named "setup_cd_system" is not expected here.
Step #2 - "tf plan": ╵
Finished Step #2 - "tf plan"
ERROR
ERROR: build step 2 "hashicorp/terraform:1.0.0" failed: step exited with non-zero status: 1
--------------------------------------------------------------------------------

BUILD FAILURE: Build step failure: build step 2 "hashicorp/terraform:1.0.0" failed: step exited with non-zero status: 1
ERROR: (gcloud.builds.submit) build 8795dfc3-914a-4482-8e32-54a3f1ed84c7 completed with status "FAILURE"

Steps to Reproduce

I forked emblem and followed the README.md.

Expected behavior

I expected it to complete without errors.

Additional context

Screenshots
If applicable, add screenshots to help explain your problem.

User environment:

• OS: MacOS
• Browser: Version 112.0.5615.39 (Official Build) beta (x86_64)
• Emblem Project Version: 0.1.0

[mco-gh]

Sorry, you can ignore this, it's actually working fine. I was seeing this error on a modified fork so I decided to make sure the vanilla repo works but I inadvertently switched tabs at some point and was looking back at the old errors.