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

Specify Jsonnet-Bundler Dependency Versions in Hierarchy #213

Closed
srueg opened this issue Oct 12, 2020 · 3 comments · Fixed by #275
Closed

Specify Jsonnet-Bundler Dependency Versions in Hierarchy #213

srueg opened this issue Oct 12, 2020 · 3 comments · Fixed by #275
Labels
enhancement New feature or request

Comments

@srueg
Copy link
Contributor

srueg commented Oct 12, 2020

Context

Currently a component can have a jsonnetfile.json to specify Jsonnet dependencies. This file is not handled by Kapitan and therefore can't make use of the configuration hierarchy. The only way to have different versions of dependencies is with a separate branch of the component (which then can be specified in the hierarchy).

Implement a possibility to specify Jsonnet dependencies and their version in the hierarchy so they can be overridden.

For example the kube-prometheus library is specific to the K8s version and therefore needs a different version (git branch/commit) for each K8s version.

Alternatives

As described, an alternative would be to use different branches to handle this.

@srueg srueg added the enhancement New feature or request label Oct 12, 2020
@srueg
Copy link
Contributor Author

srueg commented Oct 12, 2020

A possible solution could be to generate the jsonnetfile.json in Commodore and use input form the hierarchy to do so.

@srueg
Copy link
Contributor Author

srueg commented Oct 13, 2020

Implementation might affect #216

@corvus-ch
Copy link
Contributor

This might also affect #173

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants