Ensure all file permissions are set to specified unprivileged user #1175
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
This change avoids a potentially heavy chown operation at the start of the container process - in fact, it may even allow us to drop perm changes completely - by ensuring any created files are _always_ set to the correct permissions.
josegonzalez
force-pushed
the
file-perms
branch
from
450b93e
to
e9232af
Compare
josegonzalez
added a commit
that referenced
this pull request
Mar 28, 2024
- #1093 @dependabot: chore(deps): bump actions/download-artifact from 3 to 4 - #1173 @josegonzalez: Use find to identify only files not already owned by user - #1174 @josegonzalez: Add linting to CI - #1175 @josegonzalez: Ensure all file permissions are set to specified unprivileged user - #467 @mlandauer: Only copy from app import path to app path when building
Merged
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.
This change avoids a potentially heavy chown operation at the start of the container process - in fact, it may even allow us to drop perm changes completely - by ensuring any created files are always set to the correct permissions.