fix: Use become on potential cross-user actions #236
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This took me couple hours to figure out what's going on. The bug here is that when you are doing cross-user actions, you need to privilages to do so. Let's say that I'm running the playbook as user
bob
, but the runner user isjohn
.bob
cannot create and directory on behalf ofjohn
without proper rights. You need to become super user for that kind of action.This needs to be aplied everywhere where you want to change owner (run on a behalf of someone else).
Type of change
How Has This Been Tested?
Tested it locally on our fork.