Conditional actions in pipelines
Bit of context: I've got a one-size-fits-all pipeline that deploys all our various services, as they're all very similarly shaped. This is working great as it keeps things very nice and standardised, and we're using variables to target specific environments and clusters and tags and such.
There's one small difference for a few services - they have a container that runs as part of the deploy process as essentially a one-off. There's a few containers like that for all services, and I explicitly stop them once the health check has passed and we're good, to avoid them getting kicked back to life every 10 minutes, but I can't do that with this specific container as not all stacks I deploy have something like it.
So for this use case I'd love some kind of "stop this container if it exists", or even a "stop this container, but ignore any errors that might cause for the purposes of this pipeline". There' probably other ways to address this I haven't thought of, as well.
This makes a lot of sense. Will need to spend some time noodling to see how we can add this sort of logic in without overcomplicating pipelines.
Thanks for that. One suggestion to throw into the ring: Marking a step as 'don't stop running if this fails' is probably useful more generally, and would solve this issue nicely, too. It's also reasonably straight forward conceptually.
Hey Thomas, thanks for the additional note! I've got this whole idea logged in our feature request tracker. I will notify you as soon as we make some progress here :)