Hi @michal-roszak_0767, Ah, that must have been an oversight; trivial change but best we don't change it until ProGet 2025. I think you can use maven2 as the type for now, it's the internal identifier. Later on, we will make it maven and mavenlegacy Thanks, Alana

@atripp Done: https://forums.inedo.com/topic/5347/feature-request-feed-other-settings-editor Michal

Hi @michal-roszak_0767 , This is a third-party / community plugin and we have no plans to maintain it ourselves. I hear it still works, but is a bit outdated. HOWEVER, the former owner very recently "handed it over" to another community member. So this may mean we'll see some "new life" or changes -- I think they're still figuring out how to actually publish a new version, or something like that: https://github.com/jenkinsci/inedo-proget-plugin Thanks, Alana

@zs-dahe said in Retention Activation via API?: with the Feeds API it is possible to add retention rules for feeds (https://docs.inedo.com/docs/proget/administration/retention-rules). However, I don't see a possibility to actually activate the retention for a specific feed via the API. Am I missing something or is the retention intended to be activated only via the web UI? Our usecase is that we would like to activate a specific set of rules to many feeds at once. For this, we must also ensure that the retention is actually activated and an API endpoint would be convenient to enforce this. Hi Alana, thanks for the quick reply. I opened a feature reqeust ticket for this :) Best regards Daniel

Awesome! Thanks so much for the quick response.

Hi @rhessinger , i have followed your configuration and i have managed to download the docker. to tell you the truth, i do not know what has changed because the only thing that i have changed is the checkbox next to "library/..." and i have played with this prior to opening this case. thank you very much.

Hi @mmaharjan_0067 , The pgutil assets list command is intended for interactive use and should not be parsed; it could change in future versions. Instead, you can just call the endpoint directly, which will contain the details you're looking for: https://docs.inedo.com/docs/proget/api/assets/folders/list Cheers, Alana

Hi @v-makkenze_6348, Glad to hear it! Thanks, Rich

Thank you so much!

Hi Alana, This seems to work for what I am trying to accomplish. Thanks! Scott

Hi @parthu-reddy , If you can provide my with some step-by-step instructions (reproduction case), then I can see if if there's a bug in ProGet. However we can't really change the "license file is embedded in the package file" technical requirement. That said... using custom licenses for blocking package is definitely inappropriate. Please do not do that. It will cause you headaches and probably business disruptions later. There are already tools to prevent users from downloading packages from ProGet, this is not how you want to do it. The easiest solution here is to align the security team's understanding/expectations align with reality. You don't want to try to configure ProGet in unrealistic ways that will lead to actual problems/risks. I suspect the security team is conflating "vulnerable packages" with "malware and viruses", so it'd be best to take this opportunity to educate them on how packages / ProGet works. ProGet can prevent users from downloading certain packages, but vulnerable packages are freely available on the internet for download. A vulnerable package is NOT some a "virus in a lab that can escape" and infect a system A package is just a library and cannot run on its own If a user has a copy of vulnerable package, they can't use it to "hack" a system with it nor will it cause any harm Vulnerable packages simply shouldn't be used as building blocks in your own applications Thanks, Alana

Hi @parthu-reddy , This hasn't changed; to "Set Package Status", you need to first Pull the Package to the feed. From there, you can a compliance rule override of Always Block or Always Allow Downloads. Thanks, Alana

Hi @caterina, I'm sorry about this. There looks like there was a conflict with another notifier change. I have created a new ticket, PG-2933, to fix this and it will be released in the next maintenance release. Thanks, Dan

Hi @arose_5538, We just released ProGet 24.0.31 that has the fix included for this so you do not need to specify those extra environment variables. Thanks, Rich

Hi @pratik-kumar_8939 , Unfortunately Nexus has a very limited API, which is why the so the import isn't working (404 error - not found). Basically, it doesn't implement the "catalog API" that allows all artifacts/packages to be listed. However, you can use a file-system / drop-path import after you extract the files from Nexus Thanks, Alana

Hi @v-makkenze_6348 , This error was related to an error on our end - basically there was some bad data in the package that the InedoHub downloaded, and it caused the installer script to crash. We fixed the package on our end, so reinstalling normally should work now. Cheers, Steve

Awesome, thank you so much!

Thank you for your guidance Dean!

Thanks ! Works as expected... as always :)