Make bundle deploy operation analogous to unix cp command: cp <what to copy> <destination> Current design forces user to create a destination for each deploy operation. Use case: Bundle superuser - Upload bundles - Create one or more Destinations. Destination means possible targets, locations. Deploy-only user - Select a bundle and a destination to deploy Version-Release number of selected component (if applicable): JON 3.2
Moving to unspecified target milestone as only JON 3.2.0 'blockers'(https://url.corp.redhat.com/bz-jon32-blockers-list-notmodified-nodocs) will make it into subsequent builds after ER5.
There is no plan to do this. Closing this one.