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!
Status of feed independent delete API
-
This is a follow up to https://forums.inedo.com/post/13488 but I am wondering about the mentioned "API that would work across all package types" for package deletion. Is this feature still being planned for ProGet 2023?
What I'm after is a retention policy of "last X builds of each version" which doesn't seem possible with the current combinations and so one idea I had was to script the deletion from the outside using this REST API like I do now for NuGet (need to do it for maven too).
The other idea I had was making retentions rules have a scripting option (something like passing in the artifact ID and list of versions, and returning either a list of versions to keep or versions to delete, whichever is easier to implement) but that would be a new feature request that may not provide a lot of benefit for users other than us.
-
Hi @jim-borden_4965 !
I think that the "delete old versions" option of Retention Rules might be what you're looking for; that will let you keep the last "X" versions of each package. That, in combination with "unused versions" (i.e. not recently downloaded) typically cover nearly all desired retentions.
As far as a "feed independent" API, that's on our list as a "nice to have", and I don't know how much of an API we'll get in the first version of ProGet 2023. The "hard part" is usually specifications/docs, so if you have any ideas we'd be very open!
Currently, our idea is base it off of the upack api:
https://docs.inedo.com/docs/upack-feed-api-endpointsSome things will be more difficult (or impossible?) than others. Especially for multi-platform package types like ruby, python. But TBD.
Cheers,
Alana
