Bug #735
Configuration References Inconsistency
| Status: | Closed | Start date: | ||
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Luke Kanies |
% Done: | 0% |
|
| Category: | - | |||
| Target version: | 0.24.0 | |||
| Affected Puppet version: | 0.25.4 | Branch: | ||
| Keywords: | ||||
| Votes: | 0 |
Description
In the ConfigurationReference it should be made clear that puppet.conf is the only file looked for in /etc/puppet, and references to $executable —genconfig > /etc/puppet/$executable.conf removed as they suggest otherwise. Also it is my understanding that INI sections are irrelevant to the extent of configuring individual executables and only used internally. As such it might make sense to remove them from the documentation and simplify the configuration definition process.
History
Updated by Digant Kasundra almost 5 years ago
I’m not sure how to update the autogenerated docs.
Also, what if people want to run puppet with different options than puppetd? If there are not INIT sections, wouldn’t this be a problem? Or more likely, people might run the puppetmasterd with different settings/options than puppetd. I’m not sure if this is the case with my deployments b/c I haven’t sat down and compared but I fear that this might be the case.
Updated by Luke Kanies almost 5 years ago
- Status changed from 1 to 2
The references each have headers in lib/puppet/reference/
Previously, the section names had no meanings, but when I consolidated the configuration files, I changed it so the section names do have meaning: Everyone parses ‘main’ and the section that matches the executable name.
Updated by Luke Kanies almost 5 years ago
- Status changed from 2 to Closed
- 7 set to fixed
Fixed in r2743, I think.
gen_config now creates a single section heading, matching the process name, rather than keeping the internal section names.
This reference will get automatically regenerated when I release 0.23.2.