Skip to content
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 regression on agent 5 only #2848

Merged
merged 4 commits into from
Jan 3, 2019
Merged

Fix regression on agent 5 only #2848

merged 4 commits into from
Jan 3, 2019

Conversation

gzussa
Copy link
Contributor

@gzussa gzussa commented Jan 2, 2019

What does this PR do?

This PR reverts changes made in #2488.
This PR introduced regression with Agent 5.
However we still want these changes in for Agent 6.

Motivation

Fix regression with Agent 5
see #2813

Review checklist

  • PR has a meaningful title or PR has the no-changelog label attached
  • Feature or bugfix has tests
  • Git history is clean
  • If PR impacts documentation, docs team has been notified or an issue has been opened on the documentation repo
  • If PR adds a configuration option, it has been added to the configuration file.

Additional Notes

Anything else we should know when reviewing?

@gzussa gzussa requested a review from a team as a code owner January 2, 2019 14:23
olivielpeau
olivielpeau previously approved these changes Jan 3, 2019
Copy link
Member

@olivielpeau olivielpeau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code changes LGTM (CI appears to be failing though, haven't looked at why)

Also, out of curiosity: do you have a way to track the "workarounds"/compatibility fixes that we should drop once Agent 5's regular releases stop?

@gzussa
Copy link
Contributor Author

gzussa commented Jan 3, 2019

Require this #2850 for CI to pass

@gzussa
Copy link
Contributor Author

gzussa commented Jan 3, 2019

Unfortunately, we don't have an automated way to track agent version fork logic.
Hopefully, This is something we have been prohibiting by design (as much as we could) to the exception of logic in datadog_check_* modules which we know about.
That being said this kind of logic is always done using a try... except ImportError: so i guess will just grep for that :)

@ofek
Copy link
Contributor

ofek commented Jan 3, 2019

@olivielpeau Grepping for TODO or FIXME is what I do. I haven't compiled a list yet

@codecov-io
Copy link

codecov-io commented Jan 3, 2019

Codecov Report

Merging #2848 into master will increase coverage by 7.52%.
The diff coverage is 80.95%.

@@            Coverage Diff             @@
##           master    #2848      +/-   ##
==========================================
+ Coverage   85.55%   93.07%   +7.52%     
==========================================
  Files         666       11     -655     
  Lines       37292      578   -36714     
  Branches     4438       69    -4369     
==========================================
- Hits        31904      538   -31366     
+ Misses       4078       30    -4048     
+ Partials     1310       10    -1300

@gzussa gzussa changed the title Revert "Removed deprecated agentConfig option locations" for agent 5 only Fix regression on agent 5 only Jan 3, 2019
Copy link
Contributor

@gmmeyer gmmeyer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@gzussa gzussa merged commit e67fc71 into master Jan 3, 2019
@gzussa gzussa deleted the gzu/disk branch January 4, 2019 18:40
@olivielpeau
Copy link
Member

ok, thanks for the answers! Relying on the TODOs and FIXMEs sounds ok to me as long as we're sure they're there for everything we mean to drop after the last scheduled release of Agent 5 👍

olivielpeau added a commit to DataDog/datadog-agent that referenced this pull request Jul 4, 2019
`device_blacklist_re` has been superseded in v6 since DataDog/integrations-core#2848, but it hadn't been documented here
olivielpeau added a commit to DataDog/datadog-agent that referenced this pull request Jul 5, 2019
`device_blacklist_re` has been superseded in v6 since DataDog/integrations-core#2848, but it hadn't been documented here
@ofek ofek mentioned this pull request Jul 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants