Bryan MacFarlane

@karancode the reason that's an envvar is there's many scenarios (service) where it won't work as the service ends up running as a user (the user configured or one specified)....

there's an old POC PR which has rotted on the vine a bit which has the start of what alpine would look like https://github.com/actions/runner/pull/495

@hross since he's driving this area now. I imagine it's not hard technically but more of a matter of official support, building / dist, docs etc. etc. but I'm guessing...

@chrispat is correct. Essentially it's user code running on a machine as admin. Not really securable. Which means you have to trust who can edit your workflow file or in...

Thanks for creating an issue and the suggestion! Just wanted to point out that the curl example above is possible with the http-client. Get takes an url which can include...

@ericsciple

I disagree that it's the design goal to solve query string params. The design goal of the auth handlers was to be able to delay inject headers for all calls...

@joshmgross - since this is so specific to the caller, scenario, and potentially a dangerous thing to do, I think it's best for the consumer to do the retries. Either...

You can populate a tool cache directory with various versions and it will work. I will try and write something up. (hint: run env to see the tool cache root...

https://github.com/actions/setup-ruby/issues/44