When you use alias in a definition or class ie. Access alias fom within the same
enclosing scope you created the object that provieds the alias in it wors fine.
I use alias in that exact case frequently eg. For requirements/subscribes etc.
----- Urspr?ngliche Nachricht -----
Von: Francois Deppierraz <francois at ctrlaltdel.ch>
Gesendet: Dienstag, 28. August 2007 19:19
An: Puppet User Discussion <puppet-users at madstop.com>
Betreff: Re: [Puppet-users] Aliases not working in a subclass ?
Luke Kanies wrote:
> The ''alias'' metaparam is only used on the client, which
means that
> the parser doesn''t know anything about it. I can''t
decide if this is
> a bug or not, considering that you''ve already got the ability to
> easily have two names for your resource (the name and title).
Thanks, everything is now working fine using title/name instead of
title/alias. Ticket #790 type was changed to enhancement.
> In retrospect, though, it might make more sense to get rid of this
> whole name/title split and just stick to aliases as the means of
> providing multiple names. Hmm. I never thought of that. Hrm.
In my base, the alias meta-parameter was more intuitive at first than
using a name attribute.
What was the reasoning behind the implementation of the alias
meta-parameter ?
_______________________________________________
Puppet-users mailing list
Puppet-users at madstop.com
https://mail.madstop.com/mailman/listinfo/puppet-users
