Skip to content

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

Closed
cdenneen opened this issue Oct 19, 2022 · 4 comments
Closed

Backup/Restore CA #306

cdenneen opened this issue Oct 19, 2022 · 4 comments
Labels

Comments

@cdenneen
Copy link
Contributor

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.

  1. Backup CA
  2. Restore CA
@mcka1n
Copy link
Contributor

mcka1n commented Oct 20, 2022

Hey @cdenneen

The Backup and Restore plans already do this, but it's not been thoroughly tested.

Also the puppet-backup create command does that..

We created an internal ticket to properly test the PEAM backup/restore plans

@cdenneen
Copy link
Contributor Author

cdenneen commented Oct 20, 2022 via email

@mcka1n
Copy link
Contributor

mcka1n commented Oct 27, 2022

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 puppet-backup create ... --scope = certs and in the Puppet docs, we have listed that the certs scope is doing the backup for this directory: /etc/puppetlabs/puppet/ssl/

https://puppet.com/docs/pe/2019.8/backing_up_and_restoring_pe.html#directories-data-backed-up

@ragingra
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants