Skip to content

Commit 329762b

Browse files
committed
remove destroy_ events from list
I expect these will come back, but since we don't have a firm roadmap just yet it's better not to make future promises.
1 parent 9b015c6 commit 329762b

File tree

1 file changed

+1
-15
lines changed

1 file changed

+1
-15
lines changed

internal/configs/action.go

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -129,25 +129,11 @@ func decodeActionTriggerBlock(block *hcl.Block) (*ActionTrigger, hcl.Diagnostics
129129
event = BeforeUpdate
130130
case "after_update":
131131
event = AfterUpdate
132-
case "before_destroy":
133-
event = BeforeDestroy
134-
case "after_destroy":
135-
event = AfterDestroy
136132
default:
137133
diags = append(diags, &hcl.Diagnostic{
138134
Severity: hcl.DiagError,
139135
Summary: fmt.Sprintf("Invalid \"event\" value %s", hcl.ExprAsKeyword(expr)),
140-
Detail: "The \"event\" argument supports the following values: before_create, after_create, before_update, after_update, before_destroy, after_destroy.",
141-
Subject: expr.Range().Ptr(),
142-
})
143-
continue
144-
}
145-
146-
if event == BeforeDestroy || event == AfterDestroy {
147-
diags = append(diags, &hcl.Diagnostic{
148-
Severity: hcl.DiagError,
149-
Summary: "Invalid destroy event used",
150-
Detail: "The destroy events (before_destroy, after_destroy) are not supported as of right now. They will be supported in a future release.",
136+
Detail: "The \"event\" argument supports the following values: before_create, after_create, before_update, after_update.",
151137
Subject: expr.Range().Ptr(),
152138
})
153139
continue

0 commit comments

Comments
 (0)