On Oct 15, 2008, at 10:00 AM, Brice Figureau wrote:
>
>
> OK, my above manifest is then perfectly legit.
>
> And the following one is legit too:
> class t {
> file { "/tmp/testing": content => "pouet" }
> File["/tmp/testing"] { mode => 0600 }
> }
>
> class t2 inherits t {
> File["/tmp/testing"] { mode => 0666 }
> }
> include t2
>
> (Except it didn't change the mode to 0666, that's strange).
Indeed; it worked for me.
>
> Since the collection overriding stuff I did for #1088 is using the
> exact
> same codepath as resource overriding (except it appears later), I'm
> pretty sure it follows exactly the same restrictions as the resource
> overriding.
Perfect.
This syntax is useful enough that I expect people will start making
more virtual resources just so they can make mass changes. E.g., this
would make it easy to have all Yum packages depend on all yumrepo
instances.
Is it worth having this syntax work on non-virtual resources, with the
additional behaviour of it automagically realizing virtual resources?
--
Always be wary of any helpful item that weighs less than its operating
manual. -- Terry Pratchett
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---
