Issue #9657 has been updated by Brice Figureau.
I refrained implementing anything until we properly decided what was the best option. Right now I believe (but I changed my mind a lot in the past) that either: * use the current @puppet device@ application with a manifest as last argument * create 'device-apply' are our best options. This further separates the apply-to-host mechanism (like puppet device is different than puppet agent). If we settle on one of the above, I should probably be able to propose a patch around next week. ---------------------------------------- Feature #9657: Improve puppet apply to support network device https://projects.puppetlabs.com/issues/9657#change-73097 Author: Nan Liu Status: Accepted Priority: Normal Assignee: J.D. Welch Category: Target version: 2.7.x Affected Puppet version: 2.7.3 Keywords: network, device Branch: After writing additional network device, it seems reasonable to support device in puppet apply. Currently network resources are skipped: debug: /Stage[main]//F5_virtualserver[www-http]: Skipping device resources because running on a host debug: /Stage[main]//F5_virtualserver[www-https]: Skipping device resources because running on a host Rather than having two separate modules with slight differences (see: https://github.com/puppetlabs/puppetlabs-f5/issues/42). It makes sense to ensure puppet resource and puppet apply also supports --deviceconfig option. -- 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.
