Puppet

So using a simplified model:

notify {"Foo!": tag => [foo]}
notify {"Bar!": tag => [bar]}

I get the expected results for all the relevant cases:

• —tags foo
• —tags bar
• —tags foo,bar
• —tags baz
• (no tags specified)

So it appears that filtering by tags is working as expected, but tagging may not be.

You haven’t managed to reproduce this? So if you use —tags with a module name your testing fires correctly? I thought in your initial update you said it didn’t? —tags with a module name – not necessarily labelled, as you did with your example – in 0.2? would run just that module. In 2.6 it does not.

If you need anything further from me I’ll be happy to provide any more examples, including longer debug trails, should you require it.

It’s a problem with implicit tags on resources/classes rather than explicit tags. Here’s a simple test case:

class a { 
  notify { "hello a": }
}
class b { 
  notify { "hello b": }
}
include a, b

0.25.5:

$ puppet -v --tags b implicit_tags.pp 
info: Applying configuration version '1281767179'
notice: hello b
notice: //b/Notify[hello b]/message: defined 'message' as 'hello b'

2.6:

$ puppet -v --tags b implicit_tags.pp 
info: Applying configuration version '1281767216'

See following email thread: http://groups.google.com/group/puppet-users/browse_thread/thread/9d7bb94a8f9c240/d18e83876452b072?lnk=gst&q=tags#d18e83876452b072

This was broken in:

commit 0d4fd60c7c143cc1f4e4b0f99f359c09cbfbf21e

    Fixing #1903 - metaparam inheritance is much faster
    
    This doesn't actually fix the specific request in #1903,
    which said there should be no inheritance at all, but
    I've changed my mind on that.  Static inheritance is good,
    it should just be faster.
    
    This change could result in up to 70% speed improvements
    in compiling.

as part of a performance fix. It appears that restoring the functionality won’t too badly degrade performance (on first blush it looks like an incidental change).