You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
spacelift_stack_destructor is special because it is not a resource per se but rather a marker that triggers the destruction of a stack's resources. I am not sure how exposing it via a data source makes sense.
Hey @Radkowski - thanks for the context. Would this be used in the depends_on attribute? for example: depends_on = data.spacelift_stack_destructor.example ? if not, I'd be curious to how you'd leverage this.
It is possible to create destructor using resource "spacelift_stack_destructor" "example" { ... }
...but it is not possible to read already created destructor details via data_source.
It could be ideally to have a data source in spacelift provider that allows to get destructorID based on stackID, for example:
data "spacelift_stack_destructor" "example" {
stack_id = "1234567890qwertyuiop"
}
…that returns all destructor-related data, including destructor_id
The text was updated successfully, but these errors were encountered: