facter 4.0.29 → 4.0.30

data/CODEOWNERS

@@ -1,2 +0,0 @@
-# Default to Ghost team
-* @puppetlabs/ghost @puppetlabs/night-s-watch

data/CONTRIBUTING.md

@@ -1,93 +0,0 @@
-
-# How to contribute
-
-Third-party patches are essential for keeping facter great. We simply can't
-access the huge number of platforms and myriad configurations for running
-Facter. We want to keep it as easy as possible to contribute changes that
-get things working in your environment. There are a few guidelines that we
-need contributors to follow so that we can have a chance of keeping on
-top of things.
-
-## Getting Started
-
-* Make sure you have a [Jira account](https://tickets.puppetlabs.com).
-* Make sure you have a [GitHub account](https://github.com/signup/free).
-* Submit a Jira ticket for your issue if one does not already exist.
-  * Clearly describe the issue including steps to reproduce when it is a bug.
-  * Make sure you fill in the earliest version that you know has the issue.
-  * A ticket is not necessary for [trivial changes](https://puppet.com/community/trivial-patch-exemption-policy)
-* Fork the repository on GitHub.
-
-## Making Changes
-
-* Create a topic branch from where you want to base your work.
-  * This is usually the master branch.
-  * Once merged, your work will be automatically promoted to the other release
-    streams when our internal CI passes.
-  * To quickly create a topic branch based on master, run `git checkout -b
-    fix/master/my_contribution master`. Please avoid working directly on the
-    `master` branch.
-* Make commits of logical units.
-* Check for unnecessary whitespace with `git diff --check` before committing.
-* Make sure your commit messages are in the proper format. We use the [50/72 rule](https://git-scm.com/book/en/v2/Distributed-Git-Contributing-to-a-Project) in commit messages.
-* If the commit addresses an issue filed in the [Facter Jira project](https://tickets.puppetlabs.com/browse/FACT), start the first line of the commit with the issue number in parentheses.
-
-````
-    (FACT-1234) Make the example in CONTRIBUTING imperative and concrete
-
-    Without this patch applied the example commit message in the CONTRIBUTING
-    document is not a concrete example.  This is a problem because the
-    contributor is left to imagine what the commit message should look like
-    based on a description rather than an example.  This patch fixes the
-    problem by making the example concrete and imperative.
-
-    The first line is a real life imperative statement with a ticket number
-    from our issue tracker.  The body describes the behavior without the patch,
-    why this is a problem, and how the patch fixes the problem when applied.
-````
-
-* Make sure you have added the necessary tests for your changes.
-* Run _all_ the tests to assure nothing else was accidentally broken.
-  * We recommend running `./check.sh` to have the same checks run as on github
-
-## Making Trivial Changes
-
-For [changes of a trivial nature](https://puppet.com/community/trivial-patch-exemption-policy), it is not always necessary to create a new
-ticket in Jira. In this case, it is appropriate to start the first line of a
-commit with one of  `(docs)` or `(maint)` instead of a ticket number.
-
-If a Jira ticket exists for the documentation commit, you can include it
-after the `(docs)` token.
-
-```
-    (docs)(DOCUMENT-000) Add docs commit example to CONTRIBUTING
-
-    There is no example for contributing a documentation commit
-    to the Facter repository. This is a problem because the contributor
-    is left to assume how a commit of this nature may appear.
-
-    The first line is a real-life imperative statement with '(docs)' in
-    place of what would have been the FACT project ticket number in a
-    non-documentation related commit. The body describes the nature of
-    the new documentation or comments added.
-```
-
-For commits that address trivial repository maintenance tasks start the first line of the commit with `(maint)`
-
-## Submitting Changes
-
-* Sign the [Contributor License Agreement](http://links.puppet.com/cla).
-* Push your changes to a topic branch in your fork of the repository.
-* Submit a pull request to the repository in the puppetlabs organization.
-* Update your ticket to mark that you have submitted code and are ready for it to be reviewed.
-  * Include a link to the pull request in the ticket
-
-# Additional Resources
-
-* [Puppet community guidelines](https://puppet.com/community/community-guidelines/)
-* [Bug tracker (Jira)](https://tickets.puppetlabs.com/browse/FACT)
-* [Contributor License Agreement](http://links.puppet.com/cla)
-* [General GitHub documentation](http://help.github.com/)
-* [GitHub pull request documentation](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork)
-* [puppet-dev mailing list](https://groups.google.com/forum/#!forum/puppet-dev)
-* [Puppet-dev Slack channel](https://puppetcommunity.slack.com/archives/C0W1X7ZAL)

data/Gemfile

@@ -1,12 +0,0 @@
-# frozen_string_literal: true
-
-source ENV['GEM_SOURCE'] || 'https://rubygems.org'
-
-gemspec name: 'facter'
-
-group(:release, optional: true) do
-  gem 'github_changelog_generator' if Gem::Version.new(RUBY_VERSION.dup) >= Gem::Version.new('2.3.0')
-end
-
-local_gemfile = File.expand_path('Gemfile.local', __dir__)
-eval_gemfile(local_gemfile) if File.exist?(local_gemfile)

data/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2019 Puppet
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in all
-copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.

data/README.md

@@ -1,50 +0,0 @@
-# facter-ng
-
-[![Modules Status](https://github.com/puppetlabs/facter/workflows/Acceptance%20tests/badge.svg?branch=master)](https://github.com/puppetlabs/facter/actions)
-[![Modules Status](https://github.com/puppetlabs/facter/workflows/Unit%20tests/badge.svg?branch=master)](https://github.com/puppetlabs/facter/actions)
-[![Modules Status](https://github.com/puppetlabs/facter/workflows/Checks/badge.svg?branch=master)](https://github.com/puppetlabs/facter/actions)
-[![Test Coverage](https://api.codeclimate.com/v1/badges/bf43445f767f2d64170a/test_coverage)](https://codeclimate.com/github/puppetlabs/facter/test_coverage)
-[![Maintainability](https://api.codeclimate.com/v1/badges/bf43445f767f2d64170a/maintainability)](https://codeclimate.com/github/puppetlabs/facter/maintainability)
-[<img src="https://img.shields.io/badge/slack-puppet--dev-brightgreen?logo=slack">](https://puppetcommunity.slack.com/messages/C0W1X7ZAL)
-
-
-Facter is a command-line tool that gathers basic facts about nodes (systems) such as hardware details, network settings, OS type and version, and more. These facts are made available as variables in your Puppet manifests and can be used to inform conditional expressions in Puppet.
-
-## Supported platforms
-* Linux
-* macOS
-* Windows
-* Solaris
-* AIX
-
-## Requirements
-* Ruby 2.3+
-
-## Basic concepts
-The project has three main parts, the framework, facts and resolvers. 
-In the framework we implement functionality that is agnostic of specific facts like parsing user input, formatting output, etc.
-
-Facts are the nuggets of information that will be provided by facter e.g. `os.name`, `networking.interfaces`, etc.
-
-Resolvers have the role of gathering data from the system. 
-For example a resolver can execute a command on the system, can read a file or any operation that retries some data from a single source on the system. 
-
-![Facter user interaction](docs/diagrams/facter_user_interaction.png?raw=true)
-
-## Getting started
-After cloning the project, run `bundle install` to install all dependencies.
-
-You can run facter by executing `./bin/facter`. 
-The command will output all the facts that facter detected for the current os.
-
-In order to generate a fact, we can use the rake task `rake 'create_fact[<os>,<fact_name>]'` e.g. `rake 'create_fact[ubuntu,facterversion]'`
-When generating a fact, the unit test for that fact is also generated. Facts should call on or more resolvers in order to obtain the data they need.
-
-The implementation can be validated locally by running the `./check.sh` script. 
-
-## Goals - fast, easy, compatible
-* Gain performance similar to the C++ version of Facter. We plan to achieve this goal by gathering multiple facts with only one call and by using the faster Win32 API rather than WMI for the Windows implementation. 
-* Facilitate community contribution. At the moment, C++ presents a possible impediment for community contributions. 
-* Enable native integration with other Ruby-based projects such as Bolt and puppet.
-* Enable native integration for custom facts.
-* Provide 100% compatibility with C++ Facter (drop-in replacement).

data/Rakefile

@@ -1,72 +0,0 @@
-# frozen_string_literal: true
-
-require 'bundler/gem_tasks'
-require 'rspec/core/rake_task'
-
-RSpec::Core::RakeTask.new(:spec)
-Dir.glob(File.join('tasks/**/*.rake')).each { |file| load file }
-
-task default: :spec
-
-def retrieve_from_keyboard
-  return unless ARGV.include?('changelog')
-
-  puts "Please provide the next release tag:\n"
-  next_version = $stdin.gets.chomp
-  raise(ArgumentError, ' The string that you entered is invalid!') unless /[0-9]+\.[0-9]+\.[0-9]+/.match?(next_version)
-
-  next_version
-end
-
-if Bundler.rubygems.find_name('github_changelog_generator').any?
-  require 'github_changelog_generator/task'
-
-  GitHubChangelogGenerator::RakeTask.new :changelog do |config|
-    if Rake.application.top_level_tasks.include?('changelog') &&
-       ENV['CHANGELOG_GITHUB_TOKEN'].nil?
-      raise 'Set CHANGELOG_GITHUB_TOKEN environment variable' /
-            " eg 'export CHANGELOG_GITHUB_TOKEN=valid_token_here'"
-    end
-
-    config.user = 'puppetlabs'
-    config.project = 'facter'
-    config.release_branch = '4.x'
-    config.since_tag = File.read('VERSION').strip
-    config.future_release = retrieve_from_keyboard
-    config.exclude_labels = ['maintenance']
-    config.add_pr_wo_labels = true
-    config.issues = false
-    config.max_issues = 100
-    config.header = ''
-    config.base = 'CHANGELOG.md'
-    config.merge_prefix = '### UNCATEGORIZED PRS; GO LABEL THEM'
-    config.configure_sections = {
-      "Changed": {
-        "prefix": '### Changed',
-        "labels": ['backwards-incompatible']
-      },
-      "Added": {
-        "prefix": '### Added',
-        "labels": ['feature']
-      },
-      "Fixed": {
-        "prefix": '### Fixed',
-        "labels": ['bugfix']
-      }
-    }
-  end
-else
-  desc 'Generate a Changelog from GitHub'
-  task :changelog do
-    raise <<~ERRORMESSAGE
-      The changelog tasks depends on github_changelog_generator gem.
-      Please install github_changelog_generator:
-      ---
-      Gemfile:
-        optional:
-          ':release':
-            - gem: 'github_changelog_generator'
-              condition: "Gem::Version.new(RUBY_VERSION.dup) >= Gem::Version.new('2.2.2')"
-    ERRORMESSAGE
-  end
-end

data/VERSION

@@ -1 +0,0 @@
-4.0.29

data/acceptance/.beaker.yml

@@ -1,15 +0,0 @@
----
-ssh:
-  keys:
-    - id_rsa_acceptance
-    - ~/.ssh/id_rsa-acceptance
-xml:                         true
-timesync:                    false
-repo_proxy:                  true
-add_el_extras:               false
-forge_host:                  api-forge-aio02-petest.puppet.com
-'master-start-curl-retries': 30
-log_level:                   debug
-preserve_hosts:              onfail
-helper:                      ./lib/helper.rb
-options_file:                ./config/aio/options.rb

data/acceptance/.gitignore

@@ -1,12 +0,0 @@
-.vagrant
-local_options.rb
-repos.tar
-repo-configs
-log
-id_rsa-acceptance
-id_rsa-acceptance.pub
-preserved_config.yaml
-merged_options.rb
-junit
-tmp
-.bundle

data/acceptance/Gemfile

@@ -1,24 +0,0 @@
-source ENV['GEM_SOURCE'] || "https://rubygems.org"
-
-def location_for(place, fake_version = nil)
-  if place =~ /^(git:[^#]*)#(.*)/
-    [fake_version, { :git => $1, :branch => $2, :require => false }].compact
-  elsif place =~ /^file:\/\/(.*)/
-    ['>= 0', { :path => File.expand_path($1), :require => false }]
-  else
-    [place, { :require => false }]
-  end
-end
-
-gem "beaker", *location_for(ENV['BEAKER_VERSION'] || "~> 4")
-gem 'beaker-puppet', *location_for(ENV['BEAKER_PUPPET_VERSION'] || '~> 1')
-gem "beaker-hostgenerator", *location_for(ENV['BEAKER_HOSTGENERATOR_VERSION'] || "~> 1.1")
-gem "beaker-abs", *location_for(ENV['BEAKER_ABS_VERSION'] || "~> 0.5")
-gem "beaker-vagrant", *location_for(ENV['BEAKER_VAGRANT_VERSION'] || "~> 0")
-gem "beaker-vmpooler", *location_for(ENV['BEAKER_VMPOOLER_VERSION'] || "~> 1")
-gem "rake", ">= 12.3.3"
-gem "multi_json", "~> 1.8"
-
-if File.exists? "#{__FILE__}.local"
-  eval(File.read("#{__FILE__}.local"), binding)
-end

data/acceptance/Rakefile

@@ -1,2 +0,0 @@
-require 'beaker-puppet'
-Beaker::DSL::Helpers::RakeHelpers.load_tasks

data/acceptance/bin/ci-bootstrap-from-artifacts.sh

@@ -1,55 +0,0 @@
-#! /usr/bin/env bash
-
-###############################################################################
-# Initial preparation for a ci acceptance job in Jenkins.  Crucially, it
-# handles the untarring of the build artifact and bundle install, getting us to
-# a state where we can then bundle exec rake the particular ci:test we want to
-# run.
-#
-# Having this checked in in a script makes it much easier to have multiple
-# acceptance jobs.  It must be kept agnostic between Linux/Solaris/Windows
-# builds, however.
-
-set -x
-
-# If $GEM_SOURCE is not set, fall back to rubygems.org
-if [ -z $GEM_SOURCE ]; then
-  export GEM_SOURCE='https://rubygems.org'
-fi
-
-echo "SHA: ${SHA}"
-echo "FORK: ${FORK}"
-echo "BUILD_SELECTOR: ${BUILD_SELECTOR}"
-echo "PACKAGE_BUILD_STATUS: ${PACKAGE_BUILD_STATUS}"
-
-rm -rf acceptance
-tar -xzf acceptance-artifacts.tar.gz
-cd acceptance
-
-mkdir -p log/latest
-
-echo "===== This artifact is from ====="
-cat creator.txt
-
-bundle install --without=development --path=.bundle/gems
-
-if [[ "${platform}" =~ 'solaris' ]]; then
-  repo_proxy="  :repo_proxy => false,"
-fi
-
-# If the platform is Windows, append $ruby_arch
-if [[ "${platform}" =~ 'win' ]]; then
-    platform="${platform}-${ruby_arch}"
-fi
-
-cat > local_options.rb <<-EOF
-{
-  :hosts_file => 'config/nodes/${platform}.yaml',
-  :ssh => {
-    :keys => ["${HOME}/.ssh/id_rsa-acceptance"],
-  },
-${repo_proxy}
-}
-EOF
-
-[[ (-z "${PACKAGE_BUILD_STATUS}") || ("${PACKAGE_BUILD_STATUS}" = "success") ]] || exit 1

data/acceptance/config/aio/options.rb

@@ -1,6 +0,0 @@
-{
-  :type => 'aio',
-  :pre_suite => [
-      'setup/aio/pre-suite/001_run_with_facter_ng.rb',
-  ],
-}

data/acceptance/config/git/options.rb

@@ -1,3 +0,0 @@
-{
-  :type => :git,
-}

data/acceptance/config/nodes/aix-53-power.yaml

@@ -1,7 +0,0 @@
----
-HOSTS:
-  pe-aix-53-acceptance:
-    roles:
-      - agent
-    platform: aix-5.3-power
-    hypervisor: none

data/acceptance/config/nodes/aix-61-power.yaml

@@ -1,7 +0,0 @@
----
-HOSTS:
-  pe-aix-61-acceptance:
-    roles:
-      - agent
-    platform: aix-6.1-power
-    hypervisor: none

data/acceptance/config/nodes/aix-71-power.yaml

@@ -1,7 +0,0 @@
----
-HOSTS:
-  pe-aix-71-acceptance:
-    roles:
-      - agent
-    platform: aix-7.1-power
-    hypervisor: none

data/acceptance/config/nodes/huaweios-6-powerpc.yaml

@@ -1,7 +0,0 @@
----
-HOSTS:
-  huawei-ce6850-2-debian-vm-eth0.ops.puppetlabs.net:
-    roles:
-      - agent
-    platform: huaweios-6-powerpc
-    hypervisor: none

data/acceptance/config/nodes/solaris-10-sparc.yaml

@@ -1,9 +0,0 @@
----
-HOSTS:
-  solaris-10-sparc:
-    roles:
-      - agent
-    platform: solaris-10-sparc
-    hypervisor: none
-    ip: 10.32.121.124
-    vmhostname: sol10-1.delivery.puppetlabs.net

data/acceptance/config/nodes/solaris-11-sparc.yaml

@@ -1,9 +0,0 @@
----
-HOSTS:
-  solaris-11-sparc:
-    roles:
-      - agent
-    platform: solaris-11-sparc
-    hypervisor: none
-    ip: 10.32.114.245
-    vmhostname: sol11-1.delivery.puppetlabs.net