Project

General

Profile

Statistics
| Branch: | Tag: | Revision:
Name Size
  agent
  server
agent.pp 256 Bytes
config.pp 2.02 KB
init.pp 32.5 KB
params.pp 10.6 KB
server.pp 1.48 KB

Latest revisions

# Date Author Comment
3b398aa8 02/10/2016 04:09 PM Michael Moll

support newer Ubuntu versions

f4ea1e0a 01/21/2016 11:43 AM Julien Pivotto

Fix default systemd and cron commands with AIO package

This commit simplifies the way we manage the puppet commands,
especially the puppet cert command.

This commit removes Puppet 2.7 support as well -- it was already not
supported by the tests anymore....

7ce6d9ca 01/12/2016 10:28 PM Joseph Yaworski

Allow arbitrary git repo user, mode, and group

3f68188c 11/26/2015 09:28 AM Dominic Cleal

Contain service implementations inside puppet::agent::service

Preserves ordering of the agent service(s) in relation to
puppet::agent::config etc.

Fixes GH-336

77816e81 11/25/2015 04:44 AM Dominic Cleal

Remove management of systemd timer unit on non-systemd OSes

Check specific versions of Debian and EL OSes to stop managing the
systemd timer, as a service resource with the systemd provider will
fail on older OS releases.

Fixes GH-334

2c279147 11/24/2015 05:22 AM Julien Pivotto

Improve systemd.timer integration

  • Change service name to systemd-run
  • Add SuccessExitStatus=2 to the service unit
  • Use Array().join instead of a more complex method
  • Add the ability to change the systemd service name
  • Add the ability to specify different commands for systemd and cron...
6e3be223 11/24/2015 05:22 AM Greg Sutcliffe

Add systemd timers as an alternative to cron for puppet agent

761dc5f0 11/23/2015 05:46 AM Dominic Cleal

refs #8389 - lower case FQDN in foreman_url parameter

Ensures that the HTTP requests from ENC/report processors work
correctly and don't receive a 404.

06ee2d57 10/08/2015 05:35 AM Michael Moll

manage Puppet 4 on FreeBSD

Closes GH-313

7e050505 09/30/2015 09:51 AM Pall Valmundsson

Don't generate CA cert if not a CA server

Before this change a CA certificate would always be generated for a
master node, regardless of whether it was a CA or not. This changes that
behaviour so that a CA certificate is only generated when the node is
configured to be a CA server.

View revisions

Also available in: Atom