2023-11-13 18:20:27 +01:00
|
|
|
# @summary Installs Vector to transform Prometheus data
|
|
|
|
|
#
|
2024-02-06 21:40:19 +01:00
|
|
|
class kandra::vector {
|
2023-11-13 18:20:27 +01:00
|
|
|
$version = $zulip::common::versions['vector']['version']
|
|
|
|
|
$dir = "/srv/zulip-vector-${version}"
|
|
|
|
|
$bin = "${dir}/bin/vector"
|
|
|
|
|
|
2024-03-25 20:16:16 +01:00
|
|
|
$arch = $facts['os']['architecture'] ? {
|
2023-11-13 18:20:27 +01:00
|
|
|
'amd64' => 'x86_64',
|
|
|
|
|
'aarch64' => 'aarch64',
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
zulip::external_dep { 'vector':
|
|
|
|
|
version => $version,
|
|
|
|
|
url => "https://packages.timber.io/vector/${version}/vector-${version}-${arch}-unknown-linux-gnu.tar.gz",
|
|
|
|
|
tarball_prefix => "vector-${arch}-unknown-linux-gnu",
|
puppet: Stop relying on "tidy" ordering, which ignores metaparams.
The `tidy` parameter is buggy, and ignores all ordering
metaparameters. This is fixed in Puppet 7[^1], but it's helpful to
resolve it now. Specifically, this fixes bugs with tidy running too
early, and deleting the old version of a package before its new
version is installed or symlinked, leaving a race condition if
anything tries to run the binary in this window.
This is mostly not a problem for Supervisor-managed processes, since
the binary is already running, and can continue to run if it is tidied
out from under the running process. For stand-alone tools like wal-g,
which are run frequently by PostgreSQL, this may cause issues if
PostgreSQL tries to call them during a puppet run.
Remove all complicated uses of tidy, and replace them with an `exec`
which does the equivalent. We also generate `file` resources for
binaries, making them easier (and clearer) to specify as dependencies.
[^1]: https://puppet.atlassian.net/browse/PUP-10688
2024-04-15 20:11:08 +02:00
|
|
|
bin => [$bin],
|
|
|
|
|
cleanup_after => [Service[supervisor]],
|
2023-11-13 18:20:27 +01:00
|
|
|
}
|
|
|
|
|
}
|