starred/terravision

Fork 0

mirror of https://github.com/patrickchugh/terravision.git synced 2026-05-09 08:25:25 +02:00

[GH-ISSUE #113] ERROR: Invalid output from 'terraform plan' #60

New issue

Closed

opened 2026-05-06 12:36:51 +02:00 by BreizhHardware · 5 comments

BreizhHardware commented

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

Owner

Originally created by @tarak666 on GitHub (Apr 2, 2024).
Original GitHub issue: https://github.com/patrickchugh/terravision/issues/113

I have running code and when i run terraform plan and apply it works on CLI, but when i run here it shows bwlo error.
ERROR: Invalid output from 'terraform plan' command. Try using the terraform CLI first to check source files have no errors.

Output:
Preflight check..
dot command detected: /cygdrive/c/ProgramData/chocolatey/bin/dot
gvpr command detected: /cygdrive/c/ProgramData/chocolatey/bin/gvpr
git command detected: /usr/bin/git
terraform command detected: /usr/bin/terraform

Checking Terraform Version...

Terraform v1.7.2

Initializing the backend...

Initializing provider plugins...

Reusing previous version of hashicorp/aws from the dependency lock file
Installing hashicorp/aws v5.39.0...
Installed hashicorp/aws v5.39.0 (signed by HashiCorp)

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

Initalising workspace: default

Generating Terraform Plan..

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the
following symbols:

create

Terraform will perform the following actions:

aws_instance.myec2vm will be created

resource "aws_instance" "myec2vm" {
- ami = "ami-01387af90a62e3c01"
- arn = (known after apply)
- associate_public_ip_address = (known after apply)
- availability_zone = (known after apply)
- cpu_core_count = (known after apply)
- cpu_threads_per_core = (known after apply)
- disable_api_stop = (known after apply)
- disable_api_termination = (known after apply)
- ebs_optimized = (known after apply)
- get_password_data = false
- host_id = (known after apply)
- host_resource_group_arn = (known after apply)
- iam_instance_profile = (known after apply)
- id = (known after apply)
- instance_initiated_shutdown_behavior = (known after apply)
- instance_lifecycle = (known after apply)
- instance_state = (known after apply)
- instance_type = "t3.micro"
- ipv6_address_count = (known after apply)
- ipv6_addresses = (known after apply)
- key_name = (known after apply)
- monitoring = (known after apply)
- outpost_arn = (known after apply)
- password_data = (known after apply)
- placement_group = (known after apply)
- placement_partition_number = (known after apply)
- primary_network_interface_id = (known after apply)
- private_dns = (known after apply)
- private_ip = (known after apply)
- public_dns = (known after apply)
- public_ip = (known after apply)
- secondary_private_ips = (known after apply)
- security_groups = (known after apply)
- source_dest_check = true
- spot_instance_request_id = (known after apply)
- subnet_id = (known after apply)
- tags = {
  - "Name" = "EC2 Demo"
    }
- tags_all = {
  - "Name" = "EC2 Demo"
    }
- tenancy = (known after apply)
- user_data = "fc08a413e16a57e0b0c0ca2bdd2ce0235f020f12"
- user_data_base64 = (known after apply)
- user_data_replace_on_change = false
- vpc_security_group_ids = (known after apply)
  }

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

────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────

Saved the plan to: /tmp/tfplan.bin

To perform exactly these actions, run the following command to apply:
terraform apply "/tmp/tfplan.bin"

Analysing plan..

ERROR: Invalid output from 'terraform plan' command. Try using the terraform CLI first to check source files have no errors.

Originally created by @tarak666 on GitHub (Apr 2, 2024). Original GitHub issue: https://github.com/patrickchugh/terravision/issues/113 Hi I have running code and when i run terraform plan and apply it works on CLI, but when i run here it shows bwlo error. ERROR: Invalid output from 'terraform plan' command. Try using the terraform CLI first to check source files have no errors. Output: Preflight check.. dot command detected: /cygdrive/c/ProgramData/chocolatey/bin/dot gvpr command detected: /cygdrive/c/ProgramData/chocolatey/bin/gvpr git command detected: /usr/bin/git terraform command detected: /usr/bin/terraform Checking Terraform Version... Terraform v1.7.2 Initializing the backend... Initializing provider plugins... - Reusing previous version of hashicorp/aws from the dependency lock file - Installing hashicorp/aws v5.39.0... - Installed hashicorp/aws v5.39.0 (signed by HashiCorp) Terraform has been successfully initialized! You may now begin working with Terraform. Try running "terraform plan" to see any changes that are required for your infrastructure. All Terraform commands should now work. If you ever set or change modules or backend configuration for Terraform, rerun this command to reinitialize your working directory. If you forget, other commands will detect it and remind you to do so if necessary. Initalising workspace: default Generating Terraform Plan.. Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols: + create Terraform will perform the following actions: # aws_instance.myec2vm will be created + resource "aws_instance" "myec2vm" { + ami = "ami-01387af90a62e3c01" + arn = (known after apply) + associate_public_ip_address = (known after apply) + availability_zone = (known after apply) + cpu_core_count = (known after apply) + cpu_threads_per_core = (known after apply) + disable_api_stop = (known after apply) + disable_api_termination = (known after apply) + ebs_optimized = (known after apply) + get_password_data = false + host_id = (known after apply) + host_resource_group_arn = (known after apply) + iam_instance_profile = (known after apply) + id = (known after apply) + instance_initiated_shutdown_behavior = (known after apply) + instance_lifecycle = (known after apply) + instance_state = (known after apply) + instance_type = "t3.micro" + ipv6_address_count = (known after apply) + ipv6_addresses = (known after apply) + key_name = (known after apply) + monitoring = (known after apply) + outpost_arn = (known after apply) + password_data = (known after apply) + placement_group = (known after apply) + placement_partition_number = (known after apply) + primary_network_interface_id = (known after apply) + private_dns = (known after apply) + private_ip = (known after apply) + public_dns = (known after apply) + public_ip = (known after apply) + secondary_private_ips = (known after apply) + security_groups = (known after apply) + source_dest_check = true + spot_instance_request_id = (known after apply) + subnet_id = (known after apply) + tags = { + "Name" = "EC2 Demo" } + tags_all = { + "Name" = "EC2 Demo" } + tenancy = (known after apply) + user_data = "fc08a413e16a57e0b0c0ca2bdd2ce0235f020f12" + user_data_base64 = (known after apply) + user_data_replace_on_change = false + vpc_security_group_ids = (known after apply) } Plan: 1 to add, 0 to change, 0 to destroy. ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── Saved the plan to: /tmp/tfplan.bin To perform exactly these actions, run the following command to apply: terraform apply "/tmp/tfplan.bin" Analysing plan.. ERROR: Invalid output from 'terraform plan' command. Try using the terraform CLI first to check source files have no errors.

BreizhHardware closed this issue

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

BreizhHardware commented

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

Author

Owner

@patrickchugh commented on GitHub (Apr 7, 2024):

hello @tarak666 can you share your terraform source so I can try to reproduce?

@patrickchugh commented on GitHub (Apr 7, 2024): hello @tarak666 can you share your terraform source so I can try to reproduce?

BreizhHardware commented

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

Author

Owner

@tarak666 commented on GitHub (Apr 8, 2024):

Here is my Code
https://github.com/tarak666/terraform-aws-projects.git

@tarak666 commented on GitHub (Apr 8, 2024): Here is my Code https://github.com/tarak666/terraform-aws-projects.git

BreizhHardware commented

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

Author

Owner

@seanfaubus commented on GitHub (May 2, 2024):

I'm getting the same error for a lot of the tf written at my company. Is there a particular way you have seen Terravision work best? Is it best to have all code in one file?

@seanfaubus commented on GitHub (May 2, 2024): I'm getting the same error for a lot of the tf written at my company. Is there a particular way you have seen Terravision work best? Is it best to have all code in one file?

BreizhHardware commented

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

Author

Owner

@AnasAbdulatif commented on GitHub (Mar 26, 2025):

any solution ?

@AnasAbdulatif commented on GitHub (Mar 26, 2025): any solution ?

BreizhHardware commented

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

Author

Owner

@patrickchugh commented on GitHub (Dec 16, 2025):