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 73DE31FF13C for ; Thu, 02 Apr 2026 14:23:51 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 4AA9D15752; Thu, 2 Apr 2026 14:24:20 +0200 (CEST) From: Lukas Wagner To: pdm-devel@lists.proxmox.com, Shan Shaji In-Reply-To: <20260401142143.309509-1-s.shaji@proxmox.com> References: <20260401142143.309509-1-s.shaji@proxmox.com> Subject: applied: [PATCH datacenter-manager v4 0/5] fix #7179: expose ACME commands inside admin CLI Message-Id: <177513147094.338311.4887752466314496094.b4-ty@proxmox.com> Date: Thu, 02 Apr 2026 14:04:30 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1775132597119 X-SPAM-LEVEL: Spam detection results: 0 AWL -1.571 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_LOTSOFHASH 0.25 Emails with lots of hash-like gibberish RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 1 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: TME5XCN4TYHT45NMSLXIMQPCM5BZQ65Y X-Message-ID-Hash: TME5XCN4TYHT45NMSLXIMQPCM5BZQ65Y X-MailFrom: l.wagner@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 Datacenter Manager development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Wed, 01 Apr 2026 16:21:38 +0200, Shan Shaji wrote: > Previously, ACME commands were not exposed through the admin CLI. > Added the necessary functionality to manage ACME settings directly > via the command line. The changes are done by taking reference from > the proxmox-backup codebase. > > changes since v3: > - Rebase with master. > - rephrase commit messages. > - retested the changes again. > > [...] Applied, thanks! [1/5] cli: admin: initialize worker tasks before calling acme API methods commit: 637a0063bc7b2e833be90ee569788a6edf7f57bc [2/5] api: acme: define API type for ACME registration parameters commit: 8e50f425a565323aaac17cba83b483a168c2ee78 [3/5] server: api: add contact schema for ACME account update endpoint commit: 7d91baa6d466380853b38190462e8660516ed1da [4/5] fix #7179: cli: admin: add commands to manage ACME settings commit: 5df0d5b6ef8536db6b0cd311d3c0bb4a6b35e367 [5/5] chore: update proxmox-acme version to 1 commit: 0f3bf33ff8e21312a8567bb68ff8a32ffa56d2f1 Best regards, -- Lukas Wagner