Skip to content

fix: copy dependencies on aliasing to avoid sharing chart references on multiply aliased dependencies [v3 backport]#30802

Open
dastrobu wants to merge 1 commit intohelm:dev-v3from
dastrobu:dev-v3-copy-dependencies-on-aliasing
Open

fix: copy dependencies on aliasing to avoid sharing chart references on multiply aliased dependencies [v3 backport]#30802
dastrobu wants to merge 1 commit intohelm:dev-v3from
dastrobu:dev-v3-copy-dependencies-on-aliasing

Conversation

@dastrobu
Copy link
Copy Markdown
Contributor

This is a back port of #9175 as requested per #9175 (comment)

Dependencies keep a reference on their parent chart, which breaks if a chart reference is shared among multiple aliases.
By copying the dependencies, parent information can be set correctly to render the templates as expected later on.

Note that this change will make ChartFullPath return a different path for sub-subcharts. It will contain the alias names instead of the path to the chart files which makes it consistent with paths to templates on the subchart level.

Closes #9150

Signed-off-by: Daniel Strobusch 1847260+dastrobu@users.noreply.github.com

If applicable:

  • this PR contains documentation
  • this PR contains unit tests
  • this PR has been tested for backwards compatibility

@pull-request-size pull-request-size bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Apr 25, 2025
imported values are stored in dependency objects, which breaks if a chart dependency is shared among multiple aliases.
By copying the dependency objects in the metadata values can be imported correctly.

Supersedes helm#10174

Signed-off-by: Daniel Strobusch <1847260+dastrobu@users.noreply.github.com>
@dastrobu dastrobu force-pushed the dev-v3-copy-dependencies-on-aliasing branch from ae7f176 to bee2978 Compare April 25, 2025 07:00
@dastrobu dastrobu marked this pull request as ready for review April 25, 2025 07:10
@scottrigby scottrigby added the bug Categorizes issue or PR as related to a bug. label Apr 25, 2025
Copy link
Copy Markdown
Contributor

@TerryHowe TerryHowe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@benoittgt
Copy link
Copy Markdown
Contributor

benoittgt commented Jun 1, 2025

Should it be closed? With the new backport strategy ?

@dastrobu
Copy link
Copy Markdown
Contributor Author

dastrobu commented Jun 2, 2025

Should it be closed? With the new backport strategy ?

What is the new back-port strategy? I created the PR as a request for a back-port.

@benoittgt
Copy link
Copy Markdown
Contributor

benoittgt commented Jun 2, 2025

Sorry @dastrobu I was not clear enough. I was referring to the last dev meeting where it was mentioned that backporting should be limited to bug and security fixes only.

We will see with the code review, I'm probably wrong. :)

@KalenWessel
Copy link
Copy Markdown

It would be great to get this back ported.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Oct 2, 2025

This pull request has been marked as stale because it has been open for 90 days with no activity. This pull request will be automatically closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Oct 2, 2025
@hobti01
Copy link
Copy Markdown
Contributor

hobti01 commented Oct 2, 2025

We'd really appreciate this bug fix so we can remove our local fork of Helm. Is there anything the community can do to move this forward?

@pierluigilenoci
Copy link
Copy Markdown

@mattfarina @TerryHowe @AustinAbro321 @gjenkins8 @benoittgt, can one of you help move this PR forward?

1 similar comment
@pierluigilenoci
Copy link
Copy Markdown

@mattfarina @TerryHowe @AustinAbro321 @gjenkins8 @benoittgt, can one of you help move this PR forward?

@github-actions
Copy link
Copy Markdown

This pull request has been marked as stale because it has been open for 90 days with no activity. This pull request will be automatically closed in 30 days if no further activity occurs.

@github-actions github-actions bot added the Stale label Mar 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Categorizes issue or PR as related to a bug. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. Stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants