This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      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)?

            Assignee:
            FABRIZIO MANFREDI
            Reporter:
            Tim Brown
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: