From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id AB13A1FF141 for ; Tue, 05 May 2026 10:36:13 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 107EA1CDB5; Tue, 5 May 2026 10:34:04 +0200 (CEST) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com, pbs-devel@lists.proxmox.com Subject: [PATCH proxmox-perl-rs v5 11/27] pve-rs: notify: add binding for triggering state refresh Date: Tue, 5 May 2026 10:32:32 +0200 Message-ID: <20260505083248.36450-12-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260505083248.36450-1-a.bied-charreton@proxmox.com> References: <20260505083248.36450-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.114 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: NENT7BJ36J6QXZBHPYE2JT63MAGRPMDT X-Message-ID-Hash: NENT7BJ36J6QXZBHPYE2JT63MAGRPMDT X-MailFrom: abied-charreton@jett.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox Backup Server development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Expose the new `trigger_state_refresh` proxmox-notify API to allow update jobs to trigger a refresh of the crate's internal state. This currently only serves the purpose of preventing unused OAuth2 refresh tokens from expiring. Signed-off-by: Arthur Bied-Charreton Reviewed-by: Lukas Wagner --- common/src/bindings/notify.rs | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/common/src/bindings/notify.rs b/common/src/bindings/notify.rs index ff1e6cf..8316013 100644 --- a/common/src/bindings/notify.rs +++ b/common/src/bindings/notify.rs @@ -141,6 +141,20 @@ pub mod proxmox_rs_notify { api::common::send(&config, ¬ification) } + /// Method: Refresh the state for all endpoints. + /// + /// This iterates through all configured targets, refreshing their state if needed. + /// The caller is responsible for locking the notifications config. + /// + /// See [`api::common::trigger_state_refresh`] + #[export(serialize_error)] + pub fn trigger_state_refresh( + #[try_from_ref] this: &NotificationConfig, + ) -> Result<(), HttpError> { + let config = this.config.lock().unwrap(); + api::common::trigger_state_refresh(&config) + } + /// Method: Get a list of all notification targets. /// /// See [`api::get_targets`]. -- 2.47.3