On Wednesday, April 8, 2015 at 6:05:56 AM UTC+12, varun umesh wrote:
>
> Hello Lupin-
>
> Thank you for the update! Could you point me for any article, so that i
> can take a look at how exactly it could be done.
>
> Thanks!
>
> -varun
>
Hi,
I can't find any link but I won't be just treat it as normal puppet
resource if you can create a type/provider for it would be better else you
just sort to 'exec' resource.
E.g if you go for exec route
exec { 'call_to_api':
command => 'curl -X -H url'
x...x
}
Hth,
Lupin
>
> On Monday, 6 April 2015 20:38:29 UTC-7, [email protected] wrote:
>>
>>
>>
>> On Tuesday, April 7, 2015 at 8:09:41 AM UTC+12, varun umesh wrote:
>>>
>>> I am planning to use puppet for the configuration of a custom network
>>> appliance. My main problem is i am unable to install puppet on the
>>> appliance, as it is not supported. I have access to the rest api's exposed
>>> by the appliance. So can i use puppet to make the rest api calls and try to
>>> do the configurations as and when a parameter changes? Could anybody
>>> suggest me a good way to handle this problem?
>>>
>>> Thanks!
>>>
>>
>> Hello,
>>
>> You can use a slave node ( which you can install Puppet and attached the
>> module ), your module will do the call to ReST API of your appliance.
>>
>> Cheers
>> Lupin
>>
>
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/db44ffff-883d-4c4c-af2b-cc185b3df3b5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
