Sounds fair enough.
So I've had a look at what we've got, and it's not an onerous amount of
code that needs translating and implementing as facts. The problem really
is the development environment which is very straight forward with our
binary as it can be entirely built, tested and installed i
Thank you all for your responses.
>From John's response, I see that I'm going to struggle here. Ultimately, I
am just trying to get some details about the system, and will look into
installing our system info script as part of the OS build. Truthfully
though, it's not doing so much that I could
Custom Providers look interesting, although I can't immediately find a good
example to work from (it just me, or is the puppetlabs doco weirdly
confusing?). I guess it just matters when the provider is evaluated - if
it's evaluated on first use, then I can make this work.
Thanks for the suggest
Hi,
I have a module called system_info which sets a custom fact based on some
company-specific details about the host. For example, it might set
something like this:
system_info_rack_number=27
(This fact is set by a lib/facter/system_info.rb bit of Ruby code, although
the same is true if I se
Pulling our whole puppet master from SVN is indeed an option. It seems like
a bit of work, but it's possible.
The issue of trying to unit test a puppet install seems to be somewhat
addressed by the Puppet solution, although I could see that we could either
poke a node.pp manifest onto the real
Thanks for the suggestion. I did wonder about copying all the modules and
configs off the Puppet Master onto the test box. My concern is really just
about keeping that lot up to date, and most importantly to make sure that
it behaves the same as it would do if it came from the Master. It could b
Does anyone know if it's possible to run Puppet as if it's running with a
Master, but using a locally created node.pp manifest?
I'm looking into doing some unit tests on applications that are installed
by Puppet. To do this, I'm trying to use a test VM server which I'll deploy
applications onto
I have a similar requirement as Jon Forrest who opened this topic. I notice
some time has passed since then, so I thought I'd just tap you guys up to
see if anyone had any further solutions.
I'd like to use Jenkins to Unit Test come configs we use whenever someone
commits them. The idea is that
