@tkopecek do you agree with this proposed change?

Is it really usable for anything? listHosts is listing curren active hosts. Some returned values doesn't even have historical data (ready, task_load, name). But if you've some good usecase, we can do that.

Other calls that return the current values for versioned data generally do not return the current event id. The places where we do are:

• readTaggedBuilds
• maven_tag_archives

These are both relatively complex queries where the event id is relevant to interpreting the data (for tag order).

A few other calls return event ids, but the data is not technically versioned, e.g. getBuild, repoInfo, query_buildroots.

We have a bunch of data that is versioned, but where queries do not return events.

• user perms and groups
• host config and channels
• tag config, inheritance, extra
• target config
• external repo config
• cg users
• tag package listings
• tag groups info

Adding this feature for just hosts would seem inconsistent.

In general, when you care about event ids, you start with the id (e.g. by calling getLastEvent) and then query at the given event.

I don't think this is something we should put energy into right now. However, if we do, we need to consider how to make this consistent across the api. (side note: we'd probably also want to add query-at-event options to a bunch of calls too)