Uploaded image for project: 'Puppet Server'
  1. Puppet Server
  2. SERVER-2894

Create `puppetserver ca migrate` command

    XMLWordPrintable

Details

    • Task
    • Status: Resolved
    • Normal
    • Resolution: Done
    • None
    • SERVER 6.15.0, SERVER 7.0.0
    • None
    • None
    • Froyo
    • 2
    • Froyo 2020/10/26, Froyo 11/02/2020
    • New Feature
    • Hide
      Adds a new CLI command, `puppetserver ca migrate` that will move the contents of the CA dir from its current location to `/etc/puppetlabs/puppetserver/ca`. It also creates a symlink at the old location, pointing to the new directory. After running this command, it will be harder to accidentally delete the CA dir as part of cleaning up the client-side ssldir.
      Show
      Adds a new CLI command, `puppetserver ca migrate` that will move the contents of the CA dir from its current location to `/etc/puppetlabs/puppetserver/ca`. It also creates a symlink at the old location, pointing to the new directory. After running this command, it will be harder to accidentally delete the CA dir as part of cleaning up the client-side ssldir.
    • Needs Assessment

    Description

      In order to make it harder for users to delete their CA directories, we want to create a new puppetserver ca CLI command that:

      • moves their CA files to the new location (/etc/puppetlabs/puppetserver/ca) from the current configured location.
      • Creates a symlink from the old location to the new location
      • Errors informatively if the files are already in the new location
      • Does not allow the user to choose the destination.

      This command should be usable in Puppet 6, to help people migrate before upgrade to avoid warnings.

      Attachments

        Issue Links

          Activity

            People

              tony.vu Tony Vu
              maggie Maggie Dreyer
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support