-
Notifications
You must be signed in to change notification settings - Fork 75
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
Replace legacy Allowed-Origins with Origins-Pattern on all distros #204
Conversation
To ensure people don't trip over old configs, let's validate that the given origins comply with the current format. Straight-up removed legacy origins as, after checking, none of the Debian-based distributions (and thus their derivates) we support still require legacy-style origin definition. This is a breaking change.
d15a763
to
2d03650
Compare
* Leftover legacy formats in tests removed. * A typo in the ESM repositories fixed. * Use correct test specs.
8666f5b
to
aea305f
Compare
Looks good, maybe a more descriptive PR title for the changelog? |
metadata.json
Outdated
@@ -27,7 +27,8 @@ | |||
"operatingsystem": "Ubuntu", | |||
"operatingsystemrelease": [ | |||
"18.04", | |||
"20.04" | |||
"20.04", | |||
"21.04" |
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.
do you have a ubuntu 21.04 box around to provide factsets for https://github.com/voxpupuli/facterdb ? Also please create a new PR that adds 21.04 here. That allows us to put the two PRs in different sections (breaking change vs enhancement)
To be fair… I didn't even notice I forgot to change the PR title from the branch name. ta. :) |
You might consider updating the README. Currently documentation there still references the now-removed |
`legacy_origin` was removed in #204.
Thanks, I made #205 for updating the README. |
Pull Request (PR) description
Since all Debian-based distributions VP officially supports feature a version of
unattended-upgrade
that's compatible with theOrigins-Pattern
variable, this PR gets rid of the legacy configuration altogether.To ensure that no one gets unexpected surprises by this, I've added input validation for
$origins
to ensure it's only in the new-style format and hopefully avoid exploding in people's faces; nevertheless, since this potentially breaks existing configurations, it should probably be combined with a major version bump.