From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 78830A0A7A for ; Thu, 9 Nov 2023 16:34:16 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 574521704D for ; Thu, 9 Nov 2023 16:34:16 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Thu, 9 Nov 2023 16:34:15 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 5DA0347851 for ; Thu, 9 Nov 2023 16:34:15 +0100 (CET) From: Stefan Sterz To: pbs-devel@lists.proxmox.com Date: Thu, 9 Nov 2023 16:33:59 +0100 Message-Id: <20231109153403.529870-3-s.sterz@proxmox.com> X-Mailer: git-send-email 2.39.2 In-Reply-To: <20231109153403.529870-1-s.sterz@proxmox.com> References: <20231109153403.529870-1-s.sterz@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -0.089 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 SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: [pbs-devel] [PATCH proxmox 2/6] subscription: expose the `next_due_date` as an `i64` X-BeenThere: pbs-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox Backup Server development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 09 Nov 2023 15:34:16 -0000 internally `SubscriptionInfo` already uses the `parse_next_due` helper to parse the next due date to an epoch. this exposes a function that allows us to use the epoch outside of this crate too. for example, a user of pom may have multiple subscription for the same system. in that case we want to apply the one with the due date that is furthest in the future. Signed-off-by: Stefan Sterz --- proxmox-subscription/src/subscription_info.rs | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/proxmox-subscription/src/subscription_info.rs b/proxmox-subscription/src/subscription_info.rs index dc10a2a..45f1796 100644 --- a/proxmox-subscription/src/subscription_info.rs +++ b/proxmox-subscription/src/subscription_info.rs @@ -286,6 +286,13 @@ impl SubscriptionInfo { .ok_or_else(|| format_err!("no product key set")) .map(|key| key[..3].parse::())? } + + pub fn get_next_due_date(&self) -> Result { + self.nextduedate + .as_ref() + .ok_or_else(|| format_err!("no next due date set")) + .map(|e| parse_next_due(e))? + } } /// Shortcut for md5 sums. -- 2.39.2