Skip to content

[FEATURE]: Respect runtime option during publish #6997

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

Open
tungi52 opened this issue May 22, 2025 · 2 comments
Open

[FEATURE]: Respect runtime option during publish #6997

tungi52 opened this issue May 22, 2025 · 2 comments
Labels
type:enhancement Improvement to an existing feature

Comments

@tungi52
Copy link

tungi52 commented May 22, 2025

Framework or Library Name

.net8

Library Type

No response

Library Version(s)

3.9.1

Describe the feature you'd like

We use Datadog.Trace.Bundle NuGet package for manual instrumentation because as it stated in the documentation we are in the situation that accessing and updating images add extra complexity and keeping versions in sync is chore.

However using the Bundle package almost double our entire image size: using an ASP.NET Core Alpine image which is less 200 MB (let's say it's 200 with our application and with some additional packages) will be extended with addional 170 MB Datadog binaries. And in production only a few of them are required - the ones under the linux-musl-x64 and net6.0 folders (in our case).

Is it possible or even planned to respect the --runtime property during pusblish and only copy relevant files to the output?
Thanks!

Is your feature request related to a problem?

No response

Describe alternatives you've considered

No response

Additional context

No response

@tungi52 tungi52 added the type:enhancement Improvement to an existing feature label May 22, 2025
@andrewlock
Copy link
Member

Is it possible or even planned to respect the --runtime property during pusblish and only copy relevant files to the output?

Thanks for raising this! The short answer is yes, we're currently looking into exactly this 🙂 We don't have an eta, but @lucaspimentel has an outline of a solution, we just need to evaluate this further and make it more robust before shipping it.

@lucaspimentel
Copy link
Member

Here's a draft PR: #6923

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement Improvement to an existing feature
Projects
None yet
Development

No branches or pull requests

3 participants