Issue #21887 has been updated by Henrik Lindberg.
Yes it requires typing the parameters, or having the ability to annotate them (compare to javas @xxx syntax). Secondly, having the ability to introspect classes, and resource types via an API. Typing is interesting, it can be made "opt in". We could make password a subtype of string perhaps. By adding annotations we risk creating a flea market of meta data. We were also discussing "encrypted data" the other day and the ability to pass encrypted values around. This seems related. Not quite sure what tools would do with a password though, it is a parameter at the receiving end. The actual values comes from someplace else, and is the text that is sensitive. Isn't it more interesting to be able to pass encrypted data in a type in a catalog and have the type in the agent decrypt it? ---------------------------------------- Feature #21887: Ability to specify a class parameter as password parameter https://projects.puppetlabs.com/issues/21887#change-95540 * Author: Raghavendra Rachamadugu * Status: Investigating * Priority: Normal * Assignee: Henrik Lindberg * Category: * Target version: * Affected Puppet version: * Keywords: * Branch: ---------------------------------------- It would help if class parameters can be decorated as sensitive so tools processing them can handle such parameters in a secure fashion, like by hiding the actual value when showing or when user is typing. -- 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 unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/groups/opt_out.
