Bug #1239
Should be able to make /etc/puppet a symlink
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | % Done: | 0% |
||
| Category: | executables | |||
| Target version: | 0.24.5 | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
Hi,
I made /etc/puppet a symlink into a directory in a version control repository. puppetmasterd destroyed the symlink at startup, and created a new directory structure without any configuration files in it. This alarms me.
Puppetmasterd should treat the symlink as an ordinary directory if it behaves like one, and I shouldn’t have to set —confdir (which is, incidentally, not in puppetmasterd’s —help).
Cheers, Peter
History
Updated by Luke Kanies almost 4 years ago
- Status changed from 1 to Closed
- 7 set to duplicate
This is a dupe of #650.