Skip to content
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

github: Grant actions: write permission #1580

Merged
merged 1 commit into from
Jan 15, 2024
Merged

github: Grant actions: write permission #1580

merged 1 commit into from
Jan 15, 2024

Conversation

radeksimko
Copy link
Member

As discovered by @sarahethompson the new v4 version of the action we use now requires this permission.

Not providing the permission leads to those artifacts to not be deleted, which in turn trips up other workflows related to CRT which then attempt to upload these artifacts just because they are in the same path. CRT does not currently have path allowlist to ignore such artifacts but there is an internal feature request.

This is surfaced as the following error:

Error: -15T08:59:29.463Z [ERROR] bob: Failed to download workflow artifact: org=hashicorp repo=terraform-ls error="mkdir .bob/artifacts/registry.terraform.io/1password: permission denied"

In retrospect it does make sense that in order to delete an artifact, one needs write permission of some kind. It is puzzling that this behaviour (requirement of permissions) is dependent on versions.

https://github.com/GeekyEggo/delete-artifact?tab=readme-ov-file#-usage

@radeksimko radeksimko added the ci Continuous integration/delivery related label Jan 15, 2024
@radeksimko radeksimko requested a review from a team January 15, 2024 15:45
@radeksimko radeksimko requested a review from a team as a code owner January 15, 2024 15:45
@radeksimko radeksimko requested review from emilymianeil and jeanneryan and removed request for a team January 15, 2024 15:45
@radeksimko radeksimko merged commit 623f35c into main Jan 15, 2024
21 checks passed
@radeksimko radeksimko deleted the gh-add-permission branch January 15, 2024 15:48
Copy link

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
ci Continuous integration/delivery related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants