On Wed, 2 Mar 2016, Trevor Vaughan wrote:
R.I., did I just hear you make a suggestion for writing fact DDL files? Not
sure how I feel about that, they're a pain to deal with and confuse users.
The features that I would like to add my vote for:
* Fact TTLs
* Custom fact execution timeouts
* Fac
On Tue, 1 Mar 2016, Eric Sorenson wrote:
I've been thinking about a config file for Facter, which has historically
not been run-time configurable.
A little thread necromancy here, as I finally got back to this and started
working into a real proposal as Puppet RFC 24, Facter Config File. WIP
> On 2 Mar 2016, at 21:16, Trevor Vaughan wrote:
>
> R.I., did I just hear you make a suggestion for writing fact DDL files? Not
> sure how I feel about that, they're a pain to deal with and confuse users.
Not specifically. Types already have doc strings similar would be enough for
this.
>
R.I., did I just hear you make a suggestion for writing fact DDL files? Not
sure how I feel about that, they're a pain to deal with and confuse users.
The features that I would like to add my vote for:
* Fact TTLs
* Custom fact execution timeouts
* Fact execution timeouts
* Fact parallelization (
> 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 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
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
12 matches
Mail list logo
