Transaction style resources

[juliogu...@gmail.com]

Hi all,

Currently I'm working of implementing some puppet types and providers that will talk with a RESTful API that support transaction style queueing of requests.

Just like in SQL you can BEGIN a transaction, put a lot of changes on the transaction and COMMIT all of them as a single unit.

I have implemented custom types and providers before, but have never come across cases like this.

Does anybody has some examples of something similar to this?

Does puppet can even support this type of workflow?

Any idea, suggestion, tip is more than welcome!

Julio

[David Schmitt]

The Palo Alto module is a good example for talking to an API. It also contains panos_commit which activates all collected config changes that were already uploaded to the device. That's maybe not exactly what you're looking for, but it's the closest example I have.

--
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...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/7a5f12a8-8442-4d9b-92f4-56e0ea6607c5n%40googlegroups.com.