Well, I suppose it's perfectly valid to write a propellor property puppetClient PuppetConfig :: Property So if propellor's capabilities for (re)installing a s

Well, I suppose it's perfectly valid to write a propellor property puppetClient PuppetConfig :: Property So if propellor's capabilities for (re)installing a system are why you want to use it, it can be composed with other configuration management tools this way. Of course, I wrote propellor because I've read enough puppet and chef and ansible and salt documentation that I knew it would be easier to write my own tool that I fully understood and worked just the way I wanted, rather than learning those rest well enough to pick one, and then mangle it to behave the way I wanted. Quite aware that only solves the problem for me. ;)