From 41a74466b9b019e521593861d3ba32d2178d761a Mon Sep 17 00:00:00 2001 From: Ralph Bean Date: Thu, 19 Dec 2024 18:04:11 -0500 Subject: [PATCH] Add to the icm schema a field to indicate if the icm should be ignored This enables a path to deprecation. Today, scanners depend on this file primarilly for the list of content_sets. In the future, with konflux-ci, we want third-party scanners to refer to the dnf database for a more precise mapping of which rpms come from which content_sets. The idea here is that image providers can still publish an icm file, but if the from_dnf_hint is set to true, then scanners are supposed to ignore the icm file and trust the dnf database instead. Scanners that haven't been ported to the new method will continue to work in the current imprecise way until they adapt to scanning the dnf database. --- atomic_reactor/schemas/content_manifest.json | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/atomic_reactor/schemas/content_manifest.json b/atomic_reactor/schemas/content_manifest.json index f9a44b068..30f7a38d6 100644 --- a/atomic_reactor/schemas/content_manifest.json +++ b/atomic_reactor/schemas/content_manifest.json @@ -35,6 +35,11 @@ "description": "Pulp content sets available during the current image build", "type": "array", "items": { "$ref": "#/definitions/content_set" } + }, + "from_dnf_hint": { + "description": "A hint indicating if scanners should ignore this file and use the dnf database instead for more precise content_sets", + "type": "boolean", + "default": false } }, "required": ["metadata"],