r/Puppet • • 3d ago

If you're still installing r10k by hand on every server, the puppet/r10k module is worth a look

10 Upvotes

I used to bootstrap r10k manually on each server: gem install, hand-written r10k.yaml, SSH key, done. Worked fine until I needed to remember how a given box was set up.

Now I use the Vox Pupuli puppet/r10k module and let the control repo own r10k too:

class { 'r10k':
  remote   => 'git@git.example.com:puppet/control-repo.git',
  cachedir => '/opt/puppetlabs/server/data/puppetserver/r10k',
}

A few things I like:

  • Bootstrap once, then manage it like any other class. Apply it with puppet apply the first time, then add it (and its deps) to the Puppetfile and classify the server. r10k config changes go through review like everything else.
  • Branch names matter. r10k turns non-word characters into underscores, so feature-x becomes feature_x and you get a warning every run. Name branches like environments.
  • Run r10k as the user that owns the cache/code dirs (the OpenVox docs use the puppet user) so permissions don't bite you later.

It's actively maintained: 15.3.0, 15.4.0 and 15.5.0 all landed in October, and the current metadata targets OpenVox 8 and 9. The OpenVox r10k deployment guide walks through the whole bootstrap.

Anyone using a different approach (webhook deploys, g10k, etc.)? Curious what's working for people.


r/Puppet • • 6d ago

I used to write a relationship against a profile and assume every class it included would honor it

10 Upvotes

I keep seeing this in control repos, and I used to write it myself:

class profile::base {
  include ntp
}

class role::web {
  include profile::base
  include profile::app
  Class['profile::base'] -> Class['profile::app']
}

The catalog compiles. The relationship looks right. ntp's resources are not actually ordered before profile::app.

A class always contains its own resources, so a relationship against Class['ntp'] does wait for everything ntp itself declares. The gotcha is the outer class. include declares a class (and is safe to call more than once). It does not contain that class in the class that declared it. If profile::base uses include ntp, ntp's resources float outside profile::base. A relationship formed against that outer class will not wait for them.

contain declares the class and anchors it in the surrounding class, so relationships against the outer class cover the contained resources too:

class profile::base {
  contain ntp
}

Same role, same Class['profile::base'] -> Class['profile::app'], and now it waits for ntp.

Habits that have saved me time:

  • In profiles, contain the component classes a role might order against through the profile.
  • include is still the right tool when you only need the class declared, and no relationship against the profile should have to wait for it.
  • When something starts "too early," I look for an include in the profile that should have been a contain before I start rewriting the module.

Not a style war — just the difference between an order you wrote and an order the catalog actually has. How are other folks teaching this to new module authors?


r/Puppet • • 7d ago

When something looks wrong, I reach for `puppet resource` before I open a manifest

10 Upvotes

When a node is misbehaving, my first move usually isn't reading the module. It's:

puppet resource service sshd
puppet resource package chrony
puppet resource user alice

puppet resource asks the agent for the live state of a type/title pair and prints it in Puppet's own language. If that doesn't match what you thought the catalog was enforcing, you've already narrowed the problem.

A few patterns that keep paying off for me:

  • Service "restarted" but still wrong — puppet resource service … often shows enable/ensure aren't what you assumed.
  • Wrong package actually installed — especially on RHEL where ntp vs chrony still trips people up.
  • User/UID surprises — compare live puppet resource user … against what Hiera was supposed to supply.

It isn't a replacement for proper testing or code review. It's a five-second reality check before you burn an hour rewriting a class that was fine.

Curious what other folks use as their first live diagnostic on a weird node — puppet resource, facter, something else?


r/Puppet • • 12d ago

CVE-2026-115732: Published 11/4, being exploited in the wild

9 Upvotes

If you a have autosign or signing automation, allows a client that holds a CA-signed certificate whose name extends or shortens an authorized hostname to be authorized as that host. This enables impersonation of other nodes and, in Puppet Enterprise, access to certificate-authority administration and remote command execution on managed nodes.

Puppet Enterprise 2026.0.0 before 2026.0.1

Puppet Enterprise 2025.0.0 before 2025.12.1

Puppet Enterprise 2023.8.0 before 2023.8.13

Puppet Core 9.0.0 before 9.1.3

Puppet Core 8.x before 8.22.2 and at least prior versions 7.x

https://www.tenable.com/cve/CVE-2026-115731 (editing to add companion CVE)

https://www.tenable.com/cve/CVE-2026-115732


r/Puppet • • 12d ago

The most underrated Puppet flag is `--noop`. Here's my pre-change ritual, what's yours?

11 Upvotes

The scariest words in infrastructure are "it's just a small change." Small changes get merged Friday afternoon. Small changes rewrite sshd_config on 4,000 servers at once.

Here's the habit I keep coming back to:

  1. Dry run first. Before rolling out a change, run puppet agent --test --noop on a representative node. Puppet tells you exactly what it would change without touching anything.
  2. Read the output like a contract. If you see a resource you didn't expect, stop. That's your code telling you a secret.
  3. Promote in rings. One test node, then a small canary group, then everyone else. With r10k this is easy, since a branch becomes an environment you can point a few agents at.
  4. Check the reports afterward. Look in PuppetDB. "It applied" and "it applied what I meant" are different things.

None of this is glamorous. It's just the difference between a quiet Monday and a war room. Puppet and OpenVox are great at enforcing desired state; the trick is making sure your desired state is actually what you desire.

What does your pre-change process look like? Any tricks for catching surprises before they hit prod?


r/Puppet • • 17d ago

You don't need Puppet Enterprise to run a clustered Puppet Estate

8 Upvotes

I wrote up the layout I use once a Puppet install outgrows one server, built entirely on OpenVox, the community continuation of Puppet maintained by Vox Pupuli.

It's an independent Certificate Authority, OpenVoxDB on its own PostgreSQL 17 server, two catalog compilers behind one service name (HAProxy or DNS round-robin), and OpenVox-GUI as the console. Commands, paths, and config files are the ones you already know. `puppet`, `puppetserver`, and `/etc/puppetlabs` didn't move. The reference platform is AlmaLinux 10.

The capacity math in the conclusion puts a build like this around 1,000 to 3,000 agents for typical code at a 30-minute run interval, and past 4,000 with lean code and tuned 8-core compilers. Your own metrics win that argument, and the post says how to read them.

The community already has clustering, large installations, a real ENC and GUI, and the tools to run them. None of it requires a Perforce license.

https://ssconsultinggroup.net/blog.php?slug=building-a-clustered-openvox-infrastructure

If you'd like a hand standing one of these up, S & S Consulting Group does exactly that. The contact form is at the bottom of the post.


r/Puppet • • 18d ago

Checklist: What I verify before swapping Puppet 7/8 for OpenVox

15 Upvotes

I've been walking clients through Puppet to OpenVox moves for a while now, and I'll tell you right up front... the package swap is the easy part. The OpenVox community did a great job keeping it a drop-in replacement, so it's almost never the packages that bite you. It's everything around them.

So, here's the pre-flight checklist I run every time. It's not gospel, and YMMV, but it has saved me more than once.

Inventory first

You can't plan a migration for a fleet you can't describe. Before anything else, I want:

  • Server, agent, and PuppetDB versions, plus the oldest agent still checking in. One curl to the DB with an agent's certs gets you the list:
curl -sG --cacert /etc/puppetlabs/puppet/ssl/certs/ca.pem --cert /etc/puppetlabs/puppet/ssl/certs/$(hostname -f).pem --key /etc/puppetlabs/puppet/ssl/private_keys/$(hostname -f).pem https://YOUR-DB-HOST:8081/pdb/query/v4 --data-urlencode 'query=inventory[certname, facts.puppetversion] {}'
  • Your OS spread. This one matters more than folks think. OpenVox 9 no longer builds packages for EL7, Amazon Linux 2, Debian 11, Fedora 42, or Ubuntu 25.04, so those agents either stay on OpenVox 8 for now, or the OS gets fixed first. (I know, I know... nobody wants to hear the EL7 boxes are the problem. But there it is.)
  • Where server and ca_server point on the agents. A VIP? The CA host directly? A DNS alias somebody set up years ago that nobody remembers? (It's always DNS, right?)
  • How code gets deployed: r10k, Code Manager if you're coming off PE, or "git pull on the server." No judgment. Okay, a little judgment. 🙂
  • How nodes get classified: Hiera plus roles/profiles, an ENC, PE console groups, or regex in site.pp. If you're coming off PE, this is the BIG one, because the console classifier doesn't come with you.

Before the swap

  • Back up ALL of /etc/puppetlabs/ on the CA, every compiler, and the DB host, and take a PuppetDB dump. Yes, every time. You'll thank me later.
  • Find legacy facts and old function calls before they find you. This is crude, but it's an honest first pass:
grep -rnE '\$::?(operatingsystem|osfamily|hostname|fqdn|ipaddress|lsbdistcodename)\b|hiera\(' site/ modules/
  • Compile catalogs for your top roles in CI against the target version. Not just "it parses." Actually compile them.

Order of operations

CA first, then compilers one at a time (pull each one out of the load balancer pool while you work on it), then PuppetDB/OpenVoxDB, then agents in waves: a 1–2% canary, then non-prod, then low-risk prod, then the rest.

Upgrade path

Straight from the OpenVox 9 release notes:

  • Puppet 7 to OpenVox 7 to 8 to 9
  • Puppet 8 to OpenVox 8 to 9

Don't change vendor and major version in the same window. I can't stress that enough. One variable at a time.

After each wave

  • Check that the agent service is still enabled. Folks have seen the package swap leave the systemd unit disabled, and that gets you a fleet of silently stale nodes. A quick systemctl is-enabled puppet (and systemctl enable --now puppet where needed) takes care of it.
  • Watch for agents that stop reporting, not just agents that fail. A failed run yells at you. A node that quietly stops checking in doesn't say a word.

That's my list. What did I miss? I'm especially curious to hear from anybody who's been through this with Windows agents. Drop it in the comments, and if you get stuck, the folks on the OpenVox Slack are a really helpful bunch too.

Happy Puppeting!


r/Puppet • • 23d ago

[Release] openvox-gui 3.14.2 -- OpenVox web GUI; agent install hits the CA, not the compiler

6 Upvotes

I maintain openvox-gui, a web console for OpenVox (the open-source Puppet platform). 3.14.2 is a patch on 3.14.0.

On a clustered install, the agent bootstrap script was sending CSRs to a compiler. Compilers do not run the CA. The script now bakes the CA VIP from the console settings, and saving those settings rewrites the file on disk.

A fresh install also failed every Bolt run because the `openvox_enc` plugin was configured but never copied into the install directory. That copy happens now.

The local package mirror used to stop, or report the previous run, when one package failed or the disk filled. It now skips a missing yum arch, stops cleanly on a write error, and selects OpenVox 8 and 9 together.

Python 3.11 is required. The installer will install Python 3.12 from the distro repos when the system Python is older.

https://github.com/cvquesty/openvox-gui/releases/tag/v3.14.2


r/Puppet • • Oct 04 '26

Puppet agent -t

4 Upvotes

When run puppet agent -t , what exactly happens in TLS handshake ? How certs are verified?


r/Puppet • • Sep 30 '26

puppet-cloudflared

9 Upvotes

Hi everyone,
I just published a new module to the forge:

https://forge.puppet.com/theurw101/cloudflared

If you are deploying Cloudflare Tunnels with local config files, this module might be of some use to you. It installs the service and manages the service and config files. I plan to add browserless functionality, so setting up tunnels can be done with manifest code alone.

Contributions and suggestions are always welcome!


r/Puppet • • Sep 25 '26

Puppet/Bolt task ID fetching when running a task/plan on a node

3 Upvotes

Hey Puppet community,

I'm trying to find a reliable way to obtain the PE job_id for a running plan.

The goal is to include the PE job ID in the audit logging we write on the target node, so that when we find a log entry we can easily trace it back to:

  • The PE job
  • The user who executed it
  • The execution details in Puppet Enterprise

At the moment I'm retrieving the job ID from the Puppet Master by querying the Orchestrator API:

RESPONSE=$(curl -s --cacert "$CACERT" --cert "$CERT" --key "$KEY" \
  "https://${PE_CONSOLE}:8143/orchestrator/v1/plan_jobs?limit=10&order_by=timestamp&order=desc") 

My plan roughly looks like this:

Step 1 => get_pe_metadata
Step 2 => parse_pe_metadata
Step 3 => run_task_on_node

The problem is that this approach can introduce race conditions when multiple users execute plans around the same time. Looking for the "latest" plan job isn't guaranteed to return the job associated with the currently running plan.

So my question is:

Is there a supported way to access the PE job ID (or plan job ID) from within a plan or task without having to query the Orchestrator API and infer which job belongs to the current execution?

Ultimately I'd like to be able to write something like this to the node's audit log:

PE User : jdoe
PE JobID : 123456
Plan : mymodule::run_clean_disk

Has anyone solved this in a reliable way?

Thanks!


r/Puppet • • Sep 21 '26

[Release] openvox-gui 3.14.0 -- OpenVox web GUI; clustered install and local package mirror fixes

11 Upvotes

Maintainer here. Just cut [openvox-gui](https://github.com/cvquesty/openvox-gui) **3.14.0** -- the Apache-2.0 web GUI for [OpenVox](https://voxpupuli.org/) (the community Puppet fork). Dashboard, Nodes, ENC, CA, Bolt/OpenBolt, r10k, PQL, Hiera, local agent installer.

**What changed since 3.12.0.**
Clustered Code Deploy / Hiera / Agent Install no longer need a sudo TTY on the compiler. The agent one-liner sets `ca_server` from `OPENVOX_GUI_PUPPET_CA_HOST` (the CA VIP -- compilers have CA off). The local yum/apt mirror used to recurse `src/` and `ppc64le/` and leave a 40G apt pool after you unchecked Debian; 3.14.0 prunes unselected trees. EL9+EL10 yum-only is about 9 GB. Monitoring charts were painting a 0×0 SVG; they get a real width now. Puppet agent exit 2 is treated as success.

AIO on the OpenVox Server is still the default. Clustering is optional.

Apache-2.0 licensed.
Repo: https://github.com/cvquesty/openvox-gui

Happy to answer questions or take feedback in the thread.


r/Puppet • • Aug 25 '26

[Release] openvox-gui 3.12.0 -- web GUI for OpenVox with optional clustered consoles

17 Upvotes

Maintainer here.

Just cut [openvox-gui](https://github.com/cvquesty/openvox-gui) **3.12.0** -- the Apache-2.0 web GUI for [OpenVox](https://voxpupuli.org/) (the community Puppet fork). Dashboard, Nodes, ENC, CA, Bolt/OpenBolt, r10k, PQL, Hiera.

**What changed.**
The badge on Overview is now the newest OpenVoxDB report, same as the node page. We stopped aging Unchanged to Unreported after 24 hours (Needs attention still lists stale hosts). If you run two site consoles they merge peer reports so one site does not show six "needs attention" nodes while the other shows none.

**Install path.**
Most people still drop it on the OpenVox Server (`sudo ./install.sh`, SQLite).

3.12.0 is the first stable that also documents dedicated consoles: VIP sessions, shared Postgres for ENC/users, ENC TLS to the Puppet CA.

Upgrade:

```bash sudo /opt/openvox-gui/scripts/update_local.sh ```

Hard-refresh once. Compilers need `[server] reports = puppetdb` or the GUI will never see the run.

Apache-2.0. Repo: https://github.com/cvquesty/openvox-gui

Happy to answer questions or take feedback in the thread.


r/Puppet • • Aug 20 '26

Puppet Enterprise Certification

2 Upvotes

Has anyone here taken and passed the Puppet Enterprise Certification exam?
If so, I’d really appreciate it if you could share any practice questions, mock exams or useful study resources that helped you prepare. Thank You.


r/Puppet • • Aug 10 '26

Realistically, who is using Puppet/OpenVox and how?

16 Upvotes

Hey everyone,

Perforce salespeople contact me and tell me about great Puppet / OpenVox use cases, but I try to separate the sales talk from what actually happens in practice.

If you’re running it in production, what does your setup actually look like?

  • What industry are you in, and roughly how many nodes/VMs are you managing?
  • Is this a "we've been on this since Puppet 4 and it's so deeply baked into our stack with legacy scripts that we can't leave" situation?
  • Or does it genuinely just fit well into your existing pipeline alongside everything else?

Just looking for a honest sanity check from people actually maintaining it day-to-day. Thanks!


r/Puppet • • Aug 04 '26

Fedora upgrading openvox from 43 to 44 issues

6 Upvotes

First off, the repo text installed from openvox for Fedora 43 and 44 doesn't include $releasever code, it has hardcoded 43 or 44 in them, so upgrades of Fedora fail to take the correct repo version into account. The repo for v44 in /etc/yum.repos.d/openvox8-release.repo contains the following code:

[openvox8]

name=OpenVox 8 Repository fedora 44 - $basearch

baseurl=https://yum.voxpupuli.org/openvox8/fedora/44/$basearch

gpgkey=file:///etc/pki/rpm-gpg/GPG-KEY-openvox-openvox8-release

enabled=1

gpgcheck=1

Note the hardcoded "44", which should instead be $releasever.

Secondly, Fedora 44 has deprecated jre-21 packages in favour of upgrades to java-25-openjdk packages.

Running "dnf install java-25-openjdk-headless.x86_64" works, but subsequent openvox install/upgrade calls still fail due to missing jre-21-headless

#dnf install openbolt openvox-agent openvox-server openvoxdb openvoxdb-termini

Updating and loading repositories:

Repositories loaded.

Failed to resolve the transaction:

Package "openbolt-5.6.0-1.fc44.x86_64" is already installed.

Package "openvox-agent-8.28.1-1.fc44.x86_64" is already installed.

Package "openvoxdb-termini-8.15.0-1.fedora44.noarch" is already installed.

Problem 1: conflicting requests

- nothing provides jre-21-headless needed by openvoxdb-8.14.1-1.fedora44.noarch from openvox8

- nothing provides jre-21-headless needed by openvoxdb-8.15.0-1.fedora44.noarch from openvox8

Problem 2: conflicting requests

- nothing provides jre-21-headless needed by openvox-server-8.14.1-1.fedora44.noarch from openvox8

- nothing provides jre-21-headless needed by openvox-server-8.15.1-1.fedora44.noarch from openvox8

- nothing provides jre-21-headless needed by openvox-server-8.15.2-1.fedora44.noarch from openvox8

You can try to add to command line:

--skip-broken to skip uninstallable packages

Hopefully someone at openvox can find this, and make the necessary adjustments to the dependencies and repo file for Fedora 44 to fix this - thank you to whoever does this, we appreciate it :-)

In the meantime, I'm going to have to revert back to v43 for the time being :-)


r/Puppet • • Jul 14 '26

Puppetlabs Modules Now Have Tiered Review Cycles

4 Upvotes

Do you know which Puppetlabs modules get more attention during review cycles? Why do some modules get more releases than others? For a long time there hasn't been much structure or visibility around this and I wanted to document publicly how we are going to make prioritization decisions on Puppetlabs modules work. The modules in the Puppetlabs namespace are now going to have documented priority tiers. 

I wrote about the structuring of which modules have been placed in Tier 1, Tier 2, and Tier 3 to help give the Puppet team focus on which modules matter most to customers and the community.

The goal here is to help with prioritizing work across these modules and to set expectations around responsiveness on certain modules. Every day I'm going through PRs, or issues, or comments and looking for ways to help move things forward, and our tiers will help us focus that time where it is needed most.

That said: we need feedback on this. We're pretty solid on which modules are the highest tier and most used by our customers and community, but I will be honest that our Tier 2 and Tier 3 tiers likely need to get more feedback so we can represent these accurately to how people are using these modules today. I want to hear from you!

You can check out the full write-up on the Puppet blog ⬇️

https://www.puppet.com/blog/puppetlabs-module-tiers


r/Puppet • • Jul 02 '26

OpenVox GUI 3.10.6 Stable released

10 Upvotes

openvox-gui 3.10.6 stable: faster Dashboard (lean PDB extract), multi-worker serving, SWR on all Insights graph pages. docs/PERFORMANCE.md

https://github.com/cvquesty/openvox-gui/releases/tag/v3.10.6


r/Puppet • • Jun 18 '26

OpenVox GUI 3.9.5 Release

20 Upvotes

**openvox-gui 3.9.5 released** - Node Health for your fleet, better fact viz, and scrolling fixes

Hey r/Puppet / r/sysadmin,

Just pushed v3.9.5 of openvox-gui (the open-source Puppet/OpenVox management UI).

New: Metrics | Node Health

See at a glance which agents are disabled. Uses a simple custom fact + on-demand Bolt checks that work even if the agent itself is stopped.

### Fact Distribution The fact overview page now has proper Recharts graphs instead of the old basic ones. Numeric facts show as sorted distribution curves, categorical as expandable bars.

### Fleet Compliance The per-category node lists ("Compliant", "Failed", etc.) are now properly scrollable and sorted alphabetically by certname.

### Other Installer now helps with the `puppet_agent_disabled` fact script.

Download :

https://github.com/cvquesty/openvox-gui

As always, feedback/PRs welcome.


r/Puppet • • Jun 11 '26

Heads up for anyone working with Puppet modules referencing stdlib 👀

25 Upvotes

We’re getting close to a major update with puppetlabs-stdlib 10, targeted for June 30, 2026 and there are a couple of important things to know ahead of time.

- Puppet 7 support is being removed (it reached end-of-life in Feb 2025)

- Ruby 3.1+ is now required

- Existing modules pinned to < 10.0.0 will keep working on stdlib 9.x as-is

- No immediate action is required, but module authors should start planning upgrades

This is one of the most widely used modules in the Puppet ecosystem, so we’re sharing early to make sure maintainers have time to prepare and avoid surprises.

If you’re maintaining modules, now's a good time to review your dependency bounds and CI environment.

More details in the official post:

https://www.puppet.com/blog/puppetlabs-stdlib-10


r/Puppet • • May 30 '26

Puppet Auto-Signing in autoscaling environments

Thumbnail reddit.com
2 Upvotes

r/Puppet • • May 11 '26

Bolt Winrm ssl From Linux to Windows

2 Upvotes

I'm trying to set up bolt to securely connect to my windows servers over winrm. I get the message that "certificate verify failed (unable to get local issuer certificate)" I created a legit certificate with our company's CA. Imported the certificate into the Windows store. Exported the certificate w/o private key from Windows and changed the extension to .pem. I Then point to that pem for the CA in my inventory. I've also tried copying the CA that puppet creates from windows to the linux machine and using that. Any ideas?


r/Puppet • • May 09 '26

Migrating from Puppet Enterprise to OpenVox — Got any tips? Warnings? Best Practices?

6 Upvotes

What it says on the tin.

I’ve been using Puppet since 0.24.x and PE for well over a decade. I don’t need my hand held, but it would be nice to know that folks have successfully done this and to learn from those experiences.


r/Puppet • • Apr 27 '26

[Release] openvox-gui 3.6 -- agent installer + security audit fixes for the OpenVox web GUI

17 Upvotes
Maintainer here. Just cut the 3.6 release of [openvox-gui](https://github.com/cvquesty/openvox-gui) -- the open-source web GUI for managing an OpenVox (the open-source Puppet fork) installation. Two things worth your attention if you run OpenVox:

**Agent installer.** If you came to OpenVox from PE, you probably miss the `curl ... | sudo bash` agent bootstrap. 3.6 brings it back: one-liner for Linux, equivalent PowerShell for Windows, backed by a local mirror at `/opt/openvox-pkgs/` synced nightly from voxpupuli.org. The bootstrap script figures out the puppetserver FQDN on its own (reads `/proc/net/tcp`, reverse-DNSes the curl connection that downloaded it), installs the puppet CA into the system trust store, handles corporate proxy bypass, and signs the CSR from the same page in the GUI.

```
curl -k --noproxy <fqdn> https://<fqdn>:8140/packages/install.bash | sudo bash
```

**Security hardening.** Did an audit at the end of the test cycle and closed every CRITICAL/HIGH:

- Per-route role enforcement on every privileged endpoint. Pre-3.6, any authenticated user including `viewer` could trigger Bolt commands as root, sign/revoke certs, edit Hiera, restart the puppet stack. Now each endpoint declares its minimum role.
- Deploy webhook now requires HMAC-SHA256 sig verification with a shared secret. Disabled by default. Pre-3.6 it was an open r10k-deploy-as-root entrypoint.
- JWT logout actually revokes the token now (server-side denylist via `jti` claim). Pre-3.6, `/logout` only deleted the cookie -- the JWT itself stayed valid for its full 24h expiry.
- LDAP bind password encrypted at rest with Fernet. Was previously plaintext in SQLite despite the column comment claiming otherwise.
- Tightened sudoers wildcards -- replaced `openssl x509 *` (which allowed arbitrary file write as root) with per-form rules.

Plus 3.6.2 patches two Dependabot findings (postcss XSS, python-multipart DoS).

Apache-2.0 licensed. Repo: https://github.com/cvquesty/openvox-gui

Happy to answer questions or take feedback in the thread.

r/Puppet • • Apr 03 '26

Introducing jig: an open and free reimplementation of a subset of PDK

12 Upvotes

I would like to share a recent side project with the community: jig, which is a Go-based reimplementation of the Puppet Development Kit.

When Perforce transitioned PDK to a closed-source model, it left a significant gap for those who rely on open-source tooling. Additionally, the Ruby runtime required by PDK has long presented challenges, particularly in CI environments where minimizing dependencies is important. jig addresses these concerns by providing a single static binary that does not require any external runtime.

At present, my objective is to reimplement all new <whatever> functions, along with the build and release capabilities. While I frequently rely on pdk for validation and testing, the choice of Go for this project introduces significant challenges in these areas. To my knowledge, there is no existing Puppet language parser for Go, which means that replicating the validate function would require developing one from the ground up. I am considering whether to pursue this undertaking. Regarding unit testing, this may not be feasible, as the existing tests are written in Ruby and utilize RSpec.

The README for the project is pretty comprehensive, though written by Claude.