-
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
Feature "expanded custom facts" #113
base: production
Are you sure you want to change the base?
Feature "expanded custom facts" #113
Conversation
Gemfile
Outdated
gem "rspec-core", '3.1.7', :require => false | ||
gem "rspec-puppet", '2.3.2', :require => false | ||
gem "rspec-core", '3.5.1', :require => false | ||
gem "rspec-puppet", '2.4.0', :require => false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are you upgrading these?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's only gems update.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realise that. Why are you wanting to upgrade them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That does look more useful.
If the rest of the tests pass as is then it's good for me.
All of your examples are with either an array or a hash. |
Sorry... Now I understand you.
Check in code:
Run code:
validate is good.
Check in code:
Run code:
validate is good. |
So how do you generate those fact files with your code? |
Example only for Puppet4:
Puppet run:
facter check:
puppet code:
Puppet run:
I think is not good file name:
I update branch. |
@MemberIT Please remove your edits to Gemfile and Gemfile.lock and rebase. |
610a849
to
cb0cb9a
Compare
ff2b3ae
to
bf7d3ba
Compare
bf7d3ba
to
773b037
Compare
@rendhalver done |
Thanks @MemberIT. I will have a look at this locally soon to see how it works. |
be43cc2
to
e864256
Compare
e864256
to
5d4054e
Compare
Great improvement for facts. Why still puppet3 - have learn is no longer supported by puppetlabs - more and more are puppet4 only.. |
That validation is still useful. |
@rendhalver That validation not needed. Code in templates of custom facters
templates/local_facts.yaml.erb:
'yaml' is part of ruby stdlib in all versions: |
@toepi Current version of code correctly work on Puppet 3 and Puppet 4. I would not change the code of manifests in pullrequest, if module worked only Puppet 4. |
@MemberIT: I like It and use it since yesterday in my lab. And have saw how can I solve another of my template issue. |
New feature "expanded custom facts"
Puppet code:
facters: