Is it possible to change the Published at URL displayed in the Products repository page

Problem: Currently, the displayed URL is http://server.name01.domain.local/pulp/repos/OrganizationName/Library/custom/CentOS7-Base/CentOS7-Base/ I want it to be due to host naming structure in our infrastructure I can’t rename the machine to the domain since most of our automation in an external puppet server is done through hostnames. I have tried installing katello with the following to no avail:
foreman-installer --scenario katello --foreman-ssl=true --foreman-foreman-url --foreman-unattended-url= --no-enable-puppet --foreman-proxy-puppet false --foreman-proxy-puppetca false --foreman-proxy-content-puppet false --certs-ca-common-name --certs-cname --foreman-proxy-foreman-base-url --foreman-proxy-plugin-pulp-pulp-url --foreman-proxy-plugin-pulp-pulpcore-content-url --foreman-proxy-plugin-pulp-listen-on https --enable-foreman-plugin-remote-execution --enable-foreman-proxy-plugin-remote-execution-ssh

Expected outcome: Reach yum repositories at

Foreman and Proxy versions: 2.0

Foreman and Proxy plugin versions: 2.0 and katello 3.15

Distribution and version: CentOS 7

Other relevant data: None as far as I can tell

The Published At base URL comes from the URL that Katello uses to talk to Pulp. Currently there is no way to change this, but it’s possible to request this as a new feature.

Thank you for the heads up, I actually found this post which seems that it could be helpful

Specially the section where I can set the url i’d like to use subscription-manager register --org="OrgName" --activationkey="CentOS7-Base" serverurl= --baseurl=

@rivermigue hmm, I think that would set the URL that the host uses to get content. But it wouldn’t actually move anything or affect the Published At URL of a repo.

If you file an RFE I would file it for Katello and not subscription-manager.

Yeah, this approach wont work mainly because katello generates a bunch on self signed certificates and will cause the connections between endpoints to stop working due to the different certificates. So, in that case, is there a way to use a proper certificate just for the katello endpoint instead of using the one generated by katello using the server’s name?
Changing the server’s name from server1.domain.local to wont be possible since most of our puppet automation relies on server hostnames