-
Notifications
You must be signed in to change notification settings - Fork 240
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
Fork origin pull requests are currently blocked #1807
Comments
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been marked as stale for 30 days with no activity. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been marked as stale for 30 days with no activity. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been marked as stale for 30 days with no activity. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been marked as stale for 30 days with no activity. |
Pull Requests began to experience a high rate of failure due to throttling from Public ECR when pulling images. These throttling errors have been experiences in the past but have often been mitigated by rerunning the workflow. Recently (~1week) throttling failures continued to happen even after numerous retries.
In an attempt to mitigate this issue credentials account credentials were added to the PR Build workflow. This allows login to Public ECR so requests made are authenticated. This alleviated the issue but created a new one. Secrets are not passed to workflows. Putting the IAM Role ARN in plain text will also not solve the issue. OIDC authorization will continue to fail due to the subject claim for fork origin pull requests. This has been tested on a fork and the failing behavior has been validated.
Current Mitigation Steps: If you have write access to this repository then push your branch to this remote ref. Submit your PR and the PR Build workflow will be able to make authenticated requests to Public ECR
Possible Solutions:
The text was updated successfully, but these errors were encountered: