-
Notifications
You must be signed in to change notification settings - Fork 372
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
ekump/decouple core transport #3150
Conversation
121d9c1
to
1314404
Compare
c3f5bb3
to
7a186e3
Compare
…ansport::parcel to core
7a186e3
to
caecc2c
Compare
@@ -32,12 +32,6 @@ Lint/MissingSuper: | |||
- 'lib/datadog/profiling/pprof/converter.rb' |
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.
Nice cleanup!
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.
Awesome work, @ekump!
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.
nice, I will migrate to use Net::HTTP adapter from Core for agentless mode as soon as it gets merged
# Below should be: | ||
# require_relative '../../transport/http/api' |
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.
Is this comment relevant?
# Below should be: | ||
# require_relative '../../transport/http/builder' |
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.
Is this comment relevant?
# Below should be: | ||
# require_relative '../../../../ddtrace/transport/http/api/spec' |
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.
Is this comment relevant? And any other comment that state what the actual require should look like 😄
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.
These comments were already in place. I just updated them to reflect this PR's changes. If we think they're superfluous, I'm happy to remove them.
Amazing work @ekump 🎉 I wondered if you explored avoiding the duplicated portions of |
@GustavoCaso - I think there is a fair amount of interest from everyone to a) simplify transport and b) do what we can to reduce the duplicate code between remote and tracing. But, the scope of this PR was just decoupling. I'm hoping we'll be able to revisit the transport code sooner, rather than later to give it more attention. |
What does this PR do?
Properly namespace the various transport modules to aid in decoupling Tracing from Core. There should be no functional changes.
Datadog::Transport
(ddtrace/transport) was primarily used by Tracing so it has been moved toDatadog::Tracing::Transport
. The exception to this is the ext file which is a public API. We should discuss moving this in 2.0 (should be relatively easy).Datadog::Core::Transport
was only used byDatadog::Core::Remote
. It has been moved toDatadog::Core::Remote::Transport
.Files common to both Remote and Tracing were moved to
Datadog::Core::Transport
.Motivation:
Decouple Tracing from Core
Additional Notes:
The scope of this PR is primarily decoupling. There is probably a fair amount of work that can be done to simplify the transport code in general, but that can be done separately.
How to test the change?
For Datadog employees:
credentials of any kind, I've requested a review from
@DataDog/security-design-and-guidance
.Unsure? Have a question? Request a review!