大网数据广告活动
服务器运维问答

Null / blank values on puppet facts

· 52CE 我爱测

How can I quickly and easily state that a null / blank value is OK on a fact within puppet? When assembling a custom fact I'm doing something like the following: /puppet/production/modules/hosts/lib/facter Facter.add(:hostslocal)…

问题原文

原帖链接 · Tim Brigham · CC BY-SA 3.0

How can I quickly and easily state that a null / blank value is OK on a fact within puppet?

When assembling a custom fact I'm doing something like the following:

/puppet/production/modules/hosts/lib/facter

Facter.add(:hostslocal) do
  setcode do
    Facter::Util::Resolution.exec("cat /etc/hosts.local 2> /dev/null")
  end
end

This works perfectly except if the file doesn't exist, in which case it will blow up with something like the following when used in Puppet.

Detail: Could not find value for 'hostslocal'

I've been able to work around it with something akin to 'if file not exists write a line that contains only a comment' but that seems kludgy.

已采纳解答

原帖链接 · sciurus · CC BY-SA 3.0

Facter has lots of facts that only set under certain circumstances. Before using them you should check if they are undefined.

if $::hostslocal != undef {
  do_your_thing_here
}

If you really want your custom fact to always have a value, you can do something like

Facter.add(:hostslocal) do
  setcode do
    if File.exist? "/etc/hosts.local"
      Facter::Util::Resolution.exec("cat /etc/hosts.local 2> /dev/null")
    else
      "unknown"
    end
  end
end

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2013-11-22)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。