Red Hat Bugzilla – Bug 658367
[RFE] Provide channel last_modified value via api
Last modified: 2011-01-18 07:16:32 EST
Description of problem:
Provide channel last_modified value via satellite frontend api
call. It may help users f.e. to identify whether are the channel
repodata stale or not.
This issue has been already resolved upstream.
Moving to MODIFIED since the commit is already in #Description.
Changing to VERIFIED:
Compare values against getChannelLastBuildById
Before and after the sync.
Thanks for this, Tomas!
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
This update adds an API call that provides access to the channel last_modified value. This helps users to identify whether the channel repodata are stale or not.
The quality of this erratum should be enhanced, because:
- it mentions an added API call but not the name of the new API call
- it does not mention, that the existing API call channel.software.getDetails was changed and that it now returns an last_modified also
- at least the API documentation should mention this
Hey Stephan, you're right. The erratum text says incorrectly there's a new API call, instead of just enhancing the extended channel.software.getDetails. Sorry for confusion.
But API documentation look good to me.
Return struct of getDetails contains:
Just check /rhn/apidoc/handlers/ChannelSoftwareHandler.jsp#getDetails on your updated satellite.
Thanks, good to know. I didn't think that the local documentation is more recent.
Then it's only missing in the public docs
API Documentation available at rhn/apidoc/index.jsp on your satellite always reflects your available API. (It basically changes with every spacewalk-java erratum.)
Public documentation for RHN Satellite 5.4 available on http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.4/html/API_Overview/index.html describes API of released RHN Satellite 5.4 (so, no errata changes are reflected).