Jira (PUP-3230) Exported resource collectors don't support standard puppet expression set

[Trevor Vaughan (JIRA)]

Title: Message Title

Trevor Vaughan commented on an issue   Re: Exported resource collectors don't support standard puppet _expression_ set I agree that this would be nice to have, but would tags work here to solve your issue more cleanly? class myapp::db::firewall { @@firewall { "180 INPUT allow mysql for $::hostname" : chain => 'INPUT', source => $::ipaddress_main, action ="" accept, port => 3306, state => 'NEW', tag => '180_input_allow_mysql' } Firewall <| port == 3306 and tag == '180_input_allow_mysql'|> if $::ipaddress_private != undef and $::datacenter == "digitalocean" { @@firewall { "190 INPUT allow mysql for $::hostname" : chain => 'INPUT', source => $::ipaddress_private, action ="" accept, port => 3306, state => 'NEW, tag => '190_input_allow_mysql' } Firewall <| port == 3306 and tag == '190_input_allow_mysql'|> } } } Add Comment   Puppet / PUP-3230 Exported resource collectors don't support standard puppet _expression_ set When trying to gather resources, it would be helpful to be able to gather resources by a regex using the regex match operator (=~). Example; I have some database servers running in one data center, with two replicated databases in two other datacenters. To allow replication traffic, I've created firewall rules which allow tcp traffic on port 3306. O... This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.