Use .conf as the file extension for answer files on PE 2016.2.0 and newer

[Sharpie]

The HOCON library used by the PE installer can get picky about the file extension and refuse to parse an answer file unless the filename ends in .conf.

[terrimonster]

I'm getting errors related to this. I tried to point pe_bootstrap to an alternate file, too, as documented.

ERROR: Your pe.conf at /vagrant/.pe_build/answers/master.txt contains invalid HOCON syntax: Unrecognized file extension '.txt' and no value provided for :syntax option

Trying to install: 2016.4.3

vagrant plugin list
oscar (0.5.3)

• Version Constraint: > 0
  vagrant-auto_network (1.0.2)
• Version Constraint: > 0
  vagrant-hostmanager (1.8.5)
• Version Constraint: > 0
  vagrant-hosts-provisioner (2.0)
• Version Constraint: > 0
  vagrant-proxyconf (1.5.2)
• Version Constraint: > 0
  vagrant-share (1.1.7)
• Version Constraint: > 0

roles.yaml:

roles:
pe-puppet-master:
private_networks:
- {ip: '0.0.0.0', auto_network: true}
providers:
- type: virtualbox
linked_clone: true
customize:
- [modifyvm, !ruby/sym id, '--memory', 2048]
provisioners:
- type: hosts
sync_hosts: true
hosts:
- ['@vagrant_private_networks', ['master.example.com','@vagrant_hostnames']]
- {type: pe_bootstrap, answer_file: scripts/pe.conf }

[Sharpie]

Wow. I thought 2016.4.3 was fine with this issue --- it usually showed up in nightly builds where the HOCON library had been upgraded to a version that was picky about file extensions.

I think the change here can actually be fairly small, so I'll look into getting it out in the next release.