Currently when creating a clone the location of the master has to be specified as a URI in the following parameter:
pki_clone_uri=https://master.example.com:8443
Since the hostname has to be specified in the URI, it's not possible to provide a generic example of deployment config for cloning that will work without customization.
Proposed solution: The parameter should be split into separate hostname and port parameters (similar to pki_issuing_ca_uri).
pki_clone_master_hostname=master.example.com pki_clone_master_https_port=8443
The hostname will default to the machine's hostname, that way it can be removed to provide generic example. The code should continue to accept pki_clone_uri for backward compatibility.
Fixed in master: c6d781ee897deb213411f6caba9ae8a1770af732
Metadata Update from @edewata: - Issue assigned to edewata - Issue set to the milestone: 10.2.4
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/1946
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.