https://garden.io logo
#💻|dev
Title
# 💻|dev
c

calm-family-29323

05/02/2023, 12:13 PM
@alert-helicopter-61082 Currently it seems that the task status is resolved even if
force == true
which seems unnecessary I think it'd make sense to just execute the actions and not even bother resolving the statuses
a

alert-helicopter-61082

05/02/2023, 12:32 PM
This is because the process handlers currently need the status to be resolved. In most cases, the process handler (e.g. deploy, run etc.) needs to query for status upfront anyway, so it doesn't end up being a lot of extra work or time.
c

calm-family-29323

05/02/2023, 12:35 PM
alright
cc @swift-garage-61180
s

swift-garage-61180

05/02/2023, 6:40 PM
On that note: I think we could speed things up a bit by providing the
status
to the router method and leveraging that in e.g. deployment handlers. For example, this status: https://github.com/garden-io/garden/blob/0.13/core/src/tasks/deploy.ts#L107-L113 Could be used instead of refetching it here: https://github.com/garden-io/garden/blob/0.13/core/src/plugins/kubernetes/container/deployment.ts#L60
Same applies for
helm
Deploys (but not
kubernetes
Deploys, at a glance).
The status checks should be relatively cheap, though, so this is probably not hi-pri. I'd be happy to look into this when we think the time is right (and if we think it's a good idea).