> An interactive puppet shell: > https://github.com/lak/puppet/tree/prototype/master/puppet_shell > > The best tool I ever had for managing ldap directories was a simple, stupid > tool I wrote called ldapsh: http://search.cpan.org/dist/ldapsh/ . It wasn't > much of a shell (e.g., no autocomplete), but it was still 100x better than > the tools at the time. I've always wanted something similar in Puppet, so I > figured I'd give it a shot. > > The basic idea is that you'd treat the resource types as the top-level > directories, and you could cd around, look at resources, edit them, clone > them, or remove them. The reality isn't that nice, because not all resource > types play well with this -- e.g., you can't list file instances at all. > It's also just really obvious how much work it is to make an ok shell, and > you'd still just rather have bash or whatever. > > I think a FUSE filesystem would be fantastic for this, especially if it > supported connecting to other hosts, or even parallelizing across > mcollective, but this is more interesting experiment to make a point than > anything I'd recommend actually supporting.
This tool seems interesting - are we able to plugin-sync faces properly yet? Would be good to get this out into a module. At the very least it would be awesome for training purposes to teach people the power of the RAL, but beyond that it starts to get into the discussion we were having with Paul Anderson about his lcfg tooling that drives his components. I'm fascinated by the idea that not only should Puppet be useful for setting policy, but perhaps for providing cross-platform real time control on the CLI and this certainly asserts that some more. ken. -- 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.
