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

Just to let you know - the PR has been merged and we'll release AWS 3.1.2 on Friday with the fix included. Thank you!

Hi @michal-roszak_0767 , Just as an update, we've added this to our roadmap planning for ProGet 2026. We will begin that process later this year, after ProGet 2025 has been released (see road to ProGet 2025). Cheers, Alana

Hi @carsten_1879 , Can you try using buildmaster:24.0.5 instead of latest? There was a change in the Git library, and I'm wondering if this is a kind of regression on some platforms. Thanks , Alana

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

Hi @si-peham_2672, As far as I can tell, it looks like there is still a permission issue with the working directory that is preventing file listing. The workaround to use the --input argument seems to get past that issue, so I would continue to use that. For your reference, I did test this locally and on a test server, and both worked without issue. If you are interested, here is a link to our code that is searching for the file (https://github.com/Inedo/pgutil/blob/5001174a4c786bb238e8546d18d82fed71cfcc58/Inedo.ProGet/Scan/DependencyScanner.cs#L114). The SourceFileSystem.Default.FindFilesAsync just calls new DirectoryInfo(folder).EnumerateFiles and then matches against the name. For the Specified argument was out of the range of valid values error, that will be resolved in ProGet 2024.33, which will be released this Friday. If you have any other questions, please let us know. Thanks, Dan

Hi @guilherme-silva_2532, The warnings in the blob layer scanner are to be expected in most images. Not every layer includes a file system. The layer scanner scans each layer for an application database. This will vary from layer to layer. There was also a bug released in ProGet 2024.32 that was not recording certain layer scanner results properly. This will be fixed in PG-2943 and will be released in the maintenance release this Friday. This may be why you are not seeing any packages found in this container. Thanks, Dan

@michal-roszak_0767 currently maven2 is a workaround, so it will continue to warm. In ProGet 2025, Maven will create the expected feed type.

Hi @michal-roszak_0767, This is what I meant by the Security API -- a combination of HTTP Endpoints and pgutil commands. We will consider them for our ProGet 2026 roadmap. So until then you'll need to use the Native API; At this time the Native API is the option. You can also check out @steviecoaster 's PowerShell module, which has some modules that can help https://github.com/steviecoaster/InedoOps Thanks, Alana

@rhessinger Cool, thanks for the information. April 18th is great.

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!