-
Notifications
You must be signed in to change notification settings - Fork 273
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FEATURE]: Conditionally disable steps in workflows #1927
Comments
Good idea—I think we should have a look at this one soon. |
Hi @noizwaves and thanks for the feature request. I agree that this makes sense. An alternative would be to add an That would make it easier to disable a step for more than one environment. Of course we could also do both, if there's a use case for disabling a workflow or a workflow step in other contexts. |
Feature Request
Background / Motivation
In our usage of Garden, we need to run a task after deploying services. Before Garden 0.12, we would invoke
garden
CLI twice in adeploy.sh
script. With 0.12, we upgraded to use Garden Workflows 🙌.Now, we have a need to run this task conditionally. For my specific use case, it is conditional on whether a user has selected to deploy a specific application.
What should the user be able to do?
I could see it being useful for steps in Garden workflows to be conditionally disabled.
Why do they want to do this? What problem does it solve?
We've worked around this by making the task name conditional. In the case where the task should not be run, we instead run a
noop
task:Suggested Implementation(s)
I imagine a new key in the step definition called
disabled
(to match the existingdisabled
option on other modules/services). It would look something like this:How important is this feature for you/your team?
🌹 It’s a nice to have, but nice things are nice 🙂
The text was updated successfully, but these errors were encountered: