On Nov 4, 2008, at 12:54 PM, Aj wrote:
> As my reply soriginally tated, undef is part of the override syntax
> and as such is only valid in an inherited, overridden resource. I.e.;
> not a bug.
>
> Perhaps a feature request, although I personally believe that empty
> string assignment is sufficie
On Nov 4, 2008, at 1:54 PM, Aj wrote:
>
> As my reply soriginally tated, undef is part of the override syntax
> and as such is only valid in an inherited, overridden resource. I.e.;
> not a bug.
>
> Perhaps a feature request, although I personally believe that empty
> string assignment is suffic
As my reply soriginally tated, undef is part of the override syntax
and as such is only valid in an inherited, overridden resource. I.e.;
not a bug.
Perhaps a feature request, although I personally believe that empty
string assignment is sufficient.
On 5/11/2008 at 8:44 AM, Tim Harper <[EM
>> You want uid => undef
>>
>> --Paul
>
Thanks Paul - this is the lead I needed to get to at least a work
around.
Given:
=== EXHIBIT A ===
define user_test() {
user { $title:
ensure => present,
uid=> undef
}
}
node "server" {
user_test { 'boogy': }
}
=== EXHI
Can't undef only be used with the inheritance syntax?
The closest we have to initializing to undefined is an empty string
('') - you can compare this quite easily in .6 - check the language
tut - but you need to do a case/selector for comparism pre-.6
E.g.;
case $uid {
'': {
user {
You want uid => undef
--Paul
On Mon, Nov 3, 2008 at 11:44 AM, Tim Harper <[EMAIL PROTECTED]> wrote:
>
> I have a define that acts as a convenience wrapper around the user
> type and a few other things.
>
> With the 'user' type, if don't pass the uid parameter, it will default
> to let the system
On Mon, Nov 03, 2008 at 11:44:08AM -0700, Tim Harper wrote:
>
> I have a define that acts as a convenience wrapper around the user
> type and a few other things.
>
> With the 'user' type, if don't pass the uid parameter, it will default
> to let the system auto-assign it. However, passing u
