I am pretty sure a composite namevar won't be necessary. It will just be a new
param such as pkgname that, if not specified, would default to the resource
title/name for backward compatibility.
Since we have the go ahead from Puppet, does anyone have the know-how to do
this? I could try to hack
If possible, I would love to see this done without a composite namevar.
The issue is that you're going to start ending up with variables
*everywhere* to figure out what you're actually installing.
If possible, I would like the same 'title' but that should be smoothly
combined with the provider.
On Tue, Mar 11, 2014 at 5:29 PM, Andy Parker wrote:
> Personally, I would be ok with yet another hack in puppet 3 to handle this
> issue since it has been coming up so often and since I also don't know a
> clear timeline for getting new functionality in to address this specific
> issue in a better
On Mon, Mar 10, 2014 at 1:36 PM, Trevor Vaughan wrote:
> Well, I'm certainly a fan.
>
>
Personally, I would be ok with yet another hack in puppet 3 to handle this
issue since it has been coming up so often and since I also don't know a
clear timeline for getting new functionality in to address thi
I wanted to remind everyone that we will only be accepting proposals
for PuppetConf 2014 until March 18th at midnight Pacific time, so you
have one week to get your talk idea submitted!
We also have several new Puppet Camps that were recently scheduled, so
we are accepting talk proposals for Puppe
Talk about coincidence. Today I implemented this fragment of a custom
type:
def self.title_patterns
[
[ /^([-_\w\/]+)\.(\d+)$/ , [ [:parent_interface ],
[:subinterface_number] ] ],
[ /.*/, [ ] ]
]
end
newparam(:parent_interface) do
desc "The name of the parent in
