Clark Boylan 0269710c86 Don't manage puppet.conf during puppet-install
The ansible-role-puppet role manages puppet.conf for us. These two roles
are currently fighting each other over the presence of the server line
in puppet.conf. Avoid this by removing the removal of this line and the
templatedir line from the new puppet-install role since
ansible-role-puppet was there first. Basically just trust
ansible-role-puppet to write a working puppet.conf for us.

Change-Id: Ifb1dff31a61071bd867d3a7cc3cbcc496177e3ce
2019-04-08 10:09:35 -07:00

44 lines
1.1 KiB
YAML

- fail:
msg: "Unsupported puppet version '{{ puppet_install_version }}' on this platform"
when: puppet_install_version not in [3, 4]
- name: Install puppet 3 packages
when: puppet_install_version == 3
become: true
block:
# Note https doesn't work here due to certificate issues and
# python versions and SNI etc; not worth the effort of workarounds
# at this point.
- name: Install puppetlabs repo
apt:
deb: http://apt.puppetlabs.com/puppetlabs-release-trusty.deb
- name: Install puppet packages
package:
state: present
name:
- puppet
- ruby
- name: Install puppet 4 packages
when: puppet_install_version == 4
become: true
block:
- name: Install puppetlabs repo
apt:
deb: http://apt.puppetlabs.com/puppetlabs-release-pc1-trusty.deb
- name: Install puppet packages
apt:
name:
- puppet-agent
- ruby
update_cache: yes
- name: Stop and disable puppet service
service:
name: puppet
state: stopped
enabled: no
become: yes