Topics created by zs-dahe

@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

Hi @zs-dahe , The Package Promotion API only be checks for permission against toFeed - you don't need any other permission on the toFeed or fromFeed. As far as more granular permissions, perhaps setting up a Personal Key for like a builds user would do the trick? That'll let you reuse the API Key and set up very granular permissions. We decided not to duplicate that granular permission setting in the API Keys because it's already confusing enough Thanks, Alex

Hi @zs-dahe , Thanks for clarifying, that makes sense; that's not really the use case we intended for asset directory versioning, it was mostly a simple way for asset-directory end-users (i.e. generally not ProGet admins) to fix the occasional delete/accident. It's redundant with back-up, but the idea was that it would save administrator time at the cost of a little disk space. Since it'd be such a large change on our end to rewrite this, it'd be best to wait until there's more demand. Perhaps you could just not use asset versioning , and allow your backup server to handle this? Typically back-up tools will already retain a certain number of past versions of files. Cheers, Alana