Issue #2690 has been updated by James Turnbull.

Category set to server
Status changed from Unreviewed to Needs design decision
Assigned to set to Luke Kanies

I guess this is in the same broad scope as #2442.  Luke?
----------------------------------------
Bug #2690: puppet insists on /etc/puppet/manifests being a folder
http://projects.reductivelabs.com/issues/2690

Author: Klavs Klavsen
Status: Needs design decision
Priority: Normal
Assigned to: Luke Kanies
Category: server
Target version: 
Affected version: 0.24.8
Keywords: 
Branch: 


I have puppet files in svn - but because there's also files in the top-dir 
/etc/puppet - I have to have the entire dir in svn.

However I also have differing versions of /etc/puppet/puppet.conf - so that 
file can't and IMHo shouldn't be in svn.

I moved /etc/puppet to /usr/src/puppet-svn and symlinked the relevant files and 
folders to /etc/puppet to fix the problem of svn status complaining about the 
unknown /etc/puppet/puppet.conf file.

Whenever I restart puppetmaster it removes the symlink /etc/puppet/manifests 
(pointing to /usr/src/puppet-svn/manifests) - even if I have set the symlink 
immutable :(

As I see no reason for puppetmaster to need to control if manifests folder is a 
folder, or a symlink to one - I consider this a bug - although a small one :)


-- 
You have received this notification because you have either subscribed to it, 
or are involved in it.
To change your notification preferences, please click here: 
http://reductivelabs.com/redmine/my/account

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Bugs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/puppet-bugs?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to