Skip to content

Document standalone (masterless) puppet apply workflows #449

Open

Description

@miharp

The docs have no page for running nodes with puppet apply and no server. The plug-in pages describe only the agent path, and advice for the apply path is scattered across old blog posts, some of it out of date.

Who needs it:

  • bootstrapping the first node of a deployment, before a server exists
  • test environments (lab VMs, containers, CI jobs) that apply a control repository directly
  • single-node setups
  • fleets that drop their server

What testing shows, on packaged OpenVox 8.32.0 and 9.3.0 agents:

  • puppet apply loads custom facts, external facts, functions, resource types, and providers directly from the modulepath, including under --noop. The common belief that module facts are missing without a sync step is wrong. A fact that comes back undef means the modulepath was incomplete for that run.
  • puppet apply does not fill the plug-in cache, so facter -p and similar commands miss module facts afterwards. voxpupuli/controlrepo handles this with a guarded file resource at the top of its site.pp.
  • Under puppet apply, $trusted['extensions'] is always empty, even when the node's certificate carries pp_role, so classification by a certificate extension stops working.

#591 adds a how-to page next to "Puppet apply" in the 8.x and 9.x collections, and a "Plug-ins under Puppet apply" section on the plug-ins page.

Drafted with Claude; I reviewed and tested it.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions