Add option for explicit chmod with atomic file write. #111
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
benhoyt
requested changes
Mar 16, 2022
|
This should be ready for another look. |
|
Is this waiting on anything in particular? |
|
A Gustavo review. Though this is really a minor bug fix, not an API change, so I'd say we can probably push it through. |
|
Merged, thanks @rwcarlsen! |
jujubot
added a commit
to juju/juju
that referenced
this pull request
Jun 21, 2022
#14180 Non-documentation changes: * Stop all services when SIGINT/TERM/QUIT received ([#114](canonical/pebble#114)) * Make files write API (push) call chmod explicitly ([#111](canonical/pebble#111))
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
And use this explicit chmod flag for file writes coming from the files api.
Fixes #80