As a pulp-admin user, I can set relative-url on the export distributor
Support for relative-url in the export distributor config should come with #1394, but adding support for that to pulp-admin is a little tricky, warranting a brief discussion of the options:
Currently, --relative-url isn't passed into the export distributor config when repos are created or updated. If it was passed into the export distributor, it would probably result in a backward-incompatible change, since it will change the published repo path on the next publish and probably break anything depending on the location of that repo.
Breaking backward compatibility is an option if we want this for 3.0, but the safer option might be to add another flag just for the export distributer to the repo create/update command, e.g. --export-relative-url.
The export run command supports its own config flags as runtime overrides, so --relative-url could be added to only that command, but this is a portentially crappy user experience (Why do I have to set relative-url again?) so again the --export-relative-url might be the flag to use.
Option 4 (my preference):
Some combination of options 1 and 2, and option 3: probably add --export-relative-url to repo create/update and also to export run, maintaining backward compatibility the whole way.
Do nothing. The option is in the docs, leave it to adventurous users to modify the export distributor config via the REST API.
Something I didn't think of.
I think this becomes a relatively easy task once an option is chosen.
#2 Updated by semyers almost 5 years ago
After some consideration, option 3 (only add support for relative-url on the export command) is the winner. There is already precedent for not specifying export distributor options in the repo create/update step, so just adding --relative-url support to the export step, very much the same way that --export-dir does, is a simple option with no backward-incompatibility issues. Option 5 (use the REST interface) also still works really well.
Please register to edit this issue