(fleet) split installation and instrumentation for dotnet tracer oci #35152
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bmermet
added
changelog/no-changelog
qa/done
raphaelgavache
approved these changes
Mar 17, 2025
Contributor
Author
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
arbll
pushed a commit
that referenced
this pull request
Mar 19, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
This PR aligns the installer with the changes in DataDog/dd-trace-dotnet#6766 to split the installation command of the dotnet library OCI in two. One for installation and one for instrumentation. This will make it easier in the future to make versions of the tracer that can be installed without automatically injecting into IIS apps if needed.
Motivation
More flexibility in using the dotnet library OCI.
Describe how you validated your changes
This is covered by E2E tests.
Possible Drawbacks / Trade-offs
Additional Notes