github/facter
Watch
1
0
Fork
You've already forked facter
 0
mirror of https://github.com/github/facter synced 2026-07-21 03:23:43 +00:00
Code Issues Projects Releases Packages Wiki Activity
No description
3,046 commits 6 branches 116 tags 5.6 MiB
  • Ruby 98.1%
  • HTML 1.6%
  • Shell 0.2%
Find a file
Exact
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Kylo Ginsberg 38d8119108 Revert "(FACT-658) facter doesn't parse gnu uptime output" 
This reverts commit b8ea20db68.

After some discussion with Josh Cooper, we agreed that relying
on the exact path to uptime for all platforms is the wrong approach,
so we're reverting.

Two possibilities are:
1) Set the exact path to uptime for Solaris only
2) Make the uptime parsing resilient to gnu uptime output
2014-11-17 20:25:47 -08:00
acceptance (maint) fix filename for acceptance sshkey 2014-11-07 10:57:45 -08:00
bin (FACT-480) Remove current directory from Ruby load path. 2014-05-06 14:28:08 -07:00
documentation (FACT-472) Sync facter-2 branch to master 2014-07-07 16:49:33 -07:00
etc (FACT-472) Sync facter-2 branch to master 2014-07-07 16:49:33 -07:00
ext (PUP-3479) Update ffi to ~1.9.5 2014-10-24 10:55:16 -07:00
lib Revert "(FACT-658) facter doesn't parse gnu uptime output" 2014-11-17 20:25:47 -08:00
libexec/ext (#2157) add readme for libexec external facts 2012-06-15 14:48:41 -07:00
man/man8 (FACT-272) Update manpage based on facter --help 2014-02-24 14:06:05 -08:00
schema Merge branch 'stable' 2014-10-09 17:29:50 -05:00
spec Revert "(FACT-658) facter doesn't parse gnu uptime output" 2014-11-17 20:25:47 -08:00
tasks (FACT-472) Sync facter-2 branch to master 2014-07-07 16:49:33 -07:00
.autotest (#6610) Fix Autotest proper run 2011-09-06 16:07:23 -07:00
.gemspec (FACT-472) Sync facter-2 branch to master 2014-07-07 16:49:33 -07:00
.gitignore (maint) ignore .idea folder 2014-07-14 14:11:57 -05:00
.mailmap (maint) Add mailmap for git shortlog 2012-10-18 16:16:54 -07:00
.noexec.yaml (#15464) Make contributing easy via bundle Gemfile 2012-08-16 23:20:22 -07:00
.rspec (FACT-472) Sync facter-2 branch to master 2014-07-07 16:49:33 -07:00
.travis.yml (FACT-653) Cherry-pick lost update on supported Ruby versions back into master 2014-08-13 15:37:24 -07:00
.yardopts Document Facter API with YARD 2013-12-20 12:56:57 -08:00
COMMITTERS.md Revert "(maint) Update docs to reflect use of facter-2 branch" 2014-07-07 16:52:10 -07:00
CONTRIBUTING.md (doc) facter.json schema 2014-10-09 17:27:11 -05:00
Gemfile (PUP-3479) Update ffi to ~1.9.5 2014-10-24 10:55:16 -07:00
install.rb (FACT-321) Remove ENV['DESTDIR'] and --test from install.rb 2014-02-10 10:02:08 -08:00
LICENSE (maint) Update copyright year in LICENSE 2014-10-01 15:34:49 -07:00
Rakefile (FACT-472) Sync facter-2 branch to master 2014-07-07 16:49:33 -07:00
README.md (FACT-653) Doc update for supported Ruby Version cherry-pick 2014-08-13 15:37:35 -07:00

README.md

Facter

This package is largely meant to be a library for collecting facts about your system. These facts are mostly strings (i.e., not numbers), and are things like the output of uname, public ssh keys, the number of processors, etc.

See bin/facter for an example of the interface.

Installation

Generally, you need the following things installed:

  • A supported Ruby version. Ruby 1.8.7, 1.9.3, and 2.0.0 (at least p195) are fully supported.

Running Facter

Run the facter binary on the command for a full list of facts supported on your host.

Adding your own facts

See the Adding Facts page for details of how to add your own custom facts to Facter.

Running Specs

  • bundle install --path .bundle/gems
  • bundle exec rake spec

Note: external facts in the system facts.d directory can cause spec failures.

Further Information

See http://www.puppetlabs.com/puppet/related-projects/facter for more details.

Support

Please log tickets and issues at our JIRA tracker. A mailing list is available for asking questions and getting help from others. In addition there is an active #puppet channel on Freenode.

We use semantic version numbers for our releases, and recommend that users stay as up-to-date as possible by upgrading to patch releases and minor releases as they become available.

Bugfixes and ongoing development will occur in minor releases for the current major version. Security fixes will be backported to a previous major version on a best-effort basis, until the previous major version is no longer maintained.

For example: If a security vulnerability is discovered in Facter 2.1.0, we would fix it in the 2 series, most likely as 2.1.1. Maintainers would then make a best effort to backport that fix onto the latest Facter 1.7 release.

Long-term support, including security patches and bug fixes, is available for commercial customers. Please see the following page for more details:

Puppet Enterprise Support Lifecycle