Jira (FACT-1458) Allow setting existing facter config flags from the config file

2 views
Skip to first unread message

Branan Riley (JIRA)

unread,
Jul 11, 2016, 6:46:03 PM7/11/16
to puppe...@googlegroups.com
Branan Riley created an issue
 
Facter / New Feature FACT-1458
Allow setting existing facter config flags from the config file
Issue Type: New Feature New Feature
Assignee: Unassigned
Created: 2016/07/11 3:45 PM
Priority: Normal Normal
Reporter: Branan Riley

Main:
[no]-custom-facts
[no]-external-facts
[no]-ruby

Cli:
debug
trace
verbose
log-level

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Atlassian logo

Maggie Dreyer (JIRA)

unread,
Jul 13, 2016, 7:11:07 PM7/13/16
to puppe...@googlegroups.com
Maggie Dreyer commented on New Feature FACT-1458
 
Re: Allow setting existing facter config flags from the config file

Do we want these fields to match the command-line args exactly? I've noticed we're not super consistent with the formatting (in Puppet in particular) between config file, command line, and internal settings, let alone from setting to setting, but I feel like that's something we could improve in Facter, given this chance to be deliberate about it. Even if we want to differ between command-line and config file formatting, we should at least be consistent within each of these sources.

Does anyone have a problem with dash-separated across the board?

Steve Barlow (JIRA)

unread,
Jul 15, 2016, 1:21:02 PM7/15/16
to puppe...@googlegroups.com
Steve Barlow updated an issue
 

Added the client scrum team to this ticket since it is assigned to Brannan and is in a client sprint.

Change By: Steve Barlow
Scrum Team: Client Platform

Branan Riley (JIRA)

unread,
Jul 15, 2016, 1:26:05 PM7/15/16
to puppe...@googlegroups.com
Branan Riley commented on New Feature FACT-1458
 
Re: Allow setting existing facter config flags from the config file

Thanks, that was an oversight when we filed this!

On Fri, Jul 15, 2016 at 10:21 AM Steve Barlow (JIRA) <

Maggie Dreyer (JIRA)

unread,
Jul 21, 2016, 12:36:08 PM7/21/16
to puppe...@googlegroups.com

Kylo Ginsberg (JIRA)

unread,
Jul 27, 2016, 12:20:14 PM7/27/16
to puppe...@googlegroups.com
Kylo Ginsberg updated an issue
Change By: Kylo Ginsberg
Sprint: Client 2016-07-27 , Client 2016-08-10

Phong Ly (JIRA)

unread,
Jul 27, 2016, 7:26:08 PM7/27/16
to puppe...@googlegroups.com
Phong Ly updated an issue
Change By: Phong Ly
QA Risk Assessment Reason: New feature
QA Risk Assessment: High
QA Status: Reviewed

David Kramer (JIRA)

unread,
Aug 1, 2016, 1:00:05 PM8/1/16
to puppe...@googlegroups.com

Hailee Kenney (JIRA)

unread,
Aug 5, 2016, 7:26:04 AM8/5/16
to puppe...@googlegroups.com
Hailee Kenney assigned an issue to qa
Change By: Hailee Kenney
Status: Ready for  CI  Test
Assignee: qa

Eric Thompson (JIRA)

unread,
Aug 8, 2016, 2:42:08 PM8/8/16
to puppe...@googlegroups.com

Eric Thompson (JIRA)

unread,
Aug 8, 2016, 2:43:06 PM8/8/16
to puppe...@googlegroups.com
Eric Thompson updated an issue
Change By: Eric Thompson
QA Highest Test Level: Acceptance

Eric Thompson (JIRA)

unread,
Aug 8, 2016, 2:43:22 PM8/8/16
to puppe...@googlegroups.com
Eric Thompson updated an issue
Change By: Eric Thompson
QA Highest Test Level Reason: covered via test in the PR

Eric Thompson (JIRA)

unread,
Aug 8, 2016, 2:44:08 PM8/8/16
to puppe...@googlegroups.com
Eric Thompson commented on New Feature FACT-1458
 
Re: Allow setting existing facter config flags from the config file

Phong Lyif this is covered via a testrail testcase, please provide a reference to this ticket in it. it can also be set to automated.

Maggie Dreyer (JIRA)

unread,
Aug 10, 2016, 12:18:08 PM8/10/16
to puppe...@googlegroups.com
Maggie Dreyer updated an issue
 

This will currently load the config file from its default location (/etc/puppetlabs/facter/facter.conf) on Unix systems, but Windows will require specifying the path to the file using the command line flag `--config`.

Change By: Maggie Dreyer
Release Notes Summary: This adds support for a HOCON config file for Facter, which has fields for certain global settings that can currently only be set from the command line. These come in two groups: global, which contains settings for fact directories and ruby, and cli, which contains fields for configuring command line output.
Release Notes: New Feature

Sean Griffin (JIRA)

unread,
Aug 17, 2016, 7:08:03 PM8/17/16
to puppe...@googlegroups.com

Claudia Petty (Jira)

unread,
Jun 21, 2023, 8:44:05 AM6/21/23
to puppe...@googlegroups.com
Claudia Petty updated an issue
Change By: Claudia Petty
Labels: new-feature
This message was sent by Atlassian Jira (v8.20.21#820021-sha1:38274c8)
Atlassian logo
Reply all
Reply to author
Forward
0 new messages