👋 On Fri, 30 Dec 2022 at 22:00, Seth David Schoen <[email protected]> wrote: > The documentation doesn't specifically mention how to upgrade; can I > assume that making a new .deb from current sources, and then installing > that with dpkg on a machine where an older .deb is installed, will > maintain the credentials and identity of my existing probe? It won't > wipe everything out and require me to re-register as a new software > probe, right?
Compile the updated version from source as per usual and install the application from the DEB package. Take note of the SSH key. https://atlas.ripe.net/docs/howtos/software-probes.html Found in /var/atlas-probe/etc The probe identifies itself using the SSH key. Unless the key is regenerated during the upgrade. The probe will continue to chug along. :) *If* the SSH key is regenerated. You can always go to the RIPE Atlas Portal. Log in to manage your probe. And update the probe with the new ssh public key. = No need to register a new one. Either backup up the SSH key, or update the probe settings with the new ssh public key -- ripe-atlas mailing list [email protected] https://lists.ripe.net/mailman/listinfo/ripe-atlas
