github-migration/guard-puppet
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Re-apply Puppet configs while you work, thanks to Guard!
23 Commits 1 Branch 2 Tags 49 KiB
Ruby 100%
512e7f95d1
Go to file
Cezary Baginski 512e7f95d1 avoid namespace conflict with Guard::Bundler
2015-06-06 23:17:41 +02:00
lib/guard avoid namespace conflict with Guard::Bundler 2015-06-06 23:17:41 +02:00
spec avoid namespace conflict with Guard::Bundler 2015-06-06 23:17:41 +02:00
.gitignore initial commit 2011-06-30 22:48:18 -04:00
.rspec default rspec options config 2015-06-06 23:00:03 +02:00
Gemfile setup guard-rspec 2015-06-06 22:54:12 +02:00
guard-puppet.gemspec switch to use guard-compat 2015-06-06 22:50:15 +02:00
Guardfile regenerate Guard::RSpec block in Guardfile 2015-06-06 23:17:15 +02:00
Rakefile run on start 2011-07-06 19:29:43 -04:00
README.md run on start 2011-07-06 19:29:43 -04:00

README.md

Reapply your Puppet configs automatically using Guard! Awesome!

guard 'puppet' do
  watch(%r{^(manifests|modules)})
end

It's assumed your configs are all in the current folder, which is the equivalent of --confdir=$PWD at the command line. Otherwise, there's not much use of using Guard with Puppet. :)

Four options so far:

  • :run_on_start: Apply Puppet configs when starting Guard (default: false)
  • :verbose: Show more output from Puppet (default: true)
  • :debug: Show even more output from Puppet (default: false)
  • :manifest: The main manifest file to run (default: manifests/site.pp)

Bugs and fixes? You know the drill.