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
The problem I'm trying to solve:
helm2's --timeout flag specified a number of seconds for the timeout. In helm3 it uses a string formatted for golang's ParseDuration function, e.g. "200s".
If someone is upgrading from drone-helm and they have a timeout: 200 in their settings, it won't do what they expect. I'm not sure whether helm will just exit with an error or set the timeout to 0, but either way the deployment won't succeed.
How I imagine it working:
I see two options:
Say "update your timeout setting" in the "Upgrading from drone-helm" section of the readme
If we see a bare number in cfg.Timeout, append an s so it means the same thing it did in helm2
The text was updated successfully, but these errors were encountered:
Helm2's --timeout took a number of seconds, rather than the
ParseDuration-compatible string that helm3 uses. For backward-
compatibility, update a bare number into a duration string.
The problem I'm trying to solve:
helm2's
--timeout
flag specified a number of seconds for the timeout. In helm3 it uses a string formatted for golang'sParseDuration
function, e.g. "200s".If someone is upgrading from drone-helm and they have a
timeout: 200
in their settings, it won't do what they expect. I'm not sure whether helm will just exit with an error or set the timeout to 0, but either way the deployment won't succeed.How I imagine it working:
I see two options:
s
so it means the same thing it did in helm2The text was updated successfully, but these errors were encountered: