> realize(User[1], User[2], User[10])
>
>
> ah, but your collection syntax requires that you have to know the gid of
> the resources you are realizing :)
>
> There are certainly cases where the collection syntax is easier, but I
> feel that the vast majority of virtual resource realizat
On Mon, Feb 14, 2011 at 8:56 AM, Dan Bode wrote:
>
>
> On Mon, Feb 14, 2011 at 6:49 AM, Nigel Kersten wrote:
>
>> On Sun, Feb 13, 2011 at 9:59 PM, Dan Bode wrote:
>>
>>>
>>> We have only been teaching <| |> in the puppetmaster training as a way to
>>> realize virtual resources. We do not teach t
On Mon, Feb 14, 2011 at 6:49 AM, Nigel Kersten wrote:
> On Sun, Feb 13, 2011 at 9:59 PM, Dan Bode wrote:
>
>>
>> We have only been teaching <| |> in the puppetmaster training as a way to
>> realize virtual resources. We do not teach that it is possible to override
>> attributes with this syntax
On Sun, Feb 13, 2011 at 9:59 PM, Dan Bode wrote:
>
> We have only been teaching <| |> in the puppetmaster training as a way to
> realize virtual resources. We do not teach that it is possible to override
> attributes with this syntax as well: <| |> {} (at least in part b/c the
> implications/non-
On Sun, Feb 13, 2011 at 7:21 PM, Nigel Kersten wrote:
>
>
> On Sat, Feb 12, 2011 at 7:40 PM, Dan Bode wrote:
>
>>
>>> Could we add the ability to query whether a given resource has
been realized or not? How much of an ordering problem is this?
Package <| state == virtual |>
Packag
On Sun, Feb 13, 2011 at 19:21, Nigel Kersten wrote:
> On Sat, Feb 12, 2011 at 7:40 PM, Dan Bode wrote:
>>>
Could we add the ability to query whether a given resource has
been realized or not? How much of an ordering problem is this?
Package <| state == virtual |>
Package <| st
