action #135005
Updated by tinita 9 months ago
## Motivation
See https://gitlab.suse.de/openqa/salt-pillars-openqa/-/merge_requests/582#note_530351
sls files for Salt are Jinja templates. After jinja processing they result in YAML files, and only then can be checked for the correct YAML syntax.
That means we cannot just use a linter on those files in merge requests.
The files can grow quite large, so it's hard to manually review if the YAML would look actually correct. Using aliases and merhe keys (`<<`) could help reducing the size, but checking aliases manually close to impossible, because you have to keep track of where they are created (anchors) and used, and if there is no typo.
A linter can do that. However there seems to be no way to run salt in a dry mode to automatically test all possible jinja values.
## Suggestions
- How about trying to fill in example values for jinja processing and then check the resulting YAML?