Debbugging the nightmare that is Puppet ERB templates

README.txt

If you have ever done *anything* with Puppet templates, you know how ugly it is to debug. 
This Gist will help  improve debugging and reduce guesswork.  The main problem I always run into when debugging
ERB templates is grokking variable access.   

I have included two code snippets:
- erb-dump.pp       # Puppet manifest  
- erb-dump.yaml.erb # ERB template to dump the entire namespace available to the template to /tmp/erb-dump.yaml
- erb-dump.rb       # loads the yaml dump into a usable ruby hash

erb-dump-parse.rb

#!/usr/bin/env ruby

require 'yaml'

# Loads the dump into a usable hash
file = YAML.load('/tmp/erb-dump.yaml')

erb-dump.pp

# Creates /tmp/erb-dump.yaml from the erb-dump.template
file {'/tmp/erb-dump.yaml':
  content       = template ('erb-dump.yaml.erb'),
  ensure        = 'present'
  mode          = '0644',
  owner         = 'puppet',
  group         = 'puppet,
 }
  

erb-dump.yaml.erb

<%# If you have ever done *anything* with Puppet templates, you know how ugly it is to debug
    This Gist will help fix that to somewhat easier. -%>

<%= scope.to_hash.reject { |k,v| !( k.is_a?(String) && v.is_a?(String) ) }.to_yaml %>