Closed benfiedler closed 1 year ago
@benfiedler you must respect the commit message format for you pull request you can find the documentation here : https://github.com/saltstack-formulas/.github/blob/master/CONTRIBUTING.rst#commit-message-formatting
…it as EnvironmentFile
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
https://github.com/saltstack-formulas/docker-formula/issues/317
Describe the changes you're proposing
Create+manage a systemd dropin file if 'environ' pillar is configured to ensure the environ file (/etc/default/docker) is being used by the docker service. A systemd daemon-reload will be run if salt detects changes in the override file, and the docker service will be restarted if salt detects changes in the environ file.
Pillar / config required to test the proposed changes
docker/defaults.yaml docker/software/config/clean.sls docker/software/config/dropin.sls docker/software/config/init.sls docker/software/service/running.sls
Debug log showing how the proposed changes work
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context