cockpit: support setting owner/group in fsreplace1 #21128
Draft
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
jelly
added
the
no-test
jelly
force-pushed
the
fsreplace1-chown
branch
from
24fc8e2
to
2602089
Compare
Cockpit-files wants to support uploading or creating a file owned by the current directory which might be different from the logged in user. For example as superuser uploading a database into `/var/lib/postgresql` which would be owned by `postgres` and the database file should receive the same permissions.
jelly
force-pushed
the
fsreplace1-chown
branch
from
2602089
to
489d3f5
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.
Cockpit-files wants to support uploading or creating a file owned by the current directory which might be different from the logged in user.
For example as superuser uploading a database into
/var/lib/postgresqlwhich would be owned bypostgresand the database file should receive the same permissions.This still needs tests, sadly we can't chown as a normal user so we can't easily write unittests unless we start creating a new user namespace and mapping that user in there (or depending on
bwrap).So I will work on creating integration tests with the playground page to have this properly tested in Cockpit.