Fix permissions on sensitive config files #44
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
landervdb
force-pushed
the
feature/sensitive-config
branch
6 times, most recently
from
dd032fa to
d00d4b9
Compare
Signed-off-by: Lander Van den Bulcke <[email protected]>
landervdb
force-pushed
the
feature/sensitive-config
branch
from
d00d4b9 to
ed4d2c6
Compare
syberalexis
reviewed
Jul 19, 2023
| @@ -39,5 +41,8 @@ | |||
| file { $title: | |||
| ensure => $_ensure, | |||
| content => $configs.to_yaml(), | |||
| owner => $user, | |||
| group => $group, | |||
| mode => '0600', | |||
There was a problem hiding this comment.
Can you add mode in parameters too, please.
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.
These files can contain sensitive info and should not be world readable.