You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
✖ deploy.deploy → Failed resolving status for Deploy type=kubernetes name=deploy (took 0.03 sec). Here is the output:
ENOENT: no such file or directory, open '/Users/steffen/repro/generated-manifest.yml'
Build action has not been triggered (directory .garden/build/generate/ does not exist)
It looks for generated-manifest.yml in the wrong directory
When running garden build it actually generates the file
✔ build.generate → Done (took 0 sec)
Done! ✔️
% ls .garden/build/generate/
generated-manifest.yml
Expected behavior
it should execute the build action when running garden deploy, as it is listed in dependencies
Garden Bonsai (0.13) Bug
Current Behavior
When running
garden deploy
.garden/build/generate/
does not exist)generated-manifest.yml
in the wrong directoryWhen running
garden build
it actually generates the fileExpected behavior
garden deploy
, as it is listed independencies
Reproducible example
Workaround
Unknown
Suggested solution(s)
Use the original solution (a5f5092) from #4516 and make sure there is no regression like we had in #4811. Here is the patch with the original changes:
Additional context
–
Your environment
garden version
0.13.0The text was updated successfully, but these errors were encountered: