Each "Project" needs to have it's own ssh private key

I agree having a global ssh private key is restrictive, particularly for something I'm working on right now. Is project based overrides the right place to do it though? A project might include nodes that require different keys. Would it be better to have the key and use this override set on in the resource parameters for the node? We already have the "username" attribute, so it would make sense to have key info here.

That might be the easiest to extend in the short term.

Sent from my iPhone

On Jan 10, 2011, at 1:12 AM, "Lighthouse" <no-reply@lighthouseapp.com>
wrote:

Keep it in this issue

using the prefix "default" does not match up w/ existing property and config file naming convention.
Perhaps then:

• project.ssh.keypath (project.properties)
• framework.ssh.keypath (framework.properties)
• node.ssh.keypath (resource model data for a node)

"node.ssh.keypath" won't work for xml..

also, it seems reduendant to prefix it with "framework" in the framework
properties file, and "project" in the project properties file.

what about just "ssh.keypath" for the properties files?

framework prefix may seem redundant but dropping it will create an inconsistency (which we often have too much of).

To keep the property naming somewhat closer would probably should change it to "ssh-keypath" across the board.
framework.ssh-keypath, project.ssh-keypath, and ssh-keypath for a node

the purpose of naming the properties the same thing was that it is easier to just consider the scope, and you could cut and paste from one to the other in order to promote or demote the scope of the setting.

if we'd rather just maintain the consistency for naming then i suppose the redundancy is at least consistent

ok that's fine...how about

1. node attribute "ssh-keypath"
   
2. project property "project.ssh-keypath"
   
3. framework prop "framework.ssh-keypath"
   
4. (compatibility) framework prop "framework.ssh.keypath"

sounds great

+1

the only problem is now we break consistency with framework properties "framework.ssh.timeout" and "framework.ssh.user"

(from [d82f95eab3508ba512fb9514891715d7daee071d]) Add documentation of ssh private key path configuration [#3 Each "Project" needs to have it's own ssh private key] https://github.com/dtolabs/rundeck/commit/d82f95eab3508ba512fb95148...