6 Commits (56466916e283fa24c1916e4eb575c9d9c3b2bdcd)

Author	SHA1	Message	Date
shuv0id	2dc5864f44	fix: add missing context to debug logs ... Adds chart name to dependency logs, namespace to resource waiting logs, and confirmation message when all resources are ready. Addresses #31520 Signed-off-by: shuv0id <110290476+shuv0id@users.noreply.github.com>	5 months ago
Benoit Tigeot	97b7a1c9ae	Merge branch 'main' into fix-31170-URN ... Signed-off-by: Benoit Tigeot <benoittgt@users.noreply.github.com> Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>	6 months ago
Benoit Tigeot	939fff9cb9	Avoid "panic: interface conversion: interface {} is nil" ... Closes: #31202 Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>	8 months ago
Benoit Tigeot	8025a397e6	Ignore duplicated URN in logs ... Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>	8 months ago
Benoit Tigeot	03bb62f63d	jsonschema: warn and ignore unresolved URN $ref to match v3.18.4 ... - v3.18.5 switched jsonschema and began resolving external $ref at compile-time, exposing missing urn handling (“no URLLoader registered for urn:…”). - Add urn scheme loader and pluggable URNResolver. If unresolved, log a warning and return a permissive true schema (back-compat). - Apply to pkg/chart/v2 and internal/chart/v3 validators. Not sure about that Note: external URNs need AddResource/Resolver (the CLI uses --map for this). Warning may appear twice since both validators run. Another strategy could be to add the option to import more "external schema" explicitly but it is another PR. Something similar to `--map` from jsonschema package (santhosh-tekuri/jsonschema@ed65924). Close: #31170 Signed-off-by: Benoit Tigeot <benoit.tigeot@lifen.fr>	8 months ago
Matt Farina	9dcc49cbd5	Move lint pkg to be part of each chart version ... Linting is specific to the chart versions. A v2 and v3 chart will lint differently. To accomplish this, packages like engine need to be able to handle different chart versions. This was accomplished by some changes: 1. The introduction of a Charter interface for charts 2. The ChartAccessor which is able to accept a chart and then provide access to its data via an interface. There is an interface, factory, and implementation for each version of chart. 3. Common packages were moved to a common and util packages. Due to some package loops, there are 2 packages which may get some consolidation in the future. The new interfaces provide the foundation to move the actions and cmd packages to be able to handle multiple apiVersions of charts. Signed-off-by: Matt Farina <matt.farina@suse.com>	8 months ago