On Wed, Dec 08, 2010 at 04:04:17PM +0000, Dominic Cleal wrote: > It'd probably conflict with your project provider though for custom > projects. It only really makes sense to define a custom project once > and specify all attributes there, at the expense of not being able to > specify attributes of a built-in project as individual resources.
you can do
project {'default':
attributes => [ 'mynewkey=mynewvalue' ],
attribute_membership => minimum,
}
to add a custom attribute. What you can't do is to specify that you dont
want a special attribute and at the same time you dont know what
attributes you want to keep. And you have to specify all attributes at
one place.
BTW: In my last commit I use projects -l to get project information but I
haven't testet on a real solaris machine (but I have added specs that
test the parsing against some stored output).
-Stefan
pgpuCQDeA8oMY.pgp
Description: PGP signature
