Update Helm release alertmanager-snmp-notifier to v1 (main) (!4456) · Merge requests · Sylva-projects / sylva-core

This MR contains the following updates:

Package	Update	Change
alertmanager-snmp-notifier (source)	major	`0.5.0` -> `1.0.0`

prometheus-community/helm-charts (alertmanager-snmp-notifier)

The SNMP Notifier handles alerts coming from Prometheus Alertmanager and relay them as SNMP traps.

Full Changelog: https://github.com/prometheus-community/helm-charts/compare/prometheus-yet-another-cloudwatch-exporter-0.40.1...alertmanager-snmp-notifier-1.0.0

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever MR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this MR and you won't be reminded about this update again.

This MR has been generated by Renovate Bot Sylva instance.

CI configuration couldn't be handle by MR description. A dedicated comment has been posted to control it.

If no checkbox is checked, a default pipeline will be enabled (capm3, or capo if capo label is set)

CI configuration

Below you can choose test deployment variants to run in this MR's CI.

Click to open to CI configuration

Legend:

Icon	Meaning	Available values
☁️	Infra Provider	`capd`, `capo`, `capm3`
🚀	Bootstrap Provider	`kubeadm` (alias `kadm`), `rke2`
🐧	Node OS	`ubuntu`, `suse`
🛠️	Deployment Options	`light-deploy`, `dev-sources`, `ha`, `misc`, `maxsurge-0`
🎬	Pipeline Scenarios	Available scenario list and description

Notes:

Enabling autorun will make deployment pipelines to be run automatically without human interaction
Disabling allow failure will make deployment pipelines mandatory for pipeline success.
if both autorun and allow failure are disabled, deployment pipelines will need manual triggering but will be blocking the pipeline

Edited Jun 18, 2025 by Bogdan Antohe