-
Notifications
You must be signed in to change notification settings - Fork 83
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
ci: use pull_request instead of pull_request_target for Actions #380
ci: use pull_request instead of pull_request_target for Actions #380
Conversation
echo ${{ secrets.SERVICE_ACCOUNT_SIGNING_KEY }} | base64 -d > sa.key | ||
echo ${{ secrets.SERVICE_ACCOUNT_KEY }} | base64 -d > sa.pub | ||
openssl genrsa -out sa.key 2048 | ||
openssl rsa -in sa.key -pubout -out sa.pub | ||
make kind-create | ||
- name: Build azwi | ||
run: make bin/azwi | ||
- uses: azure/login@v1.4.3 |
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 like ACTIONS_ID_TOKEN_REQUEST_URL
and ACTIONS_ID_TOKEN_REQUEST_TOKEN
won't be available to this action until it's merged to the main branch, which is why azure cli login failed. Let's ignore and I will open a follow-up PR to fix the CI failure.
Signed-off-by: Ernest Wong <chuwon@microsoft.com>
Co-authored-by: Anish Ramasekar <anish.ramasekar@gmail.com>
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.
lgtm
CI failure will resolve after the follow-up PR: #380 (comment)
Reason for Change:
Uses
pull_request
instead ofpull_request_target
to prevent malicious commits.Requirements
Issue Fixed:
Please answer the following questions with yes/no:
Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
Notes for Reviewers: