-
Notifications
You must be signed in to change notification settings - Fork 44
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
'merge' fact and facts #56
Comments
Good point. |
I think idea behind puppet::facts existed before the puppet::fact define was created. |
The fix I made for this in #65 should fix the problem. |
Sorry for the delay. Main "issue" two templates are still remaining? If you don't want use create_resources, why not use concat and put facts only into local.yaml? But think create_resources for custom_facts would be a good solution to minimize duplication; Benefit file is called like the fact it is presenting every time. So you can check which facts are on the node you need a |
class
puppet::facts
and definepuppet::fact
has a similar template, to supported structured_facts you must change both. Why not usepuppet::fact
insidepuppet::facts
- the only drawback no longer alocal.yaml
? This also mean you can manage${facterbasepath}/facts.d
every time and not only if some custom_facts are provided.The text was updated successfully, but these errors were encountered: