[FR] Support for automated/mass-registration with livepatch server

[Andrew Pineiro]

[Description]

One of our customers is going through the process of getting Livepatch On-Premises deployed in their environment, and are looking into how they will be enabling their clients. Currently there are thousands of machines that would need to be enabled and registered with the livepatch server, and it would prove quite inconvenient to follow the steps listed on the Client Configuration docs[0] (config remote-server, and then enable) for each of those clients (even some scripted automation between all the different environments/network would take some time).

This LP bug is being opened to request support for a way to perform automated registrations (pre-seeding a livepatch-client config file with a token and remote?) of clients as soon as the snap is installed.

[Workarounds]

The current workaround would be to use some external automation via scripting or some other method to install the snap, run the config command, and then run the enable command with the secret token. In a large customer's environment with several jumpboxes and time-gated access this is a sub-optimal solution.

Let me know if any further information is needed. Thanks!

[0] - https://ubuntu.com/security/livepatch/docs/on_prem/client