The current spacelift_stack data source is nice but it will fail if the stack cannot be found.
If there is a spacelift_stacks data source, much like aws_iam_roles data source, then we can try to find a stack and if it fails, it can quietly return zero results.
Use case, see differences between what our current label is with what the new label is.
If the current label is a shasum of a non-committed mounted file and the new label is a new shasum of the changed non-committed mounted file, then we can use spacelift_run to trigger it.
@nitrocode That is a great suggestion. We will add the support for spacelift_stacks (plural) data source to our backlog, but I cannot tell at this moment when we will implement it.
The current
spacelift_stack
data source is nice but it will fail if the stack cannot be found.If there is a
spacelift_stacks
data source, much likeaws_iam_roles
data source, then we can try to find a stack and if it fails, it can quietly return zero results.Use case, see differences between what our current label is with what the new label is.
If the current label is a shasum of a non-committed mounted file and the new label is a new shasum of the changed non-committed mounted file, then we can use
spacelift_run
to trigger it.