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
Create a set of circumstances where one of the actions in a project will resolve to disabled: true and then run garden get actions --detail. The result will be an error like
me: ~/staging/repo (garden-bonsai) $ garden get actions --detail --env dns
Get Actions 📖
Garden v0.13 (Bonsai) is a major release with significant changes. Please help us improve it by reporting any issues/bugs here:
https://go.garden.io/report-bonsai
→ Run garden util hide-warning 0.13-bonsai to disable this warning.
ℹ garden → Running in Garden environment dev
ℹ providers → Getting status...
✔ providers → Cached (took 1.9 sec)
ℹ providers → Run with --force-refresh to force a refresh of provider statuses.
ℹ graph → Resolving actions and modules...
✔ graph → Done (took 39.4 sec)
Deploy type=container name=something-or-other is disabled.
Expected behavior
I expect garden get actions --detail to retrieve details about all actions, or at least all enabled actions, without erroring out because it discovers some actions are disabled.
Reproducible example
Workaround
Make sure every single action is enabled I guess?
Suggested solution(s)
Additional context
Your environment
OS: macOS 13.4.1 (c)
How I'm running Kubernetes: AKS (Azure)
garden version: 0.13.10-edge-bonsai-a65f2c49d
The text was updated successfully, but these errors were encountered:
To add some more context, --detail flag also goes through each action to list down the dependents of each action which in return calls getActionByKind and there it fails if an action is disabled.
Garden Bonsai (0.13) Bug
Current Behavior
Create a set of circumstances where one of the actions in a project will resolve to
disabled: true
and then rungarden get actions --detail
. The result will be an error likeExpected behavior
I expect
garden get actions --detail
to retrieve details about all actions, or at least all enabled actions, without erroring out because it discovers some actions are disabled.Reproducible example
Workaround
Make sure every single action is enabled I guess?
Suggested solution(s)
Additional context
Your environment
13.4.1 (c)
garden version: 0.13.10-edge-bonsai-a65f2c49d
The text was updated successfully, but these errors were encountered: