Open davidnewton opened 9 years ago
Hi Alessandro,
OK, sorry, I did wonder! What is the solution for changing this ? How do I reference this from inside my own "profile" module [using the Craig Dunn model]? as I'm unable to change a variable out of scope.
Many thanks,
David
On 17 October 2014 21:08, Alessandro Franceschi notifications@github.com wrote:
This variable is used in exported resources by different nodes (of different OS). We don't want to change it "client" side, with this change on the Nagios server would be created (or attempted to be created) configuration files in nagios and nagios2 directories, and this is not a wanted solution.
Reply to this email directly or view it on GitHub https://github.com/example42/puppet-nagios/pull/40#issuecomment-59568061 .
David Newton Senior Operations Engineer Esendex Ltd
Tel: +44 115 989 5102 Email: david.newton@esendex.com Web: www.esendex.com
Confidentiality: This e-mail (and any associated files) is intended only for the use of the intended recipient and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any disclosure, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and then delete it from your computer. Messages sent to and from us may be monitored. The views expressed in this message are those of the author and do not necessarily represent the views of Esendex Ltd.
Security: This e-mail and any attachments are believed to be free from any virus but it is the responsibility of the recipient to ensure this is so. E-mail is not a 100% secure communications medium. We recommend you observe this when e-mailing us.
Esendex Ltd is a limited company registered in the UK, with company number 04217280 and having its registered office at 15 Warwick Road * Stratford Upon Avon * Warwickshire * CV37 6YW.
You should set $::nagios_customconfigdir at top scope, for example in /etc/puppet/manfests/site.pp (outside any node definition) or in your ENC, or, but it's a bit out of place, in a custom fact.
Ok, I will give that a try! Many thanks for your help - it's really appreciated :)
On 21 October 2014 07:57, Alessandro Franceschi notifications@github.com wrote:
You should set $::nagios_customconfigdir at top scope, for example in /etc/puppet/manfests/site.pp (outside any node definition) or in your ENC, or, but it's a bit out of place, in a custom fact.
Reply to this email directly or view it on GitHub https://github.com/example42/puppet-nagios/pull/40#issuecomment-59886806 .
David Newton Senior Operations Engineer Esendex Ltd
Tel: +44 115 989 5102 Email: david.newton@esendex.com Web: www.esendex.com
Confidentiality: This e-mail (and any associated files) is intended only for the use of the intended recipient and may contain information that is confidential, subject to copyright or constitutes a trade secret. If you are not the intended recipient you are hereby notified that any disclosure, copying or distribution of this message, or files associated with this message, is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and then delete it from your computer. Messages sent to and from us may be monitored. The views expressed in this message are those of the author and do not necessarily represent the views of Esendex Ltd.
Security: This e-mail and any attachments are believed to be free from any virus but it is the responsibility of the recipient to ensure this is so. E-mail is not a 100% secure communications medium. We recommend you observe this when e-mailing us.
Esendex Ltd is a limited company registered in the UK, with company number 04217280 and having its registered office at 15 Warwick Road * Stratford Upon Avon * Warwickshire * CV37 6YW.
This variable is used in exported resources by different nodes (of different OS). We don't want to change it "client" side, with this change on the Nagios server would be created (or attempted to be created) configuration files in nagios and nagios2 directories, and this is not a wanted solution.