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

apt, yum, etc. providers should deal more gracefully with expired GPG keys

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Types and Providers
    • Labels:
      None
    • Template:
    • QA Risk Assessment:
      Needs Assessment

      Description

      The problem described at:
      https://puppet.com/blog/updated-puppet-gpg-signing-key
      affects a lot of other packages as well.

      It looks like the (optional) apt_key module does deal with this somewhat here:
      https://github.com/puppetlabs/puppetlabs-apt/blob/master/lib/puppet/provider/apt_key/apt_key.rb#L47-L49

      It seems to me that it would be ideal if Puppet can handle this scenario more gracefully; it's not practical for third party modules to try and add workaround functionality on a case-by-case basis, and asking users to always add site code to deal with this also doesn't seem like a good solution.

      Let me know if this should be categorized differently.

        Attachments

          Activity

            jsd-sla-details-panel

              People

              • Assignee:
                Unassigned
                Reporter:
                will47 William Yardley
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: