Michael Grosser

I think changing resources always requires a re-deploy, whereas updating replicas could be done without. Having a lightweight UI that changes scale sounds fine to me, but one that re-deploys...

Restarting, scaling down and lowering the number of resources might kinda dangerous though, so we'd need that to be documented somewhere and buddy-checked. So it need to be a deploy...

Periodic deploys might be helpful see https://github.com/zendesk/samson/pull/2175 this will deploy selected stages once a day (you can chose the interval but not the start time) /fyi @yizhang-zen

using cron sounds like a decent solution ... keeping track of timers etc inside of samson sounds like a lot of work that won't be used by many users and...

Yeah ... Could create deploys with scheduled at field ... Then make sure to never start them ... And have a timer check/start them every minute or so On Nov...

kk, fix coming in a week or so ... PR welcome if you know how to fix

In general the `1-off job` usecase is not well supported since we don't use it because it is a compliance issue when any developer can execute random code on production....

I don't use hangouts and would prefer to keep the discussion here.

I like the capturing of err and out! not a fan of openstruct though, prefer a Hash ... even better with a `success, out, err` triplet 🤷‍♂

I think we opted to make it simple to reduce the number of api requests ... ideally we would get the sha and then cache on that without having to...