The filename and unit parameter wered documented incorrectly
as to which was the name variable.

Correct docs for name var of systemd::dropin_file

Previously lots of unit names like

```
this is a service with spaces in.service
```
were permitted for instance.

From systemd.unit

> Valid unit names consist of a "name prefix" and a dot and a suffix specifying the unit type. The "unit prefix" must consist of one or more valid characters (ASCII letters, digits, ":", "-", "_", ".", and "\"). The total length of the unit name including the suffix must not exceed 256 characters. The type suffix must be one of ".service", ".socket", ".device", ".mount", ".automount", ".swap", ".target", ".path", ".timer", ".slice", or ".scope".

in addition we allow `@` to cover the case of template or template
instance.

Example
```puppet
systemd::manage_unit{ 'myrunner.service':
  $unit           => {
    'Description' => 'My great service',
  },
  $service        => {
    'Type'        => 'oneshot',
    'ExecStart'   => '/usr/bin/doit.sh',
  },
  $install        => {
    WantedBy      => 'multi-user.target',
  },
}
```

will generate and manage a new systemd unit from a template.

The type `systemd::manage_dropin` is similar
for drop in files.

New systemd::manage_unit, systemd::manage_dropin types

Fixes a problem (I) introduced in #276.

Signed-off-by: Simon Deziel <simon@sdeziel.info>

Signed-off-by: Simon Deziel <simon@sdeziel.info>

resolved: `onlyif` snippet requires shell support

…20.04

feat: manage timesyncd package on Debian >= 11 and Ubuntu >= 20.04

modulesync 5.3.0

modulesync 5.4.0

Support specification of the  absolute limit on swap usage of the executed processes in this unit.

For example

```puppet
systemd::service_limits{'condor.service':
  limits => {
    'MemorySwapMax' => '0',
  }
}
```

* https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#MemorySwapMax=bytes

Debian 8 was end of life 2020-06-30

https://wiki.debian.org/DebianReleases

more over acceptance jobs now fail with:

```json
{"stream":"\u001b[91mW: GPG error: http://deb.debian.org/ jessie-updates InRelease: The following signatures were invalid: KEYEXPIRED 1668891673\nW: GPG error: http://deb.debian.org/ jessie Release: The following signatures were invalid: KEYEXPIRED 1668891673\n\u001b[0m"}

```

Allow MemorySwapMax to be specified as service limit

Remove debian 8 support

Since 97dd16f this parameter is a bad
idea. It doesn't do a daemon reload and it may restart at the wrong
time. In fact, I'd argue it's always been a bad idea.

The recommended alternative to this is to manage the service explicitly
and let Puppet handle it. There is an automatic notify that takes care
of it.

Fixes #190

This builds on 81f3eb5 which allowed
services to be notified automatically. This changes it to default
behavior.

Fixes #74

drop support for fedora 30 & 31 (EOL)

drop support for ubuntu 16.04 (EOL)

drop debian 9 support (EOL)

Signed-off-by: Simon Deziel <simon@sdeziel.info>

Signed-off-by: Simon Deziel <simon@sdeziel.info>

Remove restart_service on service_limits define

Notify services by default on drop in files

Add support for Ubuntu 22.04

systemd::unit_file: remove hasrestart/hasstatus params

Instead of :linux.

This fact provides information about the udevadm utilty.

This fact provides access to udev db data.

add udevadm & udev facts

In 8a9e03a the parameter was removed,
but this makes it very hard for modules to be compatible with both < 4
and >= 4. Requiring >= 4 will be painful, so this adds the parameter
again but only accepts the parameter false.

A concrete example is the puppet-redis module which sets restart_service
to false to prevent a restart. This would be compatible with both the
old and new behavior, making upgrades smoother.

Fixes: 8a9e03a

release 4.0.0