update(ci): use an explicit role instead of a secret #21
Conversation
The role ARN is not a secret and does not allow any access by itself. However, adding it here explicitly makes it easier to troubleshoot potential issues. Signed-off-by: Luca Guerra <[email protected]>
|
@LucaGuerra: The label(s) In 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 kubernetes/test-infra repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: FedeDP, LucaGuerra The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. Git tree hash: afdb9e1972bf164ff9c21f82c7c7dbf3a3a0334b
|
|
/milestone falco-rules-1.0.0 |
Signed-off-by: Luca Guerra [email protected]
What type of PR is this?
/kind cleanup
Any specific area of the project related to this PR?
/area build
What this PR does / why we need it:
The role ARN is not a secret and does not allow any access by itself. However, adding it here explicitly makes it easier to troubleshoot potential issues.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: