fix issue with ownership when perms option is set #1473
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
findkim
approved these changes
May 27, 2021
When the template config option `perms` is set, the ownership isn't preserved. The problem was the file ownership is preserved in the block that is only run if perms is unset. Ownership should always be preserved.
eikenb
force-pushed
the
issue-1379-preserve-ownership
branch
from
bf93668 to
3943241
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When the template config option
permsis set, the ownership isn't preserved. The problem was the file ownership is preserved in the block that is only run if perms is unset. Ownership should always be preserved.Note there is no tests as ownership changes are hard/impossible to do cross system. Groups, which you could set, vary to much between systems to make this feasible.
Fixes #1379