-
Notifications
You must be signed in to change notification settings - Fork 417
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
Updating log_format in pillar.example #219
Conversation
This new format works well in |
@daks If you do get around to changing the tests to |
@garrettw Thanks for this. After #229 updated the test matrix, I was able to add another test to confirm this is working for all minions (in #231). Test results here: https://travis-ci.org/myii/nginx-formula/builds/524996941. |
🎉 This PR is included in version 0.56.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
test(inspec): add test for `log_format` #219
## [0.56.1](v0.56.0...v0.56.1) (2019-04-27) ### Tests * **inspec:** add test for `log_format` [#219](#219) ([4ed788e](4ed788e))
## [0.56.1](saltstack-formulas/nginx-formula@v0.56.0...v0.56.1) (2019-04-27) ### Tests * **inspec:** add test for `log_format` [saltstack-formulas#219](saltstack-formulas#219) ([4ed788e](saltstack-formulas@4ed788e))
## [0.56.1](saltstack-formulas/nginx-formula@v0.56.0...v0.56.1) (2019-04-27) ### Tests * **inspec:** add test for `log_format` [saltstack-formulas#219](saltstack-formulas#219) ([4ed788e](saltstack-formulas@4ed788e))
Continuing changes discussed in #217.
The main issue that needs discussing/testing is whether the
access_log
line (141 after this first commit) still needs to be part oflog_format
as a workaround (see #122) rather than just using the following line to specify it in YAML format.