From 9dcc841f31e330f64741f6736c29f04e4fd77b83 Mon Sep 17 00:00:00 2001 From: Martin Atkins Date: Mon, 24 Sep 2018 14:59:55 -0700 Subject: [PATCH] core: Fix TestContext2Apply_cancel Now that we populate a resource-level state pre-emptively for a resource, before we apply the instances of that resource, it is no longer true that this produces only one resource state, but the test below (comparing the string version of the state) already captures the expected behavior and so this additional check was redundant anyway. --- terraform/context_apply_test.go | 5 ----- 1 file changed, 5 deletions(-) diff --git a/terraform/context_apply_test.go b/terraform/context_apply_test.go index 080c2341a..a0b6f7635 100644 --- a/terraform/context_apply_test.go +++ b/terraform/context_apply_test.go @@ -1906,11 +1906,6 @@ func TestContext2Apply_cancel(t *testing.T) { t.Fatalf("unexpected errors: %s", applyDiags.Err()) } - mod := state.RootModule() - if len(mod.Resources) != 1 { - t.Fatalf("bad: %s", state.String()) - } - actual := strings.TrimSpace(state.String()) expected := strings.TrimSpace(testTerraformApplyCancelStr) if actual != expected {