gotmpl in helmfile YAML files

[vquie]

Hi,

we are currently in the middle of lifting mega linter into production state to clean our code. Also we are now facing an issue where I think mega-linter treats gotmpl in yaml files as json.
{{ … }} would become { { … } }. We have disabled linting on these files with the regex exclude filter to avoid breaking changes.
What is the best way, if any, to solve this?

We are using ci_light flavor with hosted GitLab on our own runners.

Cheers

[Kurt-von-Laven]

This question sounds like it might be best addressed to helm.

[vquie]

It’s actually helmfile.

https://github.com/roboll/helmfile/blob/master/docs/writing-helmfile.md

Do you mean I should ask over there?

[Kurt-von-Laven]

Yeah, I think you will have better odds. I don't see a connection to MegaLinter's behavior.

[vquie]

I thought we could treat the file accordingly to the extension and not to the content.
Or maybe keep json linters out if it a yaml, or maybe dig a little deeper if it that case after all and not something else is going on.

[Kurt-von-Laven]

MegaLinter only uses extensions, not content, to decide which linters to invoke, so my assumption is that Helm is modifying your Helm files, not some other linter. To test this, you could try running with only Helm enabled or run Helm directly.

[nvuillam]

@Kurt-von-Laven MegaLinter can also use content , if property file_contains is present on the linter descriptor :)

[nvuillam]

@vquie the conditions for detecting helm file are the following: https://megalinter.io/latest/descriptors/kubernetes_helm/#how-are-identified-applicable-files

• Activated only if sub-directory is found. (directory name can be overridden withKUBERNETES_DIRECTORY)
• Activated only if one of these files is found: Chart.yml, Chart.yaml
• File extensions: .yml, .yaml, .json
• Detected file content (regex): apiVersion:, kustomize.config.k8s.io, tekton

What linter impacts which files in your repo ?
I'm not very familiar with gotmpl , please give more info so we can help :)

[nvuillam]

That's very strange, the code called to filter files is the same at root, descriptor and linter level :/

[nvuillam]

Are you sure this is prettier that formats the file ?
Could you try with LOG_LEVEL: DEBUG to have more output so we can investigate ?

[vquie]

I am sure. I ran it with LOG_LEVEL: DEBUG and found the very command (prettier --write $file in an array). Was able to reproduce it with this command. And also..... this false changes do not happen again since I disabled it with the line I sent earlier. :-)

[Kurt-von-Laven]

This is really a stretch, but one possible explanation could be that some other instance of Prettier, such as JSON_PRETTIER, is running on the Helm files and isn't filtered. Hard to say much more here without seeing the logs though.

[vquie]

Please have a look at this example: https://github.com/vquie/mega-linter-prettier-test
You can easily reproduce it and debug logs are pushed to the repo.