Sha256: b1fa107ae7a85b97c79153cfcb2694a32c34c8e6b255fb598941f3df733f0a88
Contents?: true
Size: 1.28 KB
Versions: 18
Compression:
Stored size: 1.28 KB
Contents
# This tests is intended to verify that passing the `--no-block` command to facter will prevent
# fact blocking, despite a blocklist being specified in the config file.
test_name "C99971: the `--no-block` command line flag prevents facts from being blocked" do
tag 'risk:medium'
require 'facter/acceptance/user_fact_utils'
extend Facter::Acceptance::UserFactUtils
agents.each do |agent|
# default facter.conf
facter_conf_default_dir = get_default_fact_dir(agent['platform'], on(agent, facter('kernelmajversion')).stdout.chomp.to_f)
facter_conf_default_path = File.join(facter_conf_default_dir, "facter.conf")
teardown do
on(agent, "rm -rf '#{facter_conf_default_dir}'", :acceptable_exit_codes => [0, 1])
end
# create the directories
on(agent, "mkdir -p '#{facter_conf_default_dir}'")
step "Agent #{agent}: create config file" do
create_remote_file(agent, facter_conf_default_path, <<-FILE)
cli : { debug : true }
facts : { blocklist : [ "EC2" ] }
FILE
end
step "no facts should be blocked when `--no-block` is specified" do
on(agent, facter("--no-block")) do |facter_output|
assert_no_match(/blocking collection of .+ facts/, facter_output.stderr, "Expected no facts to be blocked")
end
end
end
end
Version data entries
18 entries across 18 versions & 2 rubygems