This PR resolves an issue encountered on Debian 11/Ubuntu 22.04 hosts where the apt-key command returns a warning due to deprecation by the OS maintainers, and fails the task as a result.
The most common workaround seems to be placing the key directly into the trusted.gpg.d directory and referencing the key path as a signed-by parameter in the repo file. I made this change on my fork and successfully ran the playbook against my Debian 11 hosts.
Description of PR
Updating the Debian apt key install process to use the recommended method of placing the key in trusted.gpg.d instead of using the deprecated apt-key command.
This PR resolves an issue encountered on Debian 11/Ubuntu 22.04 hosts where the apt-key command returns a warning due to deprecation by the OS maintainers, and fails the task as a result.
The most common workaround seems to be placing the key directly into the
trusted.gpg.d
directory and referencing the key path as asigned-by
parameter in the repo file. I made this change on my fork and successfully ran the playbook against my Debian 11 hosts.Description of PR Updating the Debian apt key install process to use the recommended method of placing the key in
trusted.gpg.d
instead of using the deprecatedapt-key
command.Type of change Bugfix Pull Request
Fixes an issue https://github.com/dj-wasabi/ansible-telegraf/issues/169