* Updating the Python packages to make Molecule work
* Triggering jobs with updating Telegraf version
* Changing Ansible version
* Changing github ci version
* Changing Python version version
* Removal of Debian9
Telegraf throws following deprecation warning:
```
W! DeprecationWarning: Plugin "inputs.io" deprecated since version 0.10.0 and will be removed in 2.0.0: use 'inputs.diskio' instead
```
As far as I can tell this is simple rename and the output of these plugins should not change. I've also tried comparing the output locally and it seems to be the same.
```
# The following command outputs two sets of identical data:
telegraf --test --config telegraf.conf --input-filter io:diskio
```
* Do not install init script on SUSE systems (#152)
The last SUSE releases that didn't support systemd were SLE 11 and
openSUSE 11.x. The telegraf packages on the Open Build Service all
contain systemd service files. openSUSE 11.x is long since dead and
buried and SLE 11 has been out of general support since mid-2019.
There are no other users of the script and it can be removed. The
dependencies required in the molecule configuration can also be removed.
* Fix Python package dependencies on SUSE releases (#153)
The naming of the packages for the Python libxml and xml modules
on SUSE releases is a bit of a mess across releases.
SLE12 ships with Python 3.4 which is not new enough for Ansible to
use so Python 2 must be used. Those packages are named python-xml
and python-libxml2.
SLE15 ships with Python 3.6 but the package containing the libxml2
module is named python3-libxml2-python. The xml module is part of
python3-base and will be present if the interpreter is present.
On later releases, the package containing the libxml2 module has been
renamed python3-libxml2 but it still offers an alias for the old name.
* Add default repository handling for SUSE releases (#154)
The repositories for SUSE releases are in well-known locations
and requiring the user to specify them is unnecessary. If the user
wishes to override the default repo using the telegraf_zypper_baseurl
that will still be honored.
- Added some commenting inside of defaults to clarify which variables
adjust which files
- Split up the role taking items out of main.yml in tasks. This is to
improve clarity of what each bit of Ansible code is doing.
- Tags were defined for each and every task within the Debian.yml moved
ths up to main.yml so they don't need repeating every task adding
clutter.
- Added some extra default plugins, as of current release version these
are now within the default configuration but were missing from this
role.
- Added some commenting inside the templates and the top of some tasks
to clarify where the templated file was coming from.
Systems like Amazon Linux are from the RedHat OS family but have a
specific release versions notation. Influxdata does not always provide a
yum repository with these versions, so it should be something to override
in order to install telegraf from a different release version path.
For instance, Influxdata currently provides telegraf for both RHEL
versions 6 and 2016.09 with packages being the same (same checksums).
This is because of Amazon Linux 2016.09 being a RHEL version 6.
However, now Amazon Linux 2017.09 is out, still being a RHEL 6 but
Influxdata does not provide a 2017.09 release version path so we cannon
install telegraf on it. Overriding the release version to 6 or 2016.09
will allow to install.
From : https://github.com/rossmcdonald/telegraf
Add `telegraf_agent_aws_tags` boolean to enable AWS tag in telegraf agent
tags section.
Also add `telegraf_agent_aws_tags_prefix` to allow usage of a prefix on AWS tags name.
