Correct puppet-strings documentation

[ekohl]

In various places @attr was used instead of @param. It also didn't use the @summary tag which led to odd summaries. Then some indenting was incorrect.

It also uses a newer version of puppet-strings which generates a list of parameters with links.

[puppet-community-rangefinder]

systemd::dropin_file is a type

Breaking changes to this file WILL impact these 23 modules (exact match):

• MiamiOH-moab
• camptocamp-es_lite
• marionetoj-logrotate
• kenyon-bind
• simp-useradd
• hfm-proxysql
• treydock-slurm
• puppet-mlocate
• puppet-nftables
• osc-openondemand
• mark0n-epics
• puppet-ferm
• puppet-proxysql
• puppet-snmp
• sensu-sensu
• saz-memcached
• theforeman-dhcp
• simp-nfs
• simp-rsyslog
• katello-qpid
• puppet-check_mk
• theforeman-puppet
• theforeman-foreman

Breaking changes to this file MAY impact these 4 modules (near match):

• aursu-grayloginstall
• simp-tpm2
• leoarnold-cups
• simp-selinux

systemd::journald is a class

that may have no external impact to Forge modules.

systemd::logind is a class

that may have no external impact to Forge modules.

systemd::network is a type

that may have no external impact to Forge modules.

systemd::resolved is a class

Breaking changes to this file MAY impact these 1 modules (near match):

• eyp-netplan

systemd::service_limits is a type

Breaking changes to this file WILL impact these 4 modules (exact match):

• puppet-rabbitmq
• saz-memcached
• treydock-slurm
• katello-qpid

Breaking changes to this file MAY impact these 2 modules (near match):

• openstack-tripleo
• theforeman-foreman_proxy

systemd::timesyncd is a class

Breaking changes to this file MAY impact these 1 modules (near match):

• eyp-ntp

systemd::tmpfile is a type

Breaking changes to this file WILL impact these 1 modules (exact match):

• initforthe-rails

systemd::udev::rule is a type

that may have no external impact to Forge modules.

systemd::udevd is a class

that may have no external impact to Forge modules.

This module is declared in 8 of 576 indexed public Puppetfiles.

---

These results were generated with Rangefinder, a tool that helps predict the downstream impact of breaking changes to elements used in Puppet modules. You can run this on the command line to get a full report.

Exact matches are those that we can positively identify via namespace and the declaring modules' metadata. Non-namespaced items, such as Puppet 3.x functions, will always be reported as near matches only.