terraform-plan-parser
terraform-plan-parser copied to clipboard
lifeomic
Command line utility and JavaScript API for parsing stdout from "terraform plan" and converting it to JSON.
Hi, I'm running plan in terraform 13 and getting this parsing error(pasted below). Unable to manage the infrastructure. ``` Refreshing Terraform state in-memory prior to plan... The refreshed state will...
Cannot parse this destroy line From `terraform-plan.stdout` ``` - module.service.module.service.module.blue.aws_launch_configuration.default (deposed) ``` ``` $ parse-terraform-plan -i terraform-plan.stdout | jq .errors[0] { "code": "UNABLE_TO_PARSE_CHANGE_LINE", "message": "Unable to parse \" - module.service.module.service.module.blue.aws_launch_configuration.default...
This is in reference to #23 I opened earlier this week. I had some free time and figured I would take a stab at it. It attempts to add the...
See: https://www.terraform.io/docs/internals/json-format.html
I was using terraform 0.12.x and get the following: ``` { "errors": [ { "code": "UNABLE_TO_PARSE_LINE", "message": "Unable to parse \" # aws_instance.kaeptn-eichhorn will be created\" (ignoring)" }, { "code":...
I ran into an issue with a deposed resource, which is currently not supported by terraform-plan-parser. This change adds the support.
It seems like this could be useful for automation as the stored plan objects are needed to ensure a consistent state is applied. Failure is caused by the lack of...
Sort of related to this issue https://github.com/lifeomic/terraform-plan-parser/issues/20 Coinbase has a great tool called [landscape](https://github.com/coinbase/terraform-landscape) and makes the plan output a lot easier to read. It would be nice to be...
For the following plan: ``` An execution plan has been generated and is shown below. Resource actions are indicated with the following symbols: ~ update in-place -/+ destroy and then...
Parse complex attributes as maps and arrays instead of separate attribute per item. Given resource: ``` resource "null_resource" "cluster" { triggers { cluster_instance_ids = "id" } ``` Current output: ```...
