-
Notifications
You must be signed in to change notification settings - Fork 222
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
Add includepkgs to repo config #443
Conversation
Hey @sspans-sbp thanks for your contribution, could you make sure the CI tests pass? It seems like they are failing on downgrades |
Includepkgs doesn't use the epoch for matching, I've added a jinja filter to strip it from the version string. |
It seems this feature is also supported by zypper, so it makes sense to add it for SuSE as well. |
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.
LGTM, but I want @bkabrda to have a look too
Any progress on the review? |
Hey, my teammate is out of office, so you will have to wait a few more days until he is back (I will remind him, no worries :)) |
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.
Thanks for opening the PR. Overall I think this is a good thing to do, however as noted inline, I can't get the SUSE part to work (I don't think this actually works with zypper). Once we get that sorted out, I can merge.
I've removed the SuSE bits, please review. |
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.
LGTM, merging. Thanks for the PR!
As a side note, for a while I was deliberating about the fact that some people might actually expect to be able to do plain That said, this new behavior should be documented clearly and explicitly in the release notes for the next release so that users are well informed of its consequences. |
The current repository configuration is unrestricted. Users / patch tooling running the standard
yum update
command will deploy the latest datadog agent. The recommended configuration of the role is to specify an explicit version, resulting in unfortunate upgrade/downgrade actions.This PR adds the versioned package as
includepkgs
to the repository configuration.This ensures that only the configured version can be installed by yum / dnf.