Closed ccouzens closed 1 year ago
@ccouzens That usually means the action was not supplied a GitHub token to use for the API requests.
Could you try this and see if it works for you?
- name: Set up Fastly CLI
uses: fastly/compute-actions/setup@v2
with:
token: ${{ secrets.GITHUB_TOKEN }}
@ccouzens did using a GitHub token resolve the issue for you?
Hi, we have always had a github token setup in this workflow.
We haven't seen the issue again, so I'm dismissing it as a blip and closing the issue.
Thank you for your time.
@JakeChampion Did you mean to suggest adding a fastly token here rather than a github token here. This looks like a rate limit from fastly rather than a rate limit from github
- uses: fastly/compute-actions/deploy@v2
env:
FASTLY_API_TOKEN: ${{ secrets.FASTLY_API_TOKEN }}
I did not, this is a GitHub rate limit and is solved by providing the token from the running action like so:
- name: Set up Fastly CLI
uses: fastly/compute-actions/setup@v2
with:
token: ${{ secrets.GITHUB_TOKEN }}
Sorry for my confusion. Thanks!
We had a failed deploy caused by a rate limiting error:
I presume Github Actions runner was rate limited downloading the
fastly
package from Github.The IP Address is Microsoft's and presumably the IP of the Github runner.