Proget: setting metadata cache to true not reflected in UI

[stefan.hakansson_8938]

Hi,

I did pgutil connectors properties set --connector=myconnector --property=metadataCacheEnabled --value=true, and when then doing pgutil connectors properties list --connector=myconnector it says metadataCacheEnabled=true.

However, it is still said being disabled in the Web UI.

Br,
Stefan

[stevedennis]

Hi @stefan-hakansson_8938 ,

I cannot reproduce this in ProGet 2025 - the value is set and displayed correctly, as expected.

Both the UI and API use the same code to retreive/load information from the database, and there is no data caching here, so I'm thinking there might be some other issue (looking at wrong instance, looking at wrong connector, etc).

Thanks,
Steve

[stefan.hakansson_8938]

Hi @stevedennis, thank you for looking into this.

I was on ProGet 2025.1 Build 5, and just upgraded to ProGet 2025.2 Build 15

$ ./pgutil health
Checking https://packages.prod.antura.cloud/...all OK
Version: 2025.2 (Build 15) (2025.2 (Build 15))

Database: OK
License:  OK
Service:  OK
$ ./pgutil connectors properties list --connector="noble updates"
url=https://archive.ubuntu.com/ubuntu/
feedType=debian
timeout=60
metadataCacheEnabled=true
metadataCacheCount=100
metadataCacheMinutes=30

while the Web UI looks like

I will be away for a few weeks now but will investigate more when I'm back, I just wanted to upload the info I have now.

Best regards,
Stefan

[stevedennis]

@stefan-hakansson_8938 thanks for confirming, I see what's happening

Debian feeds do not use metadata caching (they have a local index file instead), so it's not settable and is always displayed as "disabled" in the ProGet UI. If you were to go to the connector page, you won't be able to set it. HOWEVER, it's settable using the API.

[stefan.hakansson_8938]

Thank you @stevedennis, this makes sense.

One odd thing is that I noted that when I had set metadatacache=true using pgutil, the time the WebUI showed Loading Packages.... and the time it took to do sudo apt update in clients went from long to super long. It went back to long when I set metadatacache=false again. I don't know if there is a logical explanation for this or of it was just a coincidence.

Br,
Stefan