-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GitHub Token on GitHub Enterprise Server does not work #185
Comments
I did anticipate this, so you can check my theories: Does
Just know that you'll be subject to as low as a 60 requests per hour rate limit, depending on how many public IPs are associated with your GHES install. You may not notice, since it becomes an obvious problem with shared Actions runners, which also execute jobs for other orgs. |
Thank you. I tried your suggestion. And it works :-) Is it possible to completely avoid accessing the GitHub Api or minimize it to not run in such problems? |
No, the GitHub API is used to discover releases. HashiCorp runs their own release infrastructure for both CLIs and plugins at a substantial cost. If you want a fixed version rather than discovery, bundling will work. Keep in mind you need to do this for both TFLint itself and plugins. The internal mechanism in the CLI for loading plugins uses the same mechanics as this action, minus the ability to use "latest." Running |
When we use this action on GitHub Enterprise Server the default github token does not work (HttpError: Bad credentials)
Can this action be fixed to be used without a token? Or is there any other approach?
But: We do not want to put GitHub.Com Tokens into our GitHub Enterprise Instance.
Thanks a lot.
The text was updated successfully, but these errors were encountered: