You can have multiple resolutions for a single fact, and use fact
precedence to determine which ones should be used first.
http://docs.puppetlabs.com/guides/custom_facts.html#fact-precedence has the
details on this.
On Tue, Jul 31, 2012 at 3:24 PM, rjl wrote:
> Thanks ZJE. That is what I ended u
Thanks ZJE. That is what I ended up doing.
On Tuesday, July 31, 2012 2:50:44 PM UTC-6, ZJE wrote:
>
> It may be best to hold your value in a temporary variable and just have
> the setcode run at the end. I can't remember where I read it, but I don't
> think ruby custom facts can override other
It may be best to hold your value in a temporary variable and just have the
setcode run at the end. I can't remember where I read it, but I don't think
ruby custom facts can override other ruby custom facts once they are set
(thought I believe the FACTER_ environment variables can override ruby
Of course should be == and not =
if Facter.value("http_server") == "false"
# Change value of "server_type" here. I have tried many different
approaches but none work.
end
On Tuesday, July 31, 2012 2:38:15 PM UTC-6, rjl wrote:
>
> Hi all,
> I have a custom facts script that is distributed to a
