Issue #8438 has been updated by Jeff McCune.

Category set to cloudpack
Status changed from Unreviewed to Needs More Information
Assignee set to Dan Bode
Keywords set to fingerprint

# Separate Action #

Dan, with fingerprint becoming it's own action (#8348) , does this satisfy the 
need to have fingerprint be configurable?

The end user can opt to get the finger print or not with the following sequence:

 * puppet node create
 * puppet node fingerprint ...
 * puppet node install ...

Or 

 * puppet node create
 * puppet node install ...

----------------------------------------
Feature #8438: rather or not create should block for fingerprint should be 
configurable
https://projects.puppetlabs.com/issues/8438

Author: Dan Bode
Status: Needs More Information
Priority: Normal
Assignee: Dan Bode
Category: cloudpack
Target version: 
Keywords: fingerprint
Branch: 
Roadmapped: No


We should introduce a config option of rather or not to block the create action 
on console output for fingerprints.


-- 
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.

Reply via email to