Issue #7491 has been updated by Nigel Kersten. Status changed from Needs Decision to Rejected
I believe Stefan has answered this one. ---------------------------------------- Bug #7491: design flaw with parameters for mount type https://projects.puppetlabs.com/issues/7491 Author: Garrett Honeycutt Status: Rejected Priority: High Assignee: Nigel Kersten Category: Target version: Affected Puppet version: 2.6.4 Keywords: mount nfs Branch: >From http://docs.puppetlabs.com/references/stable/type.html#mount <pre> path The deprecated name for the mount point. Please use name now. </pre> It is not desirable to always have name map to the path of the mount point. Reasons below. 1) Consistency - not all resources require that name map to something useful. ie: for the 'exec' resource you can specify the command to be run as the name or you can specify a 'command' parameter. 2) One might want a descriptive name 3) With the current implementation, one cannot have multiple virtual resources with the same mount path and realize based on some tag, because you will have multiple resource/name's. This is common if you have different NFS devices exporting data that goes into the same mount paths and you want to select a certain NFS device. -- 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.
