Description of problem: It could be useful if spacewalk-repo-sync can obtain the channel and repository set from a JSON configuration file. { "no_errata":false, "sync_kickstart":false, "quiet":false, "fail":true, "dry_run":false, "channel":{"example_ch":["http://ex.rh.com/repo1","http://ex.rh.com/repo2"],"example_ch_1":[]}, "parent_channel":["example_parent_ch","example_parent_ch_1"] } With using configuration file can be resolved the following RFE as well: Bug 626754 - spacewalk-repo-sync should support multiple "--channel" options at one time https://bugzilla.redhat.com/show_bug.cgi?id=626754
Pull request: https://github.com/spacewalkproject/spacewalk/pull/96
SW commits: 56ce5201df01a0815f8b753aec2f503fbbf38712 c66ce7b84ba5ddca31441c8978ab3d08805f57b3
I have checked that setting urls works for 2 parent and 2 childs. Have not experimented much. Used this config (while some channels did not had repository assigned in webUI): # cat bz1104087.conf { "no_errata": false, "sync_kickstart": false, "fail": true, "dry_run": false, "channel": { "bz1104087-parent1": ["http://yum.spacewalkproject.org/2.4-client/RHEL/6/x86_64/"], "bz1104087-parent1-child1": ["http://yum.spacewalkproject.org/2.5-client/RHEL/6/x86_64/"], "bz1104087-parent1-child2": ["http://yum.spacewalkproject.org/2.6-client/RHEL/6/x86_64/"], "bz1104087-parent2": ["http://yum.spacewalkproject.org/2.0-client/RHEL/6/x86_64/"] } } And used this config with channels which now had the repos configured in webUI: # cat bz1104087-parent.conf { "no_errata": false, "sync_kickstart": false, "fail": true, "dry_run": false, "channel": { "bz1104087-parent1": [], "bz1104087-parent1-child1": [], "bz1104087-parent1-child2": [] }, "parent_channel": ["bz1104087-parent1"] } Tested on Sat with Oracle DB backend with spacewalk-utils-2.5.1-23.el6sat.noarch. During testing this, I have filled bug 1455139. => VERIFIED