Repository navigation
Keep identity hash when binding with --accept-all-permission-claims - #4545
Conversation
Signed-off-by: Raphael Fakhri <153192858+RaphaelFakhri@users.noreply.github.com>
|
Hi @RaphaelFakhri. Thanks for your PR. I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
|
LGTM label has been added. DetailsGit tree hash: a7f0050107fa643b5a3fca34c5b0391548ef9a0b |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ntnn The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Summary
kubectl kcp bind apiexport --accept-all-permission-claimsand--reject-all-permission-claimscopied only the group and resource of each APIExport permission claim into the APIBinding. Claims on resources from other APIExports carry an identity hash, so the accepted claim never matched the exported claim and was not applied.This change copies
IdentityHashfrom the APIExport claim and moves the claim-building loop out ofRunintoaddAllPermissionClaimsso it can be unit tested.TestAddAllPermissionClaimsfails without the fix and passes with it.What Type of PR Is This?
/kind bug
Related Issue(s)
Fixes #4544
Release Notes