Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Overriding Helm chart dependency version in parent chart #13041

Closed
apiwoni opened this issue May 16, 2024 · 2 comments
Closed

Overriding Helm chart dependency version in parent chart #13041

apiwoni opened this issue May 16, 2024 · 2 comments

Comments

@apiwoni
Copy link

apiwoni commented May 16, 2024

Given chart definition as follows:

apiVersion: v2
name: container-chart
description: Chart containing many other charts
type: application
version: 1.0.0
appVersion: "1.0.0"
dependencies:
- name: other-chart
  version: 1.1.0
  repository: <repositoryUrl>

Given multiple environment specific parent Helm charts with dependency. on the above defined as follows:

apiVersion: v2
name: parent-environment-chart
description: Parent chart for specific environment
type: application
version: 1.0.0
appVersion: "1.0.0"
dependencies:
- name:  container-chart
  version: 1.0.0
  repository: <fileRepositoryUrl>

Can I override "other-chart" Helm chart version in "parent-environment-chart" with other compatible version like 1.1.1?

Please note "container-chart" is not published and is part of repo for "parent-environment-chart" so its repository is file-based. Also, I need specific version for "other-chart" in "parent-environment-chart".
For this reason, why don't you publish "container-chart' with different dependency version is not relevant solution!

@gjenkins8
Copy link
Contributor

There isn't a way to do this today. If you search, I remember/believe there is an issue which discusses this in depth

@apiwoni
Copy link
Author

apiwoni commented May 21, 2024

@gjenkins8 Thank you. I'll try to search again. I found few similar issues but they all discussed wildcards. Feel free to close this.

@apiwoni apiwoni closed this as completed May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants