Closed ze42 closed 2 years ago
When option was specified, it appeared twice in config, making configuration file buggy, and not loaded.
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
log_fmt_console can now be specified without breaking the generated config files.
salt: master: log_fmt_console: '%(colorlevel)s %(colormsg)s' minion: log_fmt_console: '%(colorlevel)s %(colormsg)s'
README
Available states
pillar.example
state_top
Thanks @ze42 and @aboe76 for review
:tada: This PR is included in version 1.10.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
When option was specified, it appeared twice in config, making configuration file buggy, and not loaded.
PR progress checklist (to be filled in by reviewers)
What type of PR is this?
Primary type
[build]
Changes related to the build system[chore]
Changes to the build process or auxiliary tools and libraries such as documentation generation[ci]
Changes to the continuous integration configuration[feat]
A new feature[fix]
A bug fix[perf]
A code change that improves performance[refactor]
A code change that neither fixes a bug nor adds a feature[revert]
A change used to revert a previous commit[style]
Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc.)Secondary type
[docs]
Documentation changes[test]
Adding missing or correcting existing testsDoes this PR introduce a
BREAKING CHANGE
?No.
Related issues and/or pull requests
Describe the changes you're proposing
log_fmt_console can now be specified without breaking the generated config files.
Pillar / config required to test the proposed changes
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context