Feature #1035

"all" in tagmail.conf should allow exclusions

Added by kbrede - over 5 years ago. Updated 3 months ago.

Status:InvestigatingStart date:
Priority:NormalDue date:
Assignee:Nigel Kersten% Done:

0%

Category:reports
Target version:-
Affected Puppet version:0.24.8 Branch:
Keywords:

Description

For example the following line in tagmail.conf

all, !test_class: user@example.com

still reports test_class.

History

#1 Updated by kbrede - over 5 years ago

Here’s the class I’m using that isn’t excluded by “!trim_reports.”

class trim_reports {
    tidy { "/var/lib/puppet/reports":
        recurse => true,
        backup  => false,
        type    => ctime,
        age     => '5d';
    }
}

I did some testing and found the class name (trim_reports) does not appear to be picked up as a tag.

  message: Tidying, older than 432000 seconds
  objectsource: true
  source: //Node[puppet.example.com]/trim_reports/Tidy[/var/lib/puppet/reports/puppet.example.com/200801290034.yaml]/ensure
  tags:

  - :tidy
  - :ensure

After adding “tag => trim_reports” to the class the tag was picked up and excluded from the email properly.

  message: Tidying, older than 432000 seconds
  objectsource: true
  source: //Node[puppet.example.com]/trim_reports/Tidy[/var/lib/puppet/reports/puppet.example.com/200801290038.yaml]/ensure
  tags:

  - :tidy
  - :trim_reports
  - :ensure

#2 Updated by Redmine Admin about 5 years ago

  • Status changed from 1 to Accepted

#3 Updated by James Turnbull over 4 years ago

  • Assignee changed from Puppet Community to AJ Christensen
  • Affected Puppet version set to 0.24.4

AJ – you fancy throwing your eyes over this?

#4 Updated by Luke Schierer over 3 years ago

  • Affected Puppet version changed from 0.24.4 to 0.24.8

This is still happening in 0.2.4.8 running on RHEL5.

#5 Updated by James Turnbull over 3 years ago

  • Assignee deleted (AJ Christensen)

#6 Updated by Nigel Kersten over 2 years ago

  • Status changed from Accepted to Investigating
  • Assignee set to Nigel Kersten

Does anyone still care about this?

#7 Updated by James Turnbull almost 2 years ago

  • Target version deleted (4)

#8 Updated by Paul Barton 3 months ago

Yes this would be a good feature to have. I am currently affected by http://projects.puppetlabs.com/issues/9167 and have nodes reporting on each run after implmenting the MCollective+Facter recipe at http://projects.puppetlabs.com/projects/mcollective-plugins/wiki/FactsFacterYAML. It seems like adding a tag ‘no_tagmail’ to that recipe would allow something like:

all, !no_tagmail: user@example.com

But it doesn’t work.

Also available in: Atom PDF