Issue #8348 has been updated by Jeff McCune. Due date set to 07/15/2011 Priority changed from Normal to High
---------------------------------------- Refactor #8348: Fingerprinting should be it's own action https://projects.puppetlabs.com/issues/8348 Author: Jeff McCune Status: Accepted Priority: High Assignee: Jeff McCune Category: Target version: 0.6.0 Keywords: cloudpack Branch: # Overview # In order to quickly launch N systems, then install Puppet on those N systems it would be better to support launching in parallel rather than sequentially. With the current create action implementation, the action can only launch one node at a time and it waits for the node's SSH host key to become available in the AWS console to compare it to the host key of the system. Based on a discussion on dev@ this could be separated to it's own action with the additional feature of adding the SSH host key to the known_hosts file. # Suggested Use Case # <pre> > > The action could also append the host key to the known hosts file for > > convenience. > > As the default behavior? I think so. I'm thinking: puppet subcommand fingerprint i-f08e6e91 or puppet subcommand fingerprint --no-knownhosts i-f08e6e91 So I think it should be the documented default behavior to add the host key to the personal known hosts file, but we give the end user the option to only print the key to standard output. </pre> -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://projects.puppetlabs.com/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
