Description of problem: There should be API to create, delete, update external repos. As well as associating it to channels. Version-Release number of selected component (if applicable): spacewalk-java-1.2.76-1.el5.noarch How reproducible: Steps to Reproduce: 1. create a repo via API 2. associate repo with a channel via API 3. modify repo via API 4. disassociate repo from channel via API 5. drop repo via API Actual results: no API Expected results: Additional info:
Created commit d84acf1: 647806 - Implement API calls for external repos The following API calls now exist in the channel.software namespace for deailing with external repos (object ContentSource): public List listUserRepos(String sessionKey) { public ContentSource createRepo(String sessionKey, String label, String type, public Integer removeRepo(String sessionKey, Integer id) { public Integer removeRepo(String sessionKey, String label) { public Channel associateRepo(String sessionKey, String chanLabel, String repoLabel) { public Channel disassociateRepo(String sessionKey, String chanLabel, String repoLabel) { public ContentSource updateRepoUrl(String sessionKey, Integer id, String url) { public ContentSource updateRepoUrl(String sessionKey, String label, String url) { public ContentSource updateRepoLabel(String sessionKey, Integer id, String label) { public ContentSource updateRepo(String sessionKey, Integer id, String label, String url) {
Mass-moving to space13.
Thanks Colin for fixing this. API calls are used by spacewalk-common-channels script from spacewalk-utils package.
Verified. # ./spacewalk-common-channels -v -k unlimited -a i386 'centos4*' Then checked in webUI there are centos4 channel and subchannels and appropriate yum repos associated with them.
I don't see commit d84acf1 in our repo. However, if the commit which fixed this bugzilla is in fact 084a791a954f3b77750d642efdeb716960b696b6, then the change is in spacewalk-java-1.2.107-1 and thus in Spacewalk 1.2, and as such we could close it with CURRENTRELEASE. Could someone please confirm if this is true? Jan
This bug has been fixed in Spacewalk 1.3.