-
Notifications
You must be signed in to change notification settings - Fork 54
Backup/Restore CA #306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hey @cdenneen The Backup and Restore plans already do this, but it's not been thoroughly tested. Also the We created an internal ticket to properly test the PEAM backup/restore plans |
@mcka1n I don’t see in the task it backing up the SSL for the CA. Can you show me
where?
|
Sure thing, this is the line in the Backup plan for CA: https://github.com/puppetlabs/puppetlabs-peadm/blob/main/plans/backup.pp#L76 And it is running the https://puppet.com/docs/pe/2019.8/backing_up_and_restoring_pe.html#directories-data-backed-up |
I Split the backup CA part of the above to allow this to be done in the meantime. #400 There is more thorough testing going on for the full backup restore functionality at the moment and will probably replace the CA specific one in due course. Will Close the issue as it can be done via either of these two routes. |
Backup CA to be copied to newly provisioned infrastructure.
Saving all the certificates (agents, etc) to be re-used rather than having to re-provision those.
The text was updated successfully, but these errors were encountered: