Add Circle CI API token to request header if available #26519
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow up of #26499
A Circle CI team member got back to me. It is indeed not necessary, but they had a regression not long ago on fetching without token.
https://discuss.circleci.com/t/is-api-token-required-when-fetching-artifacts/47606/5
To mitigate the impact of this kind of issues, let's add this token to requests' header when it's available.