Skip to content
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

Open
toepi opened this issue Nov 4, 2015 · 4 comments
Open

'merge' fact and facts #56

toepi opened this issue Nov 4, 2015 · 4 comments

Comments

@toepi
Copy link
Contributor

toepi commented Nov 4, 2015

class puppet::facts and define puppet::fact has a similar template, to supported structured_facts you must change both. Why not use puppet::fact inside puppet::facts - the only drawback no longer a local.yaml? This also mean you can manage ${facterbasepath}/facts.d every time and not only if some custom_facts are provided.

@rendhalver
Copy link
Member

Good point.
I should move the directory management out of puppet::facts.

@rendhalver
Copy link
Member

I think idea behind puppet::facts existed before the puppet::fact define was created.
I could change it to use the define internally but I am not a big fan of create_resources.

@rendhalver
Copy link
Member

The fix I made for this in #65 should fix the problem.

@toepi
Copy link
Contributor Author

toepi commented Apr 17, 2016

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 ls only and not an ls and and cat local.yaml.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants