Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-55491

AWS Private key stored as plain text - when using Config as Code plugin

XMLWordPrintable

    • Icon: New Feature New Feature
    • Resolution: Duplicate
    • Icon: Minor Minor
    • ec2-plugin
    • None

      I have been playing about with creating a Jenkins instance from scratch. One of my key criteria is that I should be able to simply redeploy a new Docker container in an environment and quickly get a new setup which closely matches the previous setup (in terms of configuration). To do this I looked at the Config as Code plugin, which works well for my purposes.

      After configuring the EC2 plugin I found that the private key is stored by the ConfigAsCode plugin in plain text - which is bad as I want my config in source control.

      Can you allow the private key to be stored using the Credentials plugin instead (or as well as)?

          [JENKINS-55491] AWS Private key stored as plain text - when using Config as Code plugin

          Tim Brown created issue -
          FABRIZIO MANFREDI made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Jakub Bochenski made changes -
          Link New: This issue duplicates JENKINS-56927 [ JENKINS-56927 ]
          Jakub Bochenski made changes -
          Resolution New: Duplicate [ 3 ]
          Status Original: Open [ 1 ] New: Closed [ 6 ]

            thoulen FABRIZIO MANFREDI
            canuck1987 Tim Brown
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: