Closed danny-smit closed 3 years ago
I just noticed that, according to the toplevel README, the config
keys are meant to do the same as the environ
keys?! That would imply that introducing daemon_config
key would be better.
Thanks for the PR, @danny-smit.
@noelmcloughlin @hatifnatt Would either of you mind reviewing this PR, since you've both been recently active here?
Thanks @danny-smit this is a big one for us couldn't have had better timing
:tada: This PR is included in version 2.0.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
Bug: Can't manage /etc/docker/daemon.json using pillar syntax in v1.0.0 (#257)
Describe the changes you're proposing
This change makes the pillar key
daemon_config
update the /etc/docker/daemon.json.Pillar / config required to test the proposed changes
Fictive example configuration:
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context