Hey Martin, Well, the main reason we didn't go the hammer route is that we didn't speak ruby:) Also, since everything is exposed via the API (although not always as consistent as I would like, but that's another story/topic), it is pretty easy to make "clean" tools. So besides the implementation language we don't really have a reason (I cannot say anything positive or negative about the modularity of hammer, but I expect that it would be easy to extend it).
Our only alternative was to make feature requests for hammer and hope someone picks them up since we do not have the knowledge of extending it ourselves. Looking at it this way, we figured we might as well write something ourselves that may be of use to other people. I am aware that "We do not master the language the primary tool is written in, so we reinvented the wheel" is not really the most solid of reasons, but it *is* useful and we do not aim to replace hammer (that would be pretty stupid and unfeasible), only provide functionality that hammer does not. Cheers, Yoram On Wednesday, June 15, 2016 at 10:03:22 AM UTC+2, Martin Bačovský wrote: > > Hey Yoram, > > Ballista seems to add useful features. I'm curious what were the reasons > besides the implementation language to not to add this features to > hammer-cli-katello or as a new hammer plugin. If you were considering this > option what were the blockers or biggest pain points that hold you back > from extending Hammer? What can we improve to make it easier to create new > hammer extensions? > > Regards, > Martin > > > > On Wed, Jun 15, 2016 at 8:39 AM, Yoram Hekma <[email protected] > <javascript:>> wrote: > >> Hey all, >> >> I just wanted to show you all a project I and a colleague of mine have >> been working on and has just been added to the "official" Red Hat >> supplemental scripts group on Github. You can find it at >> https://github.com/RedHatSatellite/ballista >> >> Ballista is a tool (so far) primarily aimed at Katello and aims to be a >> supplement to hammer. It started as a tool to recursively publish content >> views and their composites, but it has started growing into a more >> modularized (?) thing that is easily extendable via modules. The >> documentation is not yet up to snuff, but it is actively maintained (and >> used in production environments) and pull requests are always welcome. >> >> Cheers, >> Yoram >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > > -- You received this message because you are subscribed to the Google Groups "foreman-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
