Open FredrikWendt opened 5 years ago
The only workaround I know of, is to manually skip Bonsai registry (you can still download stuff, but the metadata available is ignored), and just sensuctl asset create
the thing instead, but forces you to name your assets differently depending on platform (which forces you to duplicate checks as well ...)
Example:
sensuctl asset create sensu-plugins-cpu-checks \
--url https://assets.bonsai.sensu.io/68546e739d96fd695655b77b35b5aabfbabeb056/sensu-plugins-cpu-checks_4.0.0_debian_linux_amd64.tar.gz \
--sha512 da5a183ad1a1f76962561eed659c6184b3e5d6a412432e1ccb4297cce123c41f9a8bb4fdb9ab19663aada978ea862ab2bd5f00bc91e4769ddd87543f5662b3af
tl;dr: Suggest changing
platform
toplatform_family
.After adding this asset to a Sensu Backend, using
sensuctl asset add sensu-plugins/sensu-plugins-cpu-checks --rename sensu-plugins-cpu-checks
, the current 4.0.0 release shows this Bonsai metadata (sensuctl asset list --format=yaml
):(I removed rhel and alpine sections.)
This prevents the asset-managers in sensu agents running on Ubuntu from fetching this asset when running checks. I don't think exluding Ubuntu is intentional?
Thus I suggest changing the metadata from
platform
toplatform_family
, and quickly release a 4.0.1.