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

nuget.config source filtering by namespace #7007

Closed
flcdrg opened this issue Jun 8, 2018 · 2 comments
Closed

nuget.config source filtering by namespace #7007

flcdrg opened this issue Jun 8, 2018 · 2 comments
Labels
Area:Settings NuGet.Config and related issues Functionality:Restore Resolution:Duplicate This issue appears to be a Duplicate of another issue Triage:NeedsTriageDiscussion Type:Feature
Milestone

Comments

@flcdrg
Copy link

flcdrg commented Jun 8, 2018

I think it could be useful if you can specify for a particular source in nuget.config, what namespaces/names of packages should be queried for that source.

That way, if you had an internal NuGet source as well as the public nuget.org source, you could configure NuGet not to bother querying nuget.org for your internal packages.

eg. something like:

<configuration>
  <activePackageSource>
    <add key="All" value="(Aggregate source)" />
  </activePackageSource>
  <packageSources>
    <add key="TeamCity" value="http://build.local:8111/guestAuth/app/nuget/v1/FeedService.svc/" />
    <add key="MyGet Feed" value="https://www.myget.org/F/example/api/v3/index.json" />
    <add key="nuget.org" value="https://api.nuget.org/v3/index.json" />
  </packageSources>
  <filters>
    <add key="TeamCity" value="MyPackages.*" />
  </filters>
</configuration>

With the above configuration, when NuGet was asked to restore a package named "MyPackages.Blah", it would only query the TeamCity source

@nkolev92
Copy link
Member

//cc @anangaur
A request for similar to the original lineups idea.

@nkolev92 nkolev92 added this to the Backlog milestone Jun 11, 2018
@nkolev92 nkolev92 added the Resolution:Duplicate This issue appears to be a Duplicate of another issue label Jul 24, 2020
@nkolev92
Copy link
Member

Hey @flcdrg,

Thanks for creating this issue.
Given that it's been a while since this issue has been created and we haven't gotten a lot of additional enagement, I will merge this issue to #6867.

The ask there is similar. The ability to define which package source a package should come from.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area:Settings NuGet.Config and related issues Functionality:Restore Resolution:Duplicate This issue appears to be a Duplicate of another issue Triage:NeedsTriageDiscussion Type:Feature
Projects
None yet
Development

No branches or pull requests

3 participants