Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-8684

Allow overriding Facter config (specifically external facts dir) when calling Puppet

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Normal
    • Resolution: Duplicate
    • None
    • None
    • None
    • Hide

      `puppet facts --external-facts-dir=/tmp/example --debug` should load external facts from /tmp/example rather than the normal locations. All other puppet applications which make use of Facter should follow suit.

      Alternatively, an environment variable instead of a command line flag would also be acceptable, though personally I think the command-line flag is preferable.

      Show
      `puppet facts --external-facts-dir=/tmp/example --debug` should load external facts from /tmp/example rather than the normal locations. All other puppet applications which make use of Facter should follow suit. Alternatively, an environment variable instead of a command line flag would also be acceptable, though personally I think the command-line flag is preferable.
    • Night's Watch
    • Needs Assessment

    Description

      Currently when calling puppet (e.g `puppet facts`) you can override the directory from which custom facts in ruby are loaded (using the `--factdir` flag or the FACTERLIB environment variable), however it does not appear to be possible to customize the location from which external facts are loaded other than by editing facter.conf.

      When calling `facter` directly as a command line tool, you can of course specify the `--external-dir` flag at the command line, but there is no equivalent flag when calling `puppet facts` (or `puppet agent`, `puppet catalog`, etc), nor is there an environment variable you can set to achieve this end.

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              adam.gardner Adam Gardner
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support