-
Notifications
You must be signed in to change notification settings - Fork 100
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
Use cmd_check to validate config files #37
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,2 @@ | ||
.kitchen/ | ||
Gemfile.lock |
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1 @@ | ||
{{ content | tojson(indent=2) }} | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The
This is more portable and reliable. As far as I understand upstream Jinja docs, the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO, manage structured files with
file.managed
is really bad (I tried this myself and it always requires many hacks and checks).I'd suggest to keep using
file.serialize
, and create another check for syntax specifically.We could use mod_run_check_cmd, but just realized it doesn't work as expected (it's used as an internal function for
file.managed
. It's already exposed externally, however it doesn't met functions requirements, where it doesn't havename,changes
in returned output).So till fixing that (mostly I will make a PR for that), let's use
cmd.run
withunless
:The
unless
clue, will prevent running the command when it has a valid syntax. So it avoids any extra noise.