Reapply YAML in develop branch
Update foreman, foreman_proxy, and puppet module commits
Change YAML path to /etc/foreman-proxy/answers.yaml for consistency
Parameterise foreman_installer class for answers.yaml location
Throw error when YAML type is unknown
bump concat/dhcp/puppet/foreman/tftp
Include 2.6 fix to foreman
Rename loadyaml to loadanyyaml to prevent stdlib conflict
Bump dhcp/dns/foreman/foreman_proxy/passenger/puppet
Update README.md

- make sure users checkout the develop branch
- update the git repo param name
Bump foreman/foreman_proxy/puppet for 1.1RC repo support
Version bump
Add answers generator v0.1
Use git submodule foreach
Fix Puppet 2.6 compatibility, parse error with hash in function call
Ensure the terminal global is always set
Add create_resources from puppetlabs to make this work on 2.6
Use Puppet's own create_resources function if available
Updated submodules to latest and added option to run puppet to the generator
Merge remote-tracking branch 'origin/develop'

* origin/develop:
  Updated submodules to latest and added option to run puppet to the generator
  Use Puppet's own create_resources function if available
  Add create_resources from puppetlabs to make this work on 2.6
  Ensure the terminal global is always set
  Fix Puppet 2.6 compatibility, parse error with hash in function call
  Use git submodule foreach
  Add answers generator v0.1
  Version bump
  Bump foreman/foreman_proxy/puppet for 1.1RC repo support
  Update README.md
  Bump dhcp/dns/foreman/foreman_proxy/passenger/puppet
  Rename loadyaml to loadanyyaml to prevent stdlib conflict
  bump concat/dhcp/puppet/foreman/tftp
  Throw error when YAML type is unknown
  Change YAML path to /etc/foreman-proxy/answers.yaml for consistency Parameterise foreman_installer class for answers.yaml location
  Update foreman, foreman_proxy, and puppet module commits
  Reapply YAML in develop branch
Removed the develop branch from clone instructions