-
Notifications
You must be signed in to change notification settings - Fork 225
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
Do not name the RPM repo file differently depending on the Agent version #311
Conversation
Use 'datadog' as a name, to be consistent with other install methods.
9380d4e
to
a2f9e0e
Compare
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, left one small fix proposal for custom repos
tasks/pkg-redhat.yml
Outdated
yum_repository: | ||
name: "ansible_datadog_{{ item }}.repo" | ||
state: absent | ||
with_items: [ 5, 6, 7 ] |
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.
I think we also want to run this with custom
, to remove the custom yum repository (if it exists).
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.
Done and fixed the tests that were failing.
8a8039a
to
f15d50f
Compare
Co-authored-by: Kylian Serrania <[email protected]>
What does this PR do?
Use
datadog.repo
as the name, to be consistent with other install methods.Motivation
We might want the repo file to be installed with the package manager in the future, and we don't want to end up with two of them. I'm still not sure how managing this file with Ansible will interact with the package manager trying to install a newer version of the file (eg: because we added a new GPG key). In case the package manager replaces the file (which I think is not the default behavior, but can be configured that way), Ansible will change it back anyway in the next run 🤷 In any case, that's a problem we will have to solve for all config management tools, so I think this change is still making things better by making all install methods consistent.