In general, I would agree. But enterprises often have limiting factors that
make rewriting/redesign very difficult. Also, IMHO newer Puppet users can
understand function creation a lot easier than building out custom
resources and types.
Facts work well for a lot of use cases, but as mentioned earlier they can
quickly become a dumping ground and get out of control. Also, in an
enterprise environment you could find yourself needing to access sensitive
data on disk thats managed by another individual or group who hasn't got
around to putting things in Puppet or a secrets management solution and
you'd probably want to avoid exposing the data as a Fact. Using Deferred to
extract and use the data without having to know what it is would be helpful
in that case.
On Friday, August 31, 2018 at 12:07:43 PM UTC-4, Luke Bigum wrote:
>
> On Friday, 31 August 2018 16:41:34 UTC+1, Chadwick Banning wrote:
>>
>> So for this example, there are some sort of limitations as to what the
>> 'vault_lookup' function is able to do internally? I had just assumed that
>> as long as the function returned a simple value, what the function does
>> internally was open.
>>
>> As an example, could Deferred be used to read and extract a value from a
>> file agent-side?
>>
>
>
> In theory, you probably could. The ruby code probably just executes on
> the Agent. Personally though if I were to find myself in this situation,
> I'd really think about what I was trying to achieve and why I am in this
> situation in the first place... Perhaps it's Puppet design that needs to
> be refactored, or if I really wanted to "do" something on an Agent, a
> Custom Type / Provider might be a better vehicle.
>
> I can partially see the argument in proceeding posts for making decisions
> on run time environment data... I'd argue that if you're writing a
> Deferred Type in Ruby, it's not that much further to write a Fact. Also,
> unit and acceptance testing code that relies on a run time Fact seems very
> difficult.
>
>
> On Fri, Aug 31, 2018 at 9:12 AM R.I.Pienaar <r...@devco.net> wrote:
>>
>>>
>>>
>>> On Fri, 31 Aug 2018, at 15:03, Chadwick Banning wrote:
>>> > Would it be safe to consider this in a general context i.e. as
>>> enabling
>>> > agent-side function execution?
>>>
>>> I dont think so - for general function calls to be usable you want to
>>> get the value and then do some conditional logic on it. or put it in a
>>> variable and use it in another resource etc.
>>>
>>> That is not what this is for, this is a based placeholder to later be
>>> replaced by the value - you cannot do any conditionals etc with it.
>>>
>>> Imagine something like:
>>>
>>> mysql::user{"bob":
>>> password => Deferred(vault_lookup, "bob_pass")
>>> }
>>>
>>> (I am just making this syntax up, this is presumably not how it will
>>> look)
>>>
>>> Here its fine because its a simple interpolation into a value, you cant
>>> do more complex things with this design.
>>>
>>> Anyway thats my understanding, Henrik might chime in too
>>>
>>> --
>>> You received this message because you are subscribed to a topic in the
>>> Google Groups "Puppet Users" group.
>>> To unsubscribe from this topic, visit
>>> https://groups.google.com/d/topic/puppet-users/DurqiLnVWMk/unsubscribe.
>>> To unsubscribe from this group and all its topics, send an email to
>>> puppet-users...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/puppet-users/1535721137.3301091.1492516568.3EB7087A%40webmail.messagingengine.com
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>> --
>> Chadwick Banning
>>
>
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/4ea5713d-7493-4313-ab16-185d2e7a4ffe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
