This document covers using conf files for the spacewalk-merge-by-date command, and using them automates the tedium of channel lifecycle management

https://access.redhat.com/sites/default/files/attachments/red_hat_satellite-5.6-satellite_errata_management-en-us.pdf

Check out using conf files:

{
 "username": "<username>",
 "password": "<passworD>",
 "assumeyes": true,
 "skip_depsolve": false,
 "security_only": false,
 "blacklist": {
 "ALL": ["tomcat.*","java.*","apache-tomcat.*"]
 },
 "removelist": {
 "ALL": ["tomcat.*","java.*","apache-tomcat.*"]
 },
 "channels": {
 "rhel-x86_64-server-6": "test-rhel6-x86_64-server",
 "rhn-tools-rhel-x86_64-server-6": "test-tools-rhel6"
 }
}


-------- Original Message --------
Subject: [Spacewalk-list] Content Merge - Child Channels
From: Alexander Dacre <[email protected]>
Date: Thu, July 17, 2014 6:26 am
To: "[email protected]" <[email protected]>

Hi all,
 
I’m working through a Spacewalk installation to push content between environments: dev -> qa -> prod.
 
The planning is to keep development up to date and periodically merge the content to qa and then onto prod.
 
Merging the content for the base channel is fine, but is there a way to include the child channels in one operation?
 
Thanks,
Alex

_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list
_______________________________________________
Spacewalk-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/spacewalk-list

Reply via email to