Rename conflicting send_payload
method
#2673
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Move a generically named method out of the way.
Motivation
The transport infrastructure is mostly generic, except for a few choke points. This addresses one of them.
The
send_payload
method, while defined in a trace-specific module, is included at the class level.When attempting to reuse transport for other use cases, the method conflicts with other modules extending the generic client class.
Luckily its use is very limited and self-contained to a trace transport specific scope. By renaming it additional modules are able to be included and can follow a consistent pattern without conflict.
Additional Notes
This has been discovered while implementing additional transport facilities for remote configuration, from an AppSec impetus.
The whole transport code is fairly involved and due for a rewrite, nonetheless it handles many corner cases. which would make a drop-in rewrite carry much risk to tracing.
Therefore a more segregated approach is being taken to implement the required additional transports, aiming:
This is one of those changes.
How to test the change?
CI should be green.