forked from bruce/puppet-vcsrepo
-
Notifications
You must be signed in to change notification settings - Fork 285
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
strange safe_directory behavior #585
Labels
Comments
Despite poor ruby knowledge I guess that the case "directory is already in safe_directory list" is missing at b/c |
david22swan
added a commit
to david22swan/puppetlabs-vcsrepo
that referenced
this issue
May 19, 2023
Due to mistake in the logic unsafe directory was previously removed on every other run. The logic previously checked whether the unsafe directory needed to be added, removing it if this was false without taking into account when it was already set but we wanted it to be left in place.
david22swan
added a commit
to david22swan/puppetlabs-vcsrepo
that referenced
this issue
May 19, 2023
Due to mistake in the logic unsafe directory was previously removed on every other run. The logic previously checked whether the unsafe directory needed to be added, removing it if this was false without taking into account when it was already set but we wanted it to be left in place.
david22swan
added a commit
to david22swan/puppetlabs-vcsrepo
that referenced
this issue
May 19, 2023
…stem level Safe directory is now set at a system wide level rather than at a global user level in order to ensure it is as effective as possible.
david22swan
added a commit
to david22swan/puppetlabs-vcsrepo
that referenced
this issue
May 19, 2023
…stem level Safe directory is now set at a system wide level rather than at a global user level in order to ensure it is as effective as possible.
Fix for this is up: #605 |
LukasAud
added a commit
that referenced
this issue
May 19, 2023
…_directoryfix (GH-585/CONT-998) Fix for safe_directory logic
Release with fix for this has gone out: v6.0.1 |
LadyNamedLaura
pushed a commit
to UGent-DICT/puppetlabs-vcsrepo
that referenced
this issue
Oct 31, 2023
Due to mistake in the logic unsafe directory was previously removed on every other run. The logic previously checked whether the unsafe directory needed to be added, removing it if this was false without taking into account when it was already set but we wanted it to be left in place.
LadyNamedLaura
pushed a commit
to UGent-DICT/puppetlabs-vcsrepo
that referenced
this issue
Oct 31, 2023
…stem level Safe directory is now set at a system wide level rather than at a global user level in order to ensure it is as effective as possible.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the Bug
I have set
safe_directory => True
.If I run puppet it is set as expected but on the next run it is unset again. On another server the directory is always append to .gitconfig so /root/.gitconfig looks like that
Expected Behavior
Directory of repository is added to "safe" paragraph at .gitconfig if it is not present and not removed.
Steps to Reproduce
This is how I use vcsrepo
Environment
The text was updated successfully, but these errors were encountered: