On Aug 26, 2008, at 2:06 PM, Francois Deppierraz wrote:

>
> Luke Kanies wrote:
>
>> As Adam said, the "right" way to do this right now is to create the
>> resources and add them to the parser's resource graph, or -- and more
>> preferably -- use ActiveRecord to add them to the db and then use a
>> collection to query them out.  See below.
>
> Thanks, I'll give a try to the ActiveRecord way.
>
> However, my first aim was to take advantage of the parser to make  
> remote
> sources accessible -- as easily as possible -- from the Puppet  
> language
> without using any external script.
>
> But the export/collection interface going through the Indirector, as
> your described, looks promising and is definitely much cleaner.
>
>> My goal is for the export and collection interface to go through the
>> Indirector at some point, which would make it straightforward to add
>> whatever kind of backend repository you wanted, but we're likely a
>> ways out on that.
>
> Will resources merging from multiple backends into the same catalog be
> possible (ie, plain text files and a database at the same time) ?

I think so.

>
> By the way, I'm still interested in this eval function. I'm not sure
> it's going to be useful but it's still an interesting hack.

Ok.  You can look at the puppet executable for an idea on how to parse  
stand-alone code, although you'd need to pull the resulting catalog  
and connect it with the current catalog.

-- 
A government that robs Peter to pay Paul can always depend on the
support of Paul. -- George Bernard Shaw
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Puppet Developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/puppet-dev?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to