Ansible role for running puppet
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ian Wienand e9fc2df1bc Clear out old facts 3 weeks ago
defaults Allow overiding the remote hieradata link dest 10 months ago
handlers Add all of the files needed to make this a role 4 years ago
library Clear out old facts 3 weeks ago
meta Fix ansible-lint 1 month ago
tasks Fix ansible-lint 1 month ago
templates Fix hieradata path for puppet 4 4 months ago
tests Add all of the files needed to make this a role 4 years ago
vars Define defaults as defaults, not variables 3 years ago
.gitignore Add tox -eansible-lint support 3 years ago
.gitreview OpenDev Migration Patch 2 months ago
.zuul.yaml Switch to linters job 1 month ago
LICENSE Add all of the files needed to make this a role 4 years ago
README.md Update README with info about puppet apply 2 years ago
bindep.txt Add bindep.txt file 1 year ago
requirements.txt Add tox -eansible-lint support 3 years ago
run_tests.sh Add all of the files needed to make this a role 4 years ago
test-requirements.txt Add tox -eansible-lint support 3 years ago
tox.ini Fix ansible-lint 1 month ago

README.md

puppet

Run puppet consistently from ansible.

Requirements

puppet needs to be installed on the target node, and if puppet agent is being used, the cert exchange needs to have been performed.

Role Variables

Either puppetmaster or manifest should be supplied. If you are using puppet agent, you want to supply puppetmaster. If you are using puppet apply, you want to supply manifest.

Dependencies

None

Example Playbook using a puppetmaster

The only required argument is puppetmaster:

- hosts: servers
  roles:
     - { role: puppet, puppetmaster: puppetmaster.openstack.org }

Example Playbook without a puppetmaster

The only required argument is manifest:

- hosts: servers
  roles:
     - { role: puppet, manifest: /opt/system-config/production/manifests/site.pp }

License

Apache

Author Information

ansible-puppet is maintained by the OpenStack Infra team. The best way to contact them is on #openstack-infra on freenode.