-
Notifications
You must be signed in to change notification settings - Fork 118
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(repo): update repo config for keyring #162
Conversation
Any reason you don't include Debian 11 and Ubuntu 20.04 for the new method? I had much greater results by doing that on our current Debian 11 machines. |
It doesn't seem to work for Focal. I haven't tested Debian 11 |
Please fix pre-commit lint errors. Also I'm strongly recommend to squash all your commits into one, that's a pretty small change multiple commits reduce readability. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for delay. Overall I'm ok with changes, they don't break anything. Unfortunately CI test doesn't work properly for Debian 11, Ubuntu 22.04 due old version of Zabbix used in test.
@waynegemmell thanks! |
Thanks :) |
🎉 This PR is included in version 1.3.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
#160
Describe the changes you're proposing
Newer versions of Ubuntu and Debian have depricated salt-key. While it still works in practice, the errors make salt fail.
This update implements the salt-key setting that bypasses it for effected versions of Ubuntu/Debian.
Pillar / config required to test the proposed changes
No changes when using the formula.
Documentation checklist
README
(e.g.Available states
).pillar.example
.Testing checklist
state_top
).Additional context