-
Notifications
You must be signed in to change notification settings - Fork 29
Open
Description
Because of the high level of detail in data encoded in Plan it's often difficult to tell for a human what's in the plan without using some extra tooling such as jq and fully understanding the structure of the JSON. Pretty-printing the structure via tools like spew also doesn't always help, due to the amount of data:
--- FAIL: TestAccPacketSpotMarketRequest_Basic (439.06s)
testing_new_config.go:52: After applying this step, the plan was not empty. (*tfjson.Plan)(0xc0000c1b60)({
FormatVersion: (string) (len=3) "0.1",
TerraformVersion: (string) (len=7) "0.12.20",
Variables: (map[string]*tfjson.PlanVariable) <nil>,
PlannedValues: (*tfjson.StateValues)(0xc0002d3840)({
Outputs: (map[string]*tfjson.StateOutput) <nil>,
RootModule: (*tfjson.StateModule)(0xc0004bc8c0)({
Resources: ([]*tfjson.StateResource) (len=2 cap=4) {
(*tfjson.StateResource)(0xc0000d4e60)({
Address: (string) (len=19) "packet_project.test",
Mode: (tfjson.ResourceMode) (len=7) "managed",
Type: (string) (len=14) "packet_project",
Name: (string) (len=4) "test",
Index: (interface {}) <nil>,
ProviderName: (string) (len=6) "packet",
SchemaVersion: (uint64) 0,
AttributeValues: (map[string]interface {}) (len=8) {
(string) (len=16) "backend_transfer": (bool) false,
(string) (len=10) "bgp_config": ([]interface {}) {
},
(string) (len=7) "created": (string) (len=20) "2020-01-29T17:26:48Z",
(string) (len=2) "id": (string) (len=36) "96a7b2ee-c814-4b45-b607-1719757ecf49",
(string) (len=4) "name": (string) (len=36) "tfacc-spot_market_request-epxyk7xzsv",
(string) (len=15) "organization_id": (string) (len=36) "...",
(string) (len=17) "payment_method_id": (string) (len=36) "...",
(string) (len=7) "updated": (string) (len=20) "2020-01-29T17:32:54Z"
},
...
There should be a way to get a human-friendly representation of the plan, similar to output from terraform show planfile or terraform plan.
Metadata
Metadata
Assignees
Labels
No labels