Closed KaKeimei closed 3 years ago
Hi @KaKeimei. Thanks for your PR.
I'm waiting for a jenkins-x member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign garethjevans
You can assign the PR to them by writing /assign @garethjevans
in a comment when ready.
The full list of commands accepted by this bot can be found here.
/assign @garethjevans
@KaKeimei can you fix the PR title and commit to follow the semantic convention?
Nice catch btw.
Something like this will work:
fix: add object access to visualizer policy
@KaKeimei can you fix the PR title and commit to follow the semantic convention? Nice catch btw. Something like this will work:
fix: add object access to visualizer policy
OK, I'll close this one and create a new PR that follows semantic convention
Give not only bucket access but also object access to the visualizer, or it will get no access to the logs:
status code: 403, request id: 6301D24E45EF1903, host id: Lqtrx39JLM289tl7UODgB2z3V53nGuxv7kLVNQse8qw7ZqmBfh/JIogNBcWGOuAyaj4dE83Fwpk=
Description
Special notes for the reviewer(s)
Which issue this PR fixes
fixes #