Pillar / config required to test the proposed changes
–
Debug log showing how the proposed changes work
----------
ID: sshd_config
Function: file.managed
Name: /etc/ssh/sshd_config
Result: None
Comment: The file /etc/ssh/sshd_config is set to be changed
Note: No changes made, actual changes may
be different due to other states.
Started: 02:09:22.861195
Duration: 150.767 ms
Changes:
----------
diff:
---
+++
@@ -1,7 +1,4 @@
# This file is managed by salt. Manual changes are going to be overwritten.
-# The contents of the original sshd_config are kept on the bottom for
-# quick reference.
-# See the sshd_config(5) manpage for details
Port 22
Protocol 2
----------
ID: openssh
Function: service.running
Name: sshd
Result: None
Comment: Service is set to be restarted
Started: 02:09:23.132870
Duration: 55.057 ms
Changes:
Summary for host.domain.tld
-------------
Succeeded: 12 (unchanged=2, changed=1)
Failed: 0
-------------
Total states run: 12
Total run time: 2.959 s
Documentation checklist
[ ] Updated the README (e.g. Available states).
[ ] Updated pillar.example.
Testing checklist
[ ] Included in Kitchen (i.e. under state_top).
[ ] Covered by new/existing tests (e.g. InSpec, Serverspec, etc.).
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/openssh-formula/issues/120
Describe the changes you're proposing
Remove a misleading comment.
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