Seth Vargo

Hi @sochoa Thank you for opening an issue. This is not something that is currently planned, but sounds like a great idea. I have tagged as an enhancement. We would...

Hi @sochoa We do not have an "developer documentation", but you can follow the pattern in the existing GitHub authentication backend, for example. You might also be able to extend...

This was a change from https://github.com/sethvargo/go-limiter/issues/27. I think I just need to update the content.

Pull Requests are welcome!

Hi @tomorr-rexhepi - is this happening consistently? Are you using GitHub-managed runners or self-hosted runners?

Given there are no other reports, this is most likely a proxy or egress firewall configuration on your self-hosted runners.

Not unless there were core Node.js changes to proxy configurations between those versions.

`berglas exec` will run the container command, so if the command is /bin/sh, it will resolve secrets and then start a shell. Without logs, it's very difficult to diagnose.

Is this related to https://issuetracker.google.com/issues/322167526?

Sure, please include the debug logs and IAM permissions that you've granted to the WIF pool though.