Description of problem: Upon running the installer to add a new destination for pulp exports an additional step of setting the pulpcore_export_destination Setting via hammer or the WebUI must be set in order to use the new export path. This request is to update this setting value to the new value upon a successful completion of running the installer with this option. Version-Release number of selected component (if applicable): How reproducible: Every time Steps to Reproduce: 1. Run the installer with the '--foreman-proxy-content-pulpcore-additional-export-paths' option to specify a new export location. 2. Try to export and watch it export to the previously set location 3. Update the setting 'pulpcore_export_destination' to the new location and export again. 4. Export will export to the new location Actual results: Pulp will export to the previously set location listed in the Satellite settings Expected results: Use 1 action to change the export location to simplify workflow Additional info: This RFE comes from bugs previously filed: https://bugzilla.redhat.com/show_bug.cgi?id=2208013 https://bugzilla.redhat.com/show_bug.cgi?id=2158186 https://access.redhat.com/solutions/7013903
A Bugzilla for the documentation has also been opened to add the current procedure to the documentation. Should the result of this RFE be implemented, please reopen Bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=2217528 to have the procedure updated.
+1 The less confusion we create, the better the user experience would be. If What Taft requested is not possible to implement for any reason then , My alternate proposal is * Have the installer executed by the end-user to allow a new location as the export_path * As far as the setting pulpcore_export_destination goes, at the backend * It should somehow read the pulp config and get all the allowed export_paths * List then as selectable options In that way, some manual errors due to typo ( as the value of pulpcore_export_destination ) can be avoided