Skip to content

Replace deprecated 'puppet master' terminology with 'Puppet server'#9572

Closed
stuckvgn wants to merge 1 commit intopuppetlabs:mainfrom
stuckvgn:update-puppet-master-to-puppet-server
Closed

Replace deprecated 'puppet master' terminology with 'Puppet server'#9572
stuckvgn wants to merge 1 commit intopuppetlabs:mainfrom
stuckvgn:update-puppet-master-to-puppet-server

Conversation

@stuckvgn
Copy link
Copy Markdown

Summary

Puppet deprecated the puppet master command and replaced it with Puppet Server several major versions ago, but the codebase still contains ~125 references to "puppet master" in user-facing documentation, help text, API docs, and code comments.

This PR systematically replaces "puppet master" with "Puppet server" (or "Puppet Server" where referring to the product name) across:

  • CLI help text in application classes (agent, apply, device)
  • Face descriptions and summaries (catalog, facts, node/clean, plugin, report)
  • Indirector terminus descriptions and the indirector face
  • Reference documentation (configuration, function, indirection, report, type)
  • API endpoint documentation (certificate, certificate_request, certificate_revocation_list, certificate_status, environments, report)
  • Internal documentation (indirector.md, profiling.md)
  • Man pages (generated troff and markdown files)
  • Localization template (puppet.pot)
  • Code comments in profiler, ENC example, and generate function

What is NOT changed

  • Acceptance tests using master as a Beaker test framework role identifier (this is Beaker DSL, not Puppet terminology)
  • Spec tests that reference internal API backwards-compat for the master run mode
  • Ruby code that maintains backwards compatibility with :master run mode (run_mode.rb, settings handling, route configuration)
  • puppet master --compile references are updated to puppet catalog compile (the modern equivalent)

51 files changed, 125 lines replaced (1:1 substitution, no functional changes)

Test plan

  • Verify puppet agent --help, puppet apply --help, puppet device --help show updated text
  • Verify puppet plugin --help, puppet catalog --help, puppet facts --help, puppet report --help, puppet node --help show updated descriptions
  • Verify man pages render correctly with man puppet-agent, man puppet-catalog, etc.
  • Run existing test suite to confirm no regressions (these are documentation-only changes to user-facing strings)

Puppet deprecated the 'puppet master' command in favor of 'puppet server'
(Puppet Server) several versions ago, but significant documentation, help
text, API docs, and code comments throughout the codebase still reference
the outdated 'puppet master' terminology.

This commit updates user-facing strings, documentation, help text, man pages,
API docs, code comments, and localization templates to use 'Puppet server'
or 'Puppet Server' as appropriate.

Changes span:
- CLI help text in application classes (agent, apply, device)
- Face descriptions and summaries (catalog, facts, node, plugin, report)
- Indirector terminus descriptions
- Reference documentation (configuration, function, indirection, report, type)
- API endpoint documentation (certificate, report, environments)
- Internal documentation (indirector.md, profiling.md)
- Man pages (generated troff files)
- Localization template (puppet.pot)

Note: Acceptance tests and spec files that use 'master' as a Beaker test
framework role identifier are intentionally not changed, as 'master' in
that context refers to the Beaker DSL, not Puppet terminology. Internal
Ruby code that maintains backwards compatibility with the 'master' run
mode (e.g., run_mode.rb, settings handling) is also preserved.
@stuckvgn stuckvgn requested a review from a team as a code owner February 25, 2026 13:48
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Feb 25, 2026

CLA assistant check
All committers have signed the CLA.

@silug
Copy link
Copy Markdown

silug commented Feb 25, 2026

@stuckvgn it looks like a number of these changes were already made in OpenVoxProject/openvox. I made an attempt to rebase the rest of your changes in OpenVoxProject/openvox#348. We're going to try to have the changes merged for OpenVox 9.

Thanks for the contribution.

@stuckvgn
Copy link
Copy Markdown
Author

Thanks @silug for picking this up and doing the rebase work! Great to hear the changes will land in OpenVox 9. Happy to help with OpenVoxProject/openvox#348 if there's anything useful I can contribute — otherwise sounds like you've got it covered.

@stuckvgn
Copy link
Copy Markdown
Author

Closing in favor of the OpenVox fork where @silug has already picked this up in OpenVoxProject/openvox#348. The work is in better hands there — OpenVox is the actively maintained successor for this functionality. Thanks for the context @silug.

@stuckvgn stuckvgn closed this Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants