Skip to content

fusion: keep full HelmRelease object in values.yaml#177

Merged
tamalsaha merged 1 commit into
masterfrom
fusion-keep-helmrelease-full
Jul 1, 2026
Merged

fusion: keep full HelmRelease object in values.yaml#177
tamalsaha merged 1 commit into
masterfrom
fusion-keep-helmrelease-full

Conversation

@tamalsaha

Copy link
Copy Markdown
Contributor

What

Skip the fusion values.yaml trimming (introduced in #174) for HelmRelease resources in the helm.toolkit.fluxcd.io API group. For those, the full object is kept in values.yaml.

Why

#174 trims each resource entry to only apiVersion, kind and metadata, on the basis that the remaining fields are sourced from the resource's schema defaults. That assumption does not hold for a HelmRelease: its spec (chart reference, chart version, values, etc.) is meaningful and cannot be reconstructed from schema defaults, so it must be preserved.

Behavior

The values.yaml trimming (keep only apiVersion, kind and metadata) should
not apply to HelmRelease resources in the helm.toolkit.fluxcd.io group,
since their spec (chart, values, etc.) is not sourced from schema defaults
and must be preserved.

Signed-off-by: Tamal Saha <tamal@appscode.com>
@tamalsaha tamalsaha merged commit 2e3a616 into master Jul 1, 2026
4 checks passed
@tamalsaha tamalsaha deleted the fusion-keep-helmrelease-full branch July 1, 2026 02:02
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.

1 participant