big-spring-14945
05/04/2023, 12:49 PMgarden run workflow
command (now run-workflow
) can be quite confusing.
E.g. with the following config, run workflow
fails with a very cryptic error message, and run-workflow
succeeds:
kind: Project
name: repro
environments:
- name: default
providers:
- name: exec
initScript: exit 1
---
kind: Workflow
name: test
steps:
- script: echo FOO
name: setup
ancient-diamond-80011
05/04/2023, 12:50 PMbig-spring-14945
05/04/2023, 12:51 PMancient-diamond-80011
05/04/2023, 12:52 PMgarden run workflow
in bonsai, here at https://github.com/garden-io/garden/blob/f99db5321ce1eb0927b13b918b50c3a8f4aa0398/core/src/commands/run.ts#L211-L223
but the issue is that the check for it is below the getConfigGraph call here, which initializes providers https://github.com/garden-io/garden/blob/f99db5321ce1eb0927b13b918b50c3a8f4aa0398/core/src/commands/run.ts#L113big-spring-14945
05/04/2023, 12:52 PMancient-diamond-80011
05/04/2023, 12:53 PMrun
, and in bonsai, garden run
is intended for those
so there's a new, separate command run-workflow
for thosebig-spring-14945
05/04/2023, 12:54 PMancient-diamond-80011
05/04/2023, 12:54 PMbig-spring-14945
05/04/2023, 12:54 PMswift-garage-61180
05/04/2023, 2:33 PMgarden workflow
rather than garden run-workflow
.
Feels more consistent with the new CLI in general.workflow
when none is found ("Note: The garden run workflow
command has been renamed to garden run-workflow
in 0.13").run workflow
in Bonsaialert-helicopter-61082
05/04/2023, 6:32 PMancient-diamond-80011
05/05/2023, 7:45 AM