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 AB2B41FF187 for ; Mon, 3 Nov 2025 09:03:08 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id E767A13E23; Mon, 3 Nov 2025 09:03:43 +0100 (CET) From: Nicolas Frey To: pve-devel@lists.proxmox.com Date: Mon, 3 Nov 2025 09:03:08 +0100 Message-ID: <20251103080310.60168-1-n.frey@proxmox.com> X-Mailer: git-send-email 2.47.3 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.102 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 RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.001 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 0.001 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 0.001 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. 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 URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [acme.sh] Subject: [pve-devel] [PATCH proxmox-acme 0/2] Automate DNS challenge json schema with script X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Proxmox VE development discussion Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" This patch series aims to automate the process of creating the json schema for DNS challenges provided by acme.sh. This is done via a simple bash script, which parses out the required information using the `dns__info` variable in each of the providers' dnsapi scripts. This variable includes the Options, their descriptions and sometimes the default/optional values. This is then used to generate the json schema, which is then normalized. If the contents of the variable are malformed or it is empty, an empty entry will be generated. The only attribute this script cannot parse out is the type the variable has (e.g. `integer`/`string`) so it assigns string to all fields. This may be fine, as I only saw around 10 (of ~300) occurances where `integer` would be a better fit. The second patch uses the script to generate the schema. Nicolas Frey (2): dns: schema: add generate schema script dns: generate schema src/Makefile | 4 + src/dns-challenge-schema.json | 2201 +++++++++++++++++++++++++++++---- src/generate_schema.sh | 135 ++ 3 files changed, 2083 insertions(+), 257 deletions(-) create mode 100755 src/generate_schema.sh -- 2.47.3 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel