-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(ecr): policytext errors when includes resource #24401
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The pull request linter has failed. See the aws-cdk-automation comment below for failure reasons. If you believe this pull request should receive an exemption, please comment and provide a justification.
A comment requesting an exemption should contain the text Exemption Request
. Additionally, if clarification is needed add Clarification Request
to a comment.
4970dbe
to
55450ae
Compare
55450ae
to
3889fe5
Compare
✅ Updated pull request passes all PRLinter validations. Dissmissing previous PRLinter review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for picking this up!
Looks like hasWarnings
should be hasWarning
, which is causing the build failure. Also just a note that on a fix the PR title should state the bug, not the solution implemented. Can you adjust that, please?
Pull request has been modified.
I tried to test this locally, but
|
Oh, we just added some linting checks are you're running up against, probably because your branch is from before we did that. It's annoying so gimme an hour or two and I'll resolve the issues on this PR. |
@Mergifyio update |
✅ Branch has been successfully updated |
@TheRealAmazonKendra I see that the codebuild failed, however when I try to click through to see the issue I end up at an AWS login. I don't imagine I have the necessary credentials. :) Anyway, I've tried and failed to run the build and test locally and can't see the output of the failed build. I'm feeling a little bit blocked here. |
Ah, I see the build logs link above. I'll chase that down. |
@Mergifyio update |
☑️ Nothing to do
|
ECR does not allow resource to be included in private repository resource policies. CFN largely swallows the error message. Most resources require or at least allow a resource in their policies, so we should at least warn. See issue aws#24314
Co-authored-by: Joshua Weber <[email protected]>
f8d2d27
to
a71d1cc
Compare
@Mergifyio update |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
My thought is that there’s nothing more fact based than a direct link to
the issue. If it makes it easier for customers to share their voice around
an issue, that’s a bonus.
On Fri, Mar 10, 2023 at 1:25 PM Joshua Weber ***@***.***> wrote:
***@***.**** commented on this pull request.
------------------------------
In ***@***.***/aws-ecr/README.md
<#24401 (comment)>:
> +a `resources` section in the `PolicyStatement`. See AWS internal ticket
+`#WRITEME` for details around the ECR and Cfn team working together to
@ahammond <https://github.com/ahammond> My opinion: The documentation is
technical and fact-based. The purpose is not to put pressure on a team to
get a desired feature.
—
Reply to this email directly, view it on GitHub
<#24401 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADM2RER3DIXGIMQW4XUL6DW3OL5RANCNFSM6AAAAAAVMKXHUI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
MiniLockID: uX4VrN5FvyFxFCxgTksGxJqvKa16iBhqseYxxA1UkZVJw
GPG: 773A 6BDD 71CE 0AB8 0F5A 1176 8679 A114 FB1A 69BD
|
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
6 similar comments
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
This PR has been in the MERGE CONFLICTS state for 3 weeks, and looks abandoned. To keep this PR from being closed, please continue work on it. If not, it will automatically be closed in a week. |
@TheRealAmazonKendra PR updated. |
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
1 similar comment
This PR cannot be merged because it has conflicts. Please resolve them. The PR will be considered stale and closed if it remains in an unmergeable state. |
a32ca7c
to
4d26f49
Compare
@TheRealAmazonKendra updated again. Please merge. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
ECR does not allow resource to be included in private repository resource policies.
CFN largely swallows the error message.
Most resources require or at least allow a resource in their policies, so we should at least warn.
See issue #24314