Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
ProGet: nuget.org connector still using v2 after upgrade to 5.3.x and changing to v3 url
-
Hi,
We have just upgraded to 5.3.11, hoping to be able to avoid "429 Too Many Requests" responses from nuget.org by moving to use their v3 api. However, we are still getting these errors despite having only a single connector to nuget.org and that being configured with the v3 url. In addition, the upgrade notes (https://inedo.com/support/kb/1767/proget-5-3-upgrade-notes#nuget-v3-api) state that ProGet will use v3 regardless of what is configured. This doesn't appear to be the case for us.
We do have clients connecting to our local ProGet feeds using the ODATA format/urls. Does that make the connector use the same onto nuget.org?
Thanks in advance.
Mike.
-
ProGet will use the v3 (JSON-LD) API when possible, but not all v2 (ODATA) queries can be "translated" to the v3 (JSON-LD) API, and thus they need to be forwarded to the v2 (ODATA) end-point.
ODATA is a general-purpose querying API (like SQL but for the web), so clients do a lot with it (sorting, etc.). The v3 (JSON-LD) API is much more limited. So I recommend you to update the clients.
-
@atripp Hi, thanks for your reply. Understood. I'll start with getting the clients to use the v3 endpoint to the local feeds. Hopefully then things will stay in the v3 world.
-
@atripp
Alternatively, is there a way to stop outbound requests being made to a nuget.org connector? For example, there is no point asking nuget.org for packages that we host on our own internal feeds.Thanks,
Mike.
-
For this, you could just disable the connector, and use a Promoted-package workflow, where you manually promote approved packages from one feed (Unapproved) to another feed (Approved).
When the request is very simple, like "give me this exact version of this exact package", then it's not forwarded. But typically the request is, "what's the latest version of this package". Of course, that must be forwarded and aggregated against all connectors.
Why the client makes such a request in some cases is a mystery, but that's why they rewrote everything from scratch into a new, v3 api.
