-
Notifications
You must be signed in to change notification settings - Fork 328
updating the RBAC +ABAC scenario of ACR #510
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
base: main
Are you sure you want to change the base?
updating the RBAC +ABAC scenario of ACR #510
Conversation
the acrpull wont work if container is configured for ABAC the identity should have the **Container Registry Repository Contributor** role
@sanjayananthamurthy : Thanks for your contribution! The author(s) and reviewer(s) have been notified to review your proposed change. |
Learn Build status updates of commit 18d03ea: 💡 Validation status: suggestions
articles/machine-learning/concept-endpoints-online-auth.md
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. |
Can you review the proposed changes? Note: The new alt text needs to be updated to match Microsoft standards. Important: When the changes are ready for publication, adding a #label:"aq-pr-triaged" |
#sign-off |
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @s-polly |
Learn Build status updates of commit 40380d4: ✅ Validation status: passed
For more details, please refer to the build report. |
Hi @sanjayananthamurthy - In the public repo, pull requests should be signed off by the author, another member of the content team, or a PM. @dem108 - Could you take a look? Thanks! |
> | ||
>  | ||
> | ||
>In this case some existing role assignments aren't honored or will have different effects, because a different set of ACR built-in roles apply to ABAC-enabled registries. |
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.
>In this case some existing role assignments aren't honored or will have different effects, because a different set of ACR built-in roles apply to ABAC-enabled registries. | |
>In this case, some existing role assignments aren't honored or will have different effects, because a different set of ACR built-in roles apply to ABAC-enabled registries. |
> [!IMPORTANT] | ||
> If you configure your Container registry to use **[RBAC Registry + ABAC Repository Permissions](/azure/container-registry/container-registry-rbac-abac-repository-permissions?tabs=azure-portal)** | ||
> | ||
>  |
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.
This image doesn't exist. Please replace it with a valid one.
the acrpull wont work if container is configured for ABAC the identity should have the Container Registry Repository Contributor role