Skip to content

feat: adopt pre-existing values.schema.json for dependency charts#202

Merged
dadav merged 1 commit intodadav:mainfrom
TvdW:dependencies
Mar 30, 2026
Merged

feat: adopt pre-existing values.schema.json for dependency charts#202
dadav merged 1 commit intodadav:mainfrom
TvdW:dependencies

Conversation

@TvdW
Copy link
Copy Markdown
Contributor

@TvdW TvdW commented Mar 27, 2026

Dependency charts that ship with their own values.schema.json are now used as-is instead of regenerating from values.yaml. This preserves rich constraints, descriptions, and custom x-* annotations from third-party charts.

Also fixes UnmarshalJSON to extract x-* custom annotations and track explicit const fields, matching the existing UnmarshalYAML behavior.

Dependency charts that ship with their own values.schema.json are now
used as-is instead of regenerating from values.yaml. This preserves
rich constraints, descriptions, and custom x-* annotations from
third-party charts.

Also fixes UnmarshalJSON to extract x-* custom annotations and track
explicit const fields, matching the existing UnmarshalYAML behavior.
@TvdW TvdW marked this pull request as ready for review March 27, 2026 18:09
@TvdW
Copy link
Copy Markdown
Contributor Author

TvdW commented Mar 27, 2026

PR with a bit of help from Claude.

Backstory: I tried to add a schema for a chart that has a dependency chart, that comes with its own schema, not generated with helm-schema. When helm-chart generates the schema it makes it more strict than the existing schema, leaving some options unconfigurable. With this PR the existing, presumably valid schema is preferred over creating our own

@dadav dadav merged commit 24272f6 into dadav:main Mar 30, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants