> On 2 Mar 2016, at 03:45, Kylo Ginsberg wrote:
>
>> On Tue, Mar 1, 2016 at 3:13 PM, R.I.Pienaar wrote:
>>
>>
>>> On 1 Mar 2016, at 19:52, Eric Sorenson wrote:
>>>
>>> I've been thinking about a config file for Facter, which has historically
>>> not been run-time configurable.
>>>
>>> The
On Fri, Feb 5, 2016 at 12:02 AM, R.I.Pienaar wrote:
> hello,
>
> Thanks for the replies, think I'll reply to both in one go
>
> - Original Message -
> > From: "Luke Kanies"
> > To: "puppet-dev"
> > Sent: Friday, February 5, 2016 6:15:28 AM
> > Subject: Re: [Puppet-dev] metaparam questio
On 01/03/16 19:52, Eric Sorenson wrote:
I've been thinking about a config file for Facter, which has
historically not been run-time configurable.
The two problems in front of me that seem applicable are:
* Sometimes, certain facts are just plain bad to collect and users would
like to prevent th
On Tuesday, March 1, 2016, Kylo Ginsberg wrote:
>
> Does 'facter -p my_custom_fact' do the trick here?
>
In my case, it's while developing the fact, prior to distribution. Takes
some trickery to rig it up for testing.
> Ah yeah, I've heard this a few times as well. But why is it more of a
> thi
On Tue, Mar 1, 2016 at 3:13 PM, Rob Nelson wrote:
> On Tuesday, March 1, 2016, Matthew Gaspar wrote:
>
>> The only problem I sometimes encounter, which may be a usage issue on my
>> part, is when creating custom facts sometimes it'd be nice to just run
>> `facter my_custom_fact` to get the outpu
On Tue, Mar 1, 2016 at 3:13 PM, R.I.Pienaar wrote:
>
>
> On 1 Mar 2016, at 19:52, Eric Sorenson
> wrote:
>
> I've been thinking about a config file for Facter, which has historically
> not been run-time configurable.
>
> The two problems in front of me that seem applicable are:
>
> * Sometimes,
On Tuesday, March 1, 2016, Matthew Gaspar wrote:
> The only problem I sometimes encounter, which may be a usage issue on my
> part, is when creating custom facts sometimes it'd be nice to just run
> `facter my_custom_fact` to get the output. If there would be some way to
> register custom facts s
> On 1 Mar 2016, at 19:52, Eric Sorenson wrote:
>
> I've been thinking about a config file for Facter, which has historically not
> been run-time configurable.
>
> The two problems in front of me that seem applicable are:
>
> * Sometimes, certain facts are just plain bad to collect and users
> On Mar 1, 2016, at 12:25 PM, Matthew Gaspar wrote:
>
> A config file for facter is intriguing to me.
>
> Would this solely be used to change behaviors when running facter, or do you
> see some potential for defining some facts within the config itself?
I think it'd be only settings/behavior
On Tue, Mar 1, 2016 at 12:25 PM, Matthew Gaspar wrote:
> A config file for facter is intriguing to me.
>
> Would this solely be used to change behaviors when running facter, or do
> you see some potential for defining some facts within the config itself?
>
I'd rather not mix config with content.
A config file for facter is intriguing to me.
Would this solely be used to change behaviors when running facter, or do
you see some potential for defining some facts within the config itself?
Also, would you move facter specific configs into this facter.conf instead
of being managed from the pu
I've been thinking about a config file for Facter, which has historically
not been run-time configurable.
The two problems in front of me that seem applicable are:
* Sometimes, certain facts are just plain bad to collect and users would
like to prevent them from even being resolved (see FACT-71
Sorry for the late notice! Please feel free to join us for the weekly pull
request triage:
http://links.puppetlabs.com/pr-triage
--
Hailee Kenney
hai...@puppetlabs.com
Software Developer, Puppet Labs
--
You received this message because you are subscribed to the Google Groups
"Puppet Developer
13 matches
Mail list logo
