Closed major0 closed 3 years ago
@major0 Thanks for the PR. You're not going to win either way, since all of the Debian/Ubuntu pkgrepo
entries are using http
and all of the key_url
entries are using https
. Let's settle on one (probably https
) and just fix the tests. If you can make sure Allow edits from maintainers
is allowed and I'll push the changes to complete this PR.
@major0 Thanks for the PR. You're not going to win either way, since all of the Debian/Ubuntu
pkgrepo
entries are usinghttp
and all of thekey_url
entries are usinghttps
. Let's settle on one (probablyhttps
) and just fix the tests. If you can make sureAllow edits from maintainers
is allowed and I'll push the changes to complete this PR.
Allow edits
is allowed.
Fixed and merged (to use https
), @major0 -- thanks again for the PR.
Appreciate the review, @n-rodriguez.
:tada: This PR is included in version 1.8.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
Make the upstream salt package repository selectable, thus allowing the use of archived salt versions (hosted in http://archive.repo.saltproject.io), as well as custom salt versions hosted in alternate repositories.
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
Describe the changes you're proposing
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