But we’re talking the days of Puppet 2.7-3.3

Add to that the neat little dashboard in PuppetDB, and for small company (say, less than 100 nodes), it was FINE. You were never going to get the little guys to buy PE any way you slice it. Seems like now with OSP support contracts for the “little guy”, tools like this would be a HUGE benefit to the community rather than having to hack together either ENC scripts or Hiera methods of classification.

In fact, at some point the sample ENC script that used to be in the Puppet documentation disappeared, and you can’t find it any more. You have to go to the old documentation archive and hunt for it there.

One of my friends was saying the same.. OSS Puppet needs some small and easy-to-start-with ENC (which is integrated well with Puppet Bolt ideally)

I struggle to see a usecase for an ENC in small/simple environments

you usually already have hiera for something. write a few lines of puppet code to map classes from hiera to a node. or embed the role name in the client certificate

Yeah, but how many clients are you going to serve this year? I have plenty of folks who really can’t be trusted to edit their YAML, nor should they be in the site.pp for any reason, but write the HELL out of DSL. If they don’t want to retain me for every little node change (expensive), giving them simple interfaces to classify with is a better scenario. You have to be STUPID meticulous with roles/profiles, and have a profile for every time you sneeze, but when all they have to do is cobble together the legos in the GUI, it makes life considerably better for everyone.

usecase is to move nodes across groups (== role) with mouse 🙂

usecase is to move nodes across groups (== role) with mouse 🙂

Still, you have to have the interface to apply those roles to the apporpriate ndoes

some very minimal tool that queries the Puppetserver API for classes and environments shouldn't be that hard, but I have no interest in writing that

And as an old BOFH, every time some sort of ENC GUI would come out, it seemed like it was UNNECESSARILY obtuse, or had some obnoxious set of underlying language requirements that broke every time the underlying OS changed…like at all. Back in the day I was able to make one of these out of freaking Perl-CGI. You’d think that with all the talented devs around here that a simple interface shouldn’t require 37 libraries, all of which trail OS upgrades by sometimes months, and require some guy in rural Iowa or subsaharan Africa with only 3 minutes of upload time a month to get their code into Git via carrier pigeon.

And before you call me out for carrier pigeon as hyperbole, here’s the RFC: https://www.rfc-editor.org/rfc/rfc2549

That’s right. IP over Avian Carrier with QoS

Underscore (

_

) is allowed in module name, right?.. 🤔 I’m debugging strange issue when BoltSpec cannot find a plan

This message was deleted.

we use that for customers... not so familiar with hiera or yaml or vim or computers

@Yury Bushmelev yeah, underscore is ok. hyphens are a no-no

same with variable names… you can get into weirdness with hyphens there too

ty.. then it’s not the case 🤔

Rails <3

we laos have https://github.com/voxpupuli/puppet-hdm to deploy it

that seems to have the most promise. Thanks for that… bookmarked and will look into. I still get to hate supporting Rails, though.

buy can buy a support contract if you like :P

it's not that easy to implement the different lookups and identify hiera data that's used on a node, or identify parameters that you could set

I do think Rails is quite heavy and I'd have considered https://github.com/sinatra/sinatra

that's a bit of logic and writing that without a framework gets really ugly really quickly. and since most of the puppet ecosystem is ruby, rails felt most natural

yeah dito

sinatra would have been the alternative

but writing any web app without a framework today is something I wouldn't even touch