From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pve-devel-bounces@lists.proxmox.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id D668E1FF16E for <inbox@lore.proxmox.com>; Mon, 9 Dec 2024 13:46:09 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 01FEA1A45; Mon, 9 Dec 2024 13:46:10 +0100 (CET) From: Christoph Heiss <c.heiss@proxmox.com> To: pve-devel@lists.proxmox.com Date: Mon, 9 Dec 2024 13:45:53 +0100 Message-ID: <20241209124601.1272122-1-c.heiss@proxmox.com> X-Mailer: git-send-email 2.47.0 MIME-Version: 1.0 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.028 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 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. SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: [pve-devel] [PATCH installer 0/6] assistant: properly validate answer file settings X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> Reply-To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: pve-devel-bounces@lists.proxmox.com Sender: "pve-devel" <pve-devel-bounces@lists.proxmox.com> Currently, the answer file is only syntax-checked, i.e. if it can be parsed as TOML and whether it is of valid structure, but the actual answer settings are not looked at. Patch #2 is a refactoring of the whole locale info generation, as to generate the final information structure at build-time - thus being able to include it in the auto-install-assistant for verify answer file settings. Christoph Heiss (6): tui: options: simplify unit-test setup country.pl: generate final structure as json at build time directly common: setup: read locale info as shipped by the installer directly common: setup: include path in error message if file could not be read fix #5889: assistant: validate answer email & root password settings assistant: validate answer first-boot hook and locale settings .gitignore | 2 +- Makefile | 16 +-- Proxmox/Install/ISOEnv.pm | 56 +-------- country.pl | 116 ++++++++++++++---- proxmox-auto-install-assistant/src/main.rs | 18 ++- proxmox-auto-installer/src/utils.rs | 6 +- .../tests/resources/iso-info.json | 2 +- proxmox-installer-common/src/setup.rs | 34 +++-- proxmox-low-level-installer | 3 - proxmox-tui-installer/src/options.rs | 26 +--- 10 files changed, 152 insertions(+), 127 deletions(-) -- 2.47.0 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel