OCPBUGS-96892: Revert "OCPBUGS-87829: Scope minted AWS IAM policies to cluster-owned resources"#1057
Conversation
…o cluster-owned resources" This reverts commit 383d3a2 (PR openshift#1043).
|
@redhat-chai-bot: This pull request references Jira Issue OCPBUGS-96892, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
Warning Review limit reached
Next review available in: 23 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository: openshift/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (5)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: redhat-chai-bot The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
/payload-job periodic-ci-openshift-release-main-nightly-5.0-e2e-aws-csi If this passes I will merge the revert today. |
|
@dgoodwin: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command
See details on https://pr-payload-tests.ci.openshift.org/runs/ci/468eaa30-76e1-11f1-9fce-07bb33211d05-0 |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #1057 +/- ##
==========================================
- Coverage 47.28% 47.03% -0.25%
==========================================
Files 97 97
Lines 12631 12583 -48
==========================================
- Hits 5973 5919 -54
- Misses 6001 6008 +7
+ Partials 657 656 -1
🚀 New features to boost your workflow:
|
|
@redhat-chai-bot: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Summary
This reverts commit 383d3a2 (PR #1043), which introduced scoped IAM policies for cluster-owned resources.
Why
PR #1043 caused multiple regressions in the
e2e-aws-csijob — all snapshot-related tests have been permafailing since Jun 29. This has blocked PRs from merging in any repository that usesaws-csias a required presubmit, includingopenshift/origin.Merge conflict resolution
PR #1053 (OCPBUGS-95187: Reclassify
ec2:ModifyNetworkInterfaceAttributeas unscoped) modified the scoped/unscoped action maps introduced by #1043. Since this revert removes those maps entirely, #1053's changes are also effectively reverted and will need to be re-applied when the scoping feature is re-landed.Unreverting
To unrevert, please land a corrected version of this feature that fixes the snapshot test failures and verify with:
A fix is being investigated in PR #1054.