[GH-ISSUE #85] Please supply a way to pass through terraform init args #44

New issue

Closed

opened 2026-05-06 12:36:38 +02:00 by BreizhHardware · 3 comments

BreizhHardware commented

2026-05-06 12:36:38 +02:00

Owner

Originally created by @dnk8n on GitHub (Nov 30, 2023).
Original GitHub issue: https://github.com/patrickchugh/terravision/issues/85

For example, for projects that abstract secrets from the remote state config we init like this:

terraform init -backend-config=backend.tfconf

From what I can gather, terravision only supports terraform init (no args)

Originally created by @dnk8n on GitHub (Nov 30, 2023). Original GitHub issue: https://github.com/patrickchugh/terravision/issues/85 For example, for projects that abstract secrets from the remote state config we init like this: `terraform init -backend-config=backend.tfconf` From what I can gather, terravision only supports `terraform init` (no args)

BreizhHardware closed this issue

2026-05-06 12:36:38 +02:00

BreizhHardware commented

2026-05-06 12:36:39 +02:00

Author

Owner

@dnk8n commented on GitHub (Nov 30, 2023):

Note, how corresponding templates look in this case:

#main.tf
terraform {
  backend "s3" {}
}

#backend.tfconf
region = "af-south-1"
bucket = "terraform-state"
key    = "terraform.tfstate"

@dnk8n commented on GitHub (Nov 30, 2023): Note, how corresponding templates look in this case: ``` #main.tf terraform { backend "s3" {} } ``` ``` #backend.tfconf region = "af-south-1" bucket = "terraform-state" key = "terraform.tfstate" ```

BreizhHardware commented

2026-05-06 12:36:39 +02:00

Author

Owner

@patrickchugh commented on GitHub (Dec 2, 2023):

@dnk8n This could be tricky. Running terraform init and terraform plan on an S3 backend or other custom backend that exists will mean terraform in most cases will not create a plan to create all new resources from scratch. I had to implement a workaround by over-riding the backend information that is provided in source with a temporary override.tf that specifies a local backend which was empty to get around this. Any thoughts on how you would envision this working so that we get a fresh plan to create all the resources every time it is run if we allow passing in backend files during init?

@patrickchugh commented on GitHub (Dec 2, 2023): @dnk8n This could be tricky. Running `terraform init` and` terraform plan` on an S3 backend or other custom backend that exists will mean terraform in most cases will not create a plan to create all new resources from scratch. I had to implement a workaround by over-riding the backend information that is provided in source with a temporary `override.tf` that specifies a local backend which was empty to get around this. Any thoughts on how you would envision this working so that we get a fresh plan to create all the resources every time it is run if we allow passing in backend files during init?

BreizhHardware commented

2026-05-06 12:36:39 +02:00

Author

Owner

@patrickchugh commented on GitHub (Dec 20, 2023):

Didn't hear back so closing

@patrickchugh commented on GitHub (Dec 20, 2023): Didn't hear back so closing

BreizhHardware referenced this issue

2026-05-06 12:37:49 +02:00

[PR #46] [MERGED] Guard tfdata["all_locals"][module] #141