for example, puppetlabs_spec_helper already defines rake tasks, which are essentially an interface

Be that as it may, fix the PDK. Don’t punis the users.

they could be considered a UI, but also an API

I’ve got one client with 26,000 field machines, nearly half of which are Macs, for instance. You may not have a use for Macs, but thousands out here do.

ok, gtg.. I see new comments in my PR and will update it later today 🙂

Have a great day, Yury

I think you misunderstood me: when I say "I have no use for ____" I don't mean it should be dropped, but rather that I don't see a reason to use it

Well, there’s 13,000 reasons right there. 😄

I really don't see your point

if I've never used a Mac and I don't know Mac specifics, why would I bother adjusting my workflows?

I’m the same way, by the way. I get focused on what I’m doing for a client, and I get into “I only need this thing in this case…. I have no use for ____” I have to stop myself, circle back and say… “I’f I’m going to write a tool that does FEATURE, then “feature” is the product, and I should try and make it for $allthethings instead of one target platform. And given the route of the Forge, I would use PDK even if it’s a little annoying for me because it’s the common practice.

This message was deleted.

It’s like…. take SSH

There’s a number of SSH modules out there.

which is why I'm often arguing that something that's now implemented in PDK should be split of into smaller components that can be reused elsewhere

take for example the code that inspects the generated changelog and recommends a version bump (major/minor/patch): we want to use the same thing in our gem development, but PDK can't work with gems

if it was split off into a smaller component (that PDK would include), it could be reused

Now, let’s say I’m a FreeBSD user who has cracked SSH, and for the sake of argument, I want to publish my toolset. I’m more than likely going to engage saz over at sazz-ssh, and start doing pulls to add platforms instead of developing an entirely new (yet another) module that will eventually die in the Forge, and come to Vox

See, here’s where my not being a Ruby dev comes into play

and I'm not paid to support clients - I just need various tooling for my workflows so I make sure my needs are covered

I usually update a Gemfile and then do

pdk bundle install

that classifies as “working with Gems” for those who aren’t career Ruby devs.

I mean, I support both RHEL and Ubuntu. I loathe and do not use Ubuntu, but I support it. It’s more because I’m focused on what my tool does than who it’s for, I guess.

Unfortunately, I work for the government, so…. I can’t even share the tools I make, so this is an entirely academic conversation. LOL

btw, the primary reason I refuse to use PDK now is that it does analytics by default and I want to boycot tools that do that

that I don't see a further benefit is all secondary

and yes, I know that puppetserver does it too now, but boycotting that sort of implies leaving the Puppet ecosystem

indeed

I know that I for one won’t use Forge modules that don’t have the PDK tag any more. It takes a lot for me to stray off the beaten path now.

that excludes all of Vox Pupupli's modules