Ask Your Question

Notify resource and Foreman

asked 2016-02-02 16:13:40 -0600

amirb gravatar image

updated 2016-02-11 07:02:19 -0600

Does anyone can answer this?

I'm trying to find a work-around to the issue described here

edit retag flag offensive close merge delete

2 Answers

Sort by ยป oldest newest most voted

answered 2016-02-07 04:25:48 -0600

Iakov GAN gravatar image

If you are into a hacky mood, you can change content of your report by modifying foreman.rb file at your puppet master.

edit flag offensive delete link more


That's exactly what I'm trying to do, but I can't get the code right. How can I add an exception to treat Notify resource as an unchanged status?

amirb gravatar imageamirb ( 2016-02-08 05:06:02 -0600 )edit

answered 2016-02-02 16:39:33 -0600

amirb gravatar image

updated 2016-02-06 00:19:18 -0600

I'll refine the question: Is there a way to use the Notify resource without causing puppet to report that the node has changed? Meaning just print the message to client log (and therefore the message will be visible in report) but without puppet classify the event as an applied configuration?

The reason is that when puppet triggers the Notify resource, Foreman flags the node as being active (changed)

UPDATE No one has a clue? I'm thinking about changing Foreman report file so that the UI will ignore Notify events so that the node's status will remain unchanged but still show the message in the report. Can someone point me to the right direction? Thanks!

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-02-02 16:13:40 -0600

Seen: 165 times

Last updated: Feb 11 '16