While syncing packages from one satellite to another if valuable, having to move back and forth content views and other system content meta data makes the current feature set unscalable. The purpose of this request is to allow content views and other valuable data to be inter satellite synced between installations. In this use case, the DEV and Prod environments are strictly separated which necessitates having multiple installations of Satellite 6. (One for DEV and one for PROD) one tens of thousands of systems are managed, having to manually (by hand or with scripts) export content views from one satellite only to import into another generates a large overhead in the amount of work needed for the workflow to be complete.
Thank you for the bugzilla report. This appears to be a duplicate of bug 1269273; therefore, I am going to mark it as duplicate. If that is not the case, please feel free to re-open with the appropriate details. *** This bug has been marked as a duplicate of bug 1269273 ***