Jira (BOLT-116) Consider the contents and format of a possible bolt.conf

[Nathan Shobe (JIRA)]

Title: Message Title

Nathan Shobe commented on BOLT-116   Re: Consider the contents and format of a possible bolt.conf My perference would be for the conf file to be in a yaml hash, and also allow eyaml integration. This would allow the conf to live in a git repo within an organization, and maintain authority to run with an external key control mechanism. Point: The conf is going to end up in version control, so let's have a way to protect the obvious. A yaml hash example: --- moduledir: - './modules' - '/usr/local/anotherdir' ssh: port: 22 host: name: wehatenormalportslan* port: 4022 host: name: nopasswordallowed key: '~/.ssh/stupidoracle.pem' And so on. Add Comment   This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.