-
Notifications
You must be signed in to change notification settings - Fork 533
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
k8s:helm should use values.yaml file #327
Comments
Hi
The model classes are typed, so when generating the class instance and setting the values as placeholders for variables, this will only work for string fields that can be set with a We'll need to figure out a way to overcome this, probably by converting the class instance to an intermediate Map, setting the problematic fields on the Map, and then serializing it. |
Besides the problems with replacing integer values, Helm mojo is not behaving correctly.
Template parameters (k8s:resource & k8s:helm)As of now, ReourceMojo#findTemplate locates the first resource of type This means that if there are several (1-first-template.yml, template.yml, etc.) only the first will be considered to gather parameters. The List of parameters should be gathered as: (List<Parameter>)(Template) resources.getItems().stream()
.filter(template -> template instanceof Template)
.map(Template.class::cast)
.map(Template::getParameters)
.collect(Collectors.toList()) Only for Helm Mojo
Helm should be decoupled from resource goal. Helm should run a resource generation but without replacing parameter placeholders. |
k8s:helm
generate Helm artifacts.. but the content of deleployment.yaml and others doesn't use values.yaml
you should use standars values like this
deployment.yaml
...
The text was updated successfully, but these errors were encountered: