Hello

I'm upgrading from 3.6 to 3.7 and have it a issue/bug

I'm using users/groups but to keep it short and something others can run
without the mess of users being made I've made up a file example

====== modules/filegroups/manifests/matches.pp =======
class filegroups::matches {
  include files
  Files::Afile <| tag == matches |>
}
====== modules/files/manifests/afile.pp =======
define files::afile {
  file { $title: ensure=>present, content=>'hello', }
}
====== modules/files/manifests/data.pp =======
class files::data {
  @files::afile { '/tmp/meanttobemade': tag=>['matches'], }
  @files::afile { '/tmp/notmeanttobemade': tag=>['doesnotmatch'], }
}
====== modules/files/manifests/init.pp =======
class files {
  include files::data
}
====== site.pp =======
node default {
  include filegroups::matches
}

makes both files
Notice:
/Stage[main]/Files::Data/Files::Afile[/tmp/notmeanttobemade]/File[/tmp/notmeanttobemade]/ensure:
created


If I rename modules/filegroups/manifests/matches.pp
to  modules/filegroups/manifests/iwantmatches.pp (and change the first line)
or rename the tag I get the desired behaviour

Anyone else seen this? Is this a bug?

There is a matching old question at askpuppetlabs
https://ask.puppetlabs.com/question/14349/upgrade-to-371-causes-resource-collectors-to-realize-everything/
that I've chipped in on the end off

Thanks,

Neil

-- 
You received this message because you are subscribed to the Google Groups 
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/puppet-users/CAAohVBe750Dk8Hc207TsGiNFZeU2kTyE1SR5XrO7-bgCJHFiEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to