[Pulp-list] use case: "last modified"

[Dennis Gregorovic]

On Thu, 2013-07-25 at 14:26 -0400, Michael Hrivnak wrote:
> The attributes of an actual unit don't change while the unit is in
> pulp. For example, an RPM might go through multiple iterations of
> being associated with repositories and unassociated, but its own
> attributes will not change. Pulp separates the actual unit from its
> associations to repositories.
Good point.  I could imagine, though, that in the future some content
units may have attributes that change over time.  But we can ignore that
case for now.
> 
> For a specific repository, you can use the following command to match
> units that were added within a time frame:
> 
> $ pulp-admin rpm repo content rpm --help
> 
> We do not expose an API that allows you to search associations for
> multiple repositories at once. You can only do so for one repository
> at a time.

Would you consider exposing an API that allows searching associations
against multiple repositories at a time?  I'm happy to file an RFE. :)

Cheers
-- Dennis

> 
> Michael
> 
> 
> ----- Original Message -----
> From: "Dennis Gregorovic" <dgregor at redhat.com>
> To: pulp-list at redhat.com
> Sent: Thursday, July 25, 2013 1:58:36 PM
> Subject: [Pulp-list] use case: "last modified"
> 
> Hi,
> 
> I have a use case and I'm wondering how to address it in pulp.  I would
> like to get the "last modified" timestamp on a content unit, where "last
> modified" is defined as either 
>  a) the most recent time the content's attributes were modified
>  b) the most recent time the content was associated or removed from a
> repo
> 
> Additionally, I would like to be able to perform queries across repos on
> this data.  For example: "what are all of the RPMs that have been
> modified since July 1, 2013?"
> 
> Is this something that can be accomplished today?
> 
> Cheers
> -- Dennis
> 
> _______________________________________________
> Pulp-list mailing list
> Pulp-list at redhat.com
> https://www.redhat.com/mailman/listinfo/pulp-list