in 0.12 you could list a disabled task as a dependency and it would consider that dependency satisfied without running it as of 0.13 listing a run action as a dependency will cause it to run even if its disabled is there a way to match the 0.12 behaviour? i did notice workflows appear to have some syntax around skipping actions etc, is it intended to deal with this via workflows now?

@mammoth-flag-56137 can you define "task" here? Is this any action?

a run action

Gotcha. I myself am confused by this as the docs explicitly mention that dependencies that refer to a disabled action are ignored: https://docs.garden.io/reference/action-types/run/exec#disabled

in 0.12 you could have (psuedo code)

module
deps:
  - taskfoo
  - taskbar

tasks:
  taskfoo:
    disabled: true
  taskbar:
    disabled: false

and garden would only run taskbar before deploying the module

But @flat-state-47578, in the thread below, mentioned that disabled actions run if set as a dependency https://discord.com/channels/817392104711651328/1198800256935141396/1198809423066435654

now in 0.13 if you add a run action as a dep of a deploy action it will always run even if the run action is set to disabled

Yes, this seems odd to me. I'll ping the engineers.

btw ek is my jnr which is why the two of us are making all these threads, we're trying to move from 0.12 to 0.13 and having a FUN time of it 😛

Oh wow, haha, well good to have you both here with us! Migrations are always fun 😅

we're two steps away from getting a fresh deploy of a new env using 0.13 working, then will come finding out what happens when we try to 'upgrade' from an old 0.12 deploy

Hi @mammoth-flag-56137! Thanks for flagging this. I'll take a look at this in the coming days, will hopefully be a simple fix.

yay, thank you