Closed myii closed 5 years ago
[build]
[chore]
[ci]
[feat]
[fix]
[perf]
[refactor]
[revert]
[style]
[docs]
[test]
BREAKING CHANGE
No.
Follow-up for #44.
Use grains.get directly rather than via. config.get. Also increase the list of containers that are checked for, based on discussions in the wg.
grains.get
config.get
wg
Covered by existing setup.
As shown in Travis.
README
Available states
pillar.example
state_top
:tada: This PR is included in version 0.19.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
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
Follow-up for #44.
Describe the changes you're proposing
Use
grains.get
directly rather than via.config.get
. Also increase the list of containers that are checked for, based on discussions in thewg
.Pillar / config required to test the proposed changes
Covered by existing setup.
Debug log showing how the proposed changes work
As shown in Travis.
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context