Update Certificate for a Pulp Remote

Support
#1

Problem:
I am syncing some RHEL repos that use certificate to authenticate, these repos are configured with auto publish and sync task runs everyday. During Remote creation we supplied cert and key from local file in pulp server. However, sometimes that certificate changes or expires, can I use API to update Remote certificate/key without removing it? and if so, do I need to restart pulp services after change? or change is effective immediately after certificate update?

Plan is to use PATCH method with endpoint:
/pulp/api/v3/remotes/rpm/rpm/{pulp_id}/

and supply client_cert and client_key.

Expected outcome:

Pulpcore version:
“core”: “3.48.0”
Pulp plugins installed and their versions:
“versions”: {
“rpm”: “3.25.1”,
“core”: “3.48.0”,
“file”: “3.48.0”,
“certguard”: “3.48.0”
},
Operating system - distribution and version:
RHEL 9
Other relevant data:

#2

Yes, calling PATCH on a remote pulp_href will update the remote with the new fields you supply. The change will schedule a task to peform the update, requiring an exclusive lock on the remote. This means that if you schedule multiple syncs with that remote and then perform an update on the remote, the update will only occur after all the syncs have completed. After the update all future syncs will use the new remote values, there is no need to restart any Pulp services.

1 Like