On Tuesday, 11 September 2012 22:25:16 UTC+1, Daniel Pittman wrote:
>
> On Tue, Sep 11, 2012 at 2:16 PM, Kayode Odeyemi
> >
> wrote:
> >> That doesn't actually map super-well to the design of Puppet, since it
> >> doesn't instantly react to change, it reacts on a schedule. You can
> >> obviou
On Tue, Sep 11, 2012 at 2:16 PM, Kayode Odeyemi wrote:
>> That doesn't actually map super-well to the design of Puppet, since it
>> doesn't instantly react to change, it reacts on a schedule. You can
>> obviously make the latency low by running all the time, but it is
>> still non-zero.
>>
>> The
>
> That doesn't actually map super-well to the design of Puppet, since it
> doesn't instantly react to change, it reacts on a schedule. You can
> obviously make the latency low by running all the time, but it is
> still non-zero.
>
> The things you want to do are also not done by talking dir
On Tue, Sep 11, 2012 at 12:22 PM, Kayode Odeyemi wrote:
> On Tuesday, 11 September 2012 19:35:27 UTC+1, Daniel Pittman wrote:
>> On Tue, Sep 11, 2012 at 11:16 AM, Kayode Odeyemi wrote:
>>
>> > I will like to have puppet agent as WSDL service that can be consumed
>> > from
>> > an external applica
On Tuesday, 11 September 2012 19:35:27 UTC+1, Daniel Pittman wrote:
>
> On Tue, Sep 11, 2012 at 11:16 AM, Kayode Odeyemi
> >
> wrote:
>
> > I will like to have puppet agent as WSDL service that can be consumed
> from
> > an external application. I want to be able to have access to puppet
> ag
On Tue, Sep 11, 2012 at 11:16 AM, Kayode Odeyemi wrote:
> I will like to have puppet agent as WSDL service that can be consumed from
> an external application. I want to be able to have access to puppet agents
> via some URL from an external application.
We don't provide any WSDL descriptions of
