Deploy telegraf configuration as a "non config" file #7250
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Required for all PRs:
Description
This PR fixes #4966, by changing the way
telegraf.conf
is packaged and deployed:telegraf.conf
is now packaged astelegraf.conf.sample
. This will make package managers compare over the.sample
file instead of the.conf
one, making it more user friendly since/etc/telegraf.conf
is usually configured by the user/etc/telegraf/telegraf.conf
is present on the target system (typical case of a fresh install), the post installation step will copy/etc/telegraf/telegraf.conf.sample
to/etc/telegraf/telegraf.conf
to have an initial working configurationNotes:
build.py
file, based on PEP-8 recommendationslinux/amd64
rpm/deb
packages, I take it it should be similar for the rest since there is a lot of shared code but if I'm missing some scenario please let me knowCHANGELOG
myself, if so please let me knowFeel free to add any suggestion, I was not really familiar with
deb
rpm
packaging internals, nor withfpm
.