Iain Lane

That sounds like a good idea! I might get to work on that but if I don’t get to it in time the lack of that shouldn’t block this PR...

Just to say quickly: 429 errors can come with a [`Retry-After header`](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Retry-After) telling you how long to wait before retrying. Perhaps we could extend the retrying logic to look for...

Example runs where I had hacked the action to work on pushes to `iainlane/*`: * [`master`](https://github.com/iainlane/xk6/actions/runs/4885649492) * [tag](https://github.com/iainlane/xk6/actions/runs/4885677479) (gets `latest` and `1.0.0`, the `v` is dropped) * [rc](https://github.com/iainlane/xk6/actions/runs/4885677485) (gets `1.0.0-rc.1`...

Hi, we think we have fixed this. Could folks give a re-check please? log from me trying in a fedora docker container This used to error before, as people are...

I've got it, cheers!

Yes, they're piped by us, the values are known on Tanka's side: https://github.com/grafana/tanka/blob/965612cecec8466a6f10c1ec1930b59d276b1766/pkg/helm/template.go#L31-L35 (I have checked in this case and they are the same)

Not sure. Could `server` imply using `--force` all the time and then you don't need to set two flags to use `server` in this configuration (with flux)?

I don't really mind if you want to close this, but this has the effect of making _all_ logs look nice. It's a decent practice if you ask me. But...

@julienduchesne can you help me with the CI failure please? :see_no_evil: