Topics created by pmsensi

Hi @pmsensi , You'd need to run through a proxy like Fiddler or ProxyMan, which can capture the outbound / inbound traffic. Or if you provide us with a URL/API key we might be able to play around and attach a debugger. You could always create a free trial or something and set it up that way. First thing that comes to mind is that your endpoint is incorrect and you may need to "play around" with the URL. Typically it's like this: endpoint is https://server.corp/path/my-pypi index file is https://server.corp/path/my-pypi/simple ProGet automatically appends /simple unless you specify otherwise on Advanced The "Simple " endpoint is just a list of HTML like <a href="...">. That's what ProGet/connectors/pypi follow. Thanks, Steve

Hi @pmsensi , Can you take a look at this thread? https://forums.inedo.com/topic/5493/request-for-creation-of-api-for-package-auditing-before-dependency-restoration/7 I believe that new API proposal ( pgutil packages metadata) would contain that information -- please share your thoughts in that thread so we can keep it in one place. Thanks, Steve

Hi @pmsensi , Thanks for the heads-up; looks like there was a replication issue with one of our edge nodes. It should be there now Thanks, Alana

Hi @pmsensi , Short of using the Native API, I'm afraid we don't have a first-class API to export/import package policies and their related information We may consider adding that after ProGet 2025 is released. Thanks, Steve

Hi @pmsensi , The pgutil builds audit command should show the same license information you see in the UI: https://docs.inedo.com/docs/proget/api/sca/builds/analyze The pgutil packages audit command should also provide similar information on a package level. Is that's what you're looking for? Thanks, Steve

Hello @atripp , Thank you for your help. We have an intermediate certificate (proxy), which I think, as you point out, can be the problem. I will clarify with our IT department. Anyway, after reading a little bit more, there is a variable to force Kaniko to use HTTP/1.1. variables: GODEBUG: "http2client=0" After adding that, everything works :) Thank you! Best Regards, Pedro

@rhessinger I added the requested info to the opened ticket. Best Regards, Pedro

If you're looking for nuget.org-specific metadata, I recommend querying nuget.org directly; of course if you need to work-around internet access issues, you could configure a special feed/connector with no caching. But if you're looking for latest version of a package, the registration API is your best choice. That's what Visual Studio (NuGet client) does for every package and dependency, every time a restore happens.

Hi @apxltd, thanks for the insights! I half expected this to be way more complicated than I had hoped for, but one can dream...