Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-8918

Finalize separation of CA from Ruby

    XMLWordPrintable

Details

    • Epic
    • Status: Closed
    • Normal
    • Resolution: Incomplete
    • None
    • None
    • None
    • None
    • Separate CA from Ruby
    • Froyo
    • Needs Assessment

    Description

      This epic contains the work for removing the CA's last ties to Ruby Puppet. This includes moving settings from Puppet into Puppetserver and moving the CA directory under puppetserver's file tree instead of puppet/ssl. We plan to provide a path for doing this in the Puppet 6 series and move the directories and settings by default in Puppet 7.

      Attachments

        Issue Links

          is duplicated by

          Improvement - An improvement or enhancement to an existing feature or task. PUP-3262 By default, the cadir should be separated from the ssldir

          • Critical - Crashes, loss of data, severe memory leak.
          • Closed
          relates to

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SERVER-2975 CA without JRuby

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. PUP-8965 Change dns-alt-names option to subject-alt-names

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Improvement - An improvement or enhancement to an existing feature or task. PUP-9156 Add a `puppet ssl clean` command that will clean up all cert artifacts on an agent

          • Normal - Regular issue, some loss of functionality under specific circumstances.
          • Closed

          Activity

            People

              Unassigned Unassigned
              maggie Maggie Dreyer
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support