Open bbilyeu opened 2 years ago
Apologies for the radio silence!
4903638765 :: This is a foolish mistake on my part, failing only due to improper casing of the commit subject.
4890361620 :: (EDIT) Resolved
5030042061 :: All the rest are failing due to something specific to Saltstack master branch (3005?), which isn't live yet.
@bbilyeu Regarding the failing commitlint
job:
⧗ input: style(*): Added vim modelines
Adding simple vim modelines for convenience.
✖ subject must not be sentence-case, start-case, pascal-case, upper-case [subject-case]
✖ found 1 problems, 0 warnings
Please amend the commit title accordingly:
-style(*): Added vim modelines
+style(*): added vim modelines
In terms of the Rendering SLS 'base:snmp.conf' failed: could not find expected ':'
failures:
snmpv3 creating myv3user step 2 of 3:
file.line:
- name: /var/lib/snmp/snmpd.conf
- mode: insert
- location: end
- content:
createUser myv3user SHA myv3password AES v3privpass
- show_changes: False
- onchanges:
- snmpv3 creating myv3user step 1 of 3
This is happening because the whitespace control for createUser ...
macro needs to be amended. I've suggested something inline.
Only an initial review, just to get the CI working, hopefully.
@alxwr Will you be able to look over this PR?
@bbilyeu Actually, when you amend the commit, would you mind rebasing this PR on the latest commit to this repo? That will use the updated CI matrix.
@bbilyeu Actually, when you amend the commit, would you mind rebasing this PR on the latest commit to this repo? That will use the updated CI matrix.
I apologize, but my rebase knowledge/experience is embarrassingly weak. Would amending the commit and rebasing not bloat the commit history with duplicates?
I apologize, but my rebase knowledge/experience is embarrassingly weak. Would amending the commit and rebasing not bloat the commit history with duplicates?
@bbilyeu No, it's an expected (and usually preferred) procedure. Once you've rebased and amended the commit message, you need to force push it back here.
This is useful documentation:
--force-with-lease
) is discussed in the section directly below the one I've linked.@bbilyeu I've just noticed that the very last commit message needs to be updated as well:
-Update snmp/macros.jinja
+fix(macros.jinja): fix macro `v3_createUser_string` whitespace control
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
?Yes, there are a few breaking changes.
logconnect
has been changed todontLogTCPWrappersConnects
which identically matches the snmpd.conf option (instead of forcing a formula specific value). This also corrects a slightly less than intuitive boolean usage.syscontact
changed tosysContact
to also match the snmpd.conf option.location
changed tosysLocation
to also match the snmpd.conf option.Related issues and/or pull requests
Describe the changes you're proposing
Pillar / config required to test the proposed changes
None, files
test/integration/default/controls/config.rb
andtest/salt/pillar/default.sls
were updated to all turnkey testing.Debug log showing how the proposed changes work
CentOS 7 3003.3 and 3004.0 (both py3) would fail to start up SSH. Skipping those
CentOS 8 3003.3 py3
CentOS 8 3004.0 py3
Debian 9 3003.3 py3
Debian 9 3004.0 py3
Debian 10 3003.3 py3
Debian 10 3004.0 py3
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context