openvox 9.0.0.pre.alpha2 → 9.0.0.pre.beta2

data/lib/puppet/type/file/source.rb

@@ -20,7 +20,7 @@ module Puppet
       attribute is mutually exclusive with `content` and `target`. Allowed
       values are:
 
-      * `puppet:` URIs, which point to files in modules or Puppet file server
+      * `puppet:` URIs, which point to files in modules or OpenVox file server
       mount points.
       * Fully qualified paths to locally available files (including files on NFS
       shares or Windows mapped drives).
@@ -31,8 +31,8 @@ module Puppet
 
       `puppet:///modules/<MODULE NAME>/<FILE PATH>`
 
-      This will fetch a file from a module on the Puppet master (or from a
-      local module when using Puppet apply). Given a `modulepath` of
+      This will fetch a file from a module on the OpenVox server (or from a
+      local module when using puppet apply). Given a `modulepath` of
       `/etc/puppetlabs/code/modules`, the example above would resolve to
       `/etc/puppetlabs/code/modules/<MODULE NAME>/files/<FILE PATH>`.
 
@@ -46,28 +46,28 @@ module Puppet
       because HTTP servers do not transfer any metadata that translates to
       ownership or permission details.
 
-      Puppet determines if file content is synchronized by computing a checksum
+      OpenVox determines if file content is synchronized by computing a checksum
       for the local file and comparing it against the `checksum_value`
       parameter. If the `checksum_value` parameter is not specified for
-      `puppet` and `file` sources, Puppet computes a checksum based on its
-      `Puppet[:digest_algorithm]`. For `http(s)` sources, Puppet uses the
+      `puppet` and `file` sources, OpenVox computes a checksum based on its
+      `Puppet[:digest_algorithm]`. For `http(s)` sources, OpenVox uses the
       first HTTP header it recognizes out of the following list:
       `X-Checksum-Sha256`, `X-Checksum-Sha1`, `X-Checksum-Md5` or `Content-MD5`.
-      If the server response does not include one of these headers, Puppet
-      defaults to using the `Last-Modified` header. Puppet updates the local
+      If the server response does not include one of these headers, OpenVox
+      defaults to using the `Last-Modified` header. OpenVox updates the local
       file if the header is newer than the modified time (mtime) of the local
       file.
 
-      _HTTP_ URIs can include a user information component so that Puppet can
+      _HTTP_ URIs can include a user information component so that OpenVox can
       retrieve file metadata and content from HTTP servers that require HTTP Basic
       authentication. For example `https://<user>:<pass>@<server>:<port>/path/to/file.`
 
-      When connecting to _HTTPS_ servers, Puppet trusts CA certificates in the
-      puppet-agent certificate bundle and the Puppet CA. You can configure Puppet
+      When connecting to _HTTPS_ servers, OpenVox trusts CA certificates in the
+      puppet-agent certificate bundle and the OpenVox CA. You can configure OpenVox
       to trust additional CA certificates using the `Puppet[:ssl_trust_store]`
       setting.
 
-      Multiple `source` values can be specified as an array, and Puppet will
+      Multiple `source` values can be specified as an array, and OpenVox will
       use the first source that exists. This can be used to serve different
       files to different system types:
 
@@ -323,9 +323,9 @@ module Puppet
 
     def chunk_file_from_source(&block)
       if uri.scheme =~ /^https?/
-        # Historically puppet has not encoded the http(s) source URL before parsing
+        # Historically OpenVox has not encoded the http(s) source URL before parsing
         # it, for example, if the path contains spaces, then it must be URL encoded
-        # as %20 in the manifest. Puppet behaves the same when retrieving file
+        # as %20 in the manifest. OpenVox behaves the same when retrieving file
         # metadata via http(s), see Puppet::Indirector::FileMetadata::Http#find.
         url = URI.parse(metadata.source)
         get_from_http_source(url, &block)
@@ -347,7 +347,7 @@ module Puppet
 
   Puppet::Type.type(:file).newparam(:source_permissions) do
     desc <<-'EOT'
-      Whether (and how) Puppet should copy owner, group, and mode permissions from
+      Whether (and how) OpenVox should copy owner, group, and mode permissions from
       the `source` to `file` resources when the permissions are not explicitly
       specified. (In all cases, explicit permissions will take precedence.)
       Valid values are `use`, `use_when_creating`, and `ignore`:
@@ -355,10 +355,10 @@ module Puppet
       * `ignore` (the default) will never apply the owner, group, or mode from
         the `source` when managing a file. When creating new files without explicit
         permissions, the permissions they receive will depend on platform-specific
-        behavior. On POSIX, Puppet will use the umask of the user it is running as.
-        On Windows, Puppet will use the default DACL associated with the user it is
+        behavior. On POSIX, OpenVox will use the umask of the user it is running as.
+        On Windows, OpenVox will use the default DACL associated with the user it is
         running as.
-      * `use` will cause Puppet to apply the owner, group,
+      * `use` will cause OpenVox to apply the owner, group,
         and mode from the `source` to any files it is managing.
       * `use_when_creating` will only apply the owner, group, and mode from the
         `source` when creating a file; existing files will not have their permissions
@@ -368,13 +368,7 @@ module Puppet
     defaultto :ignore
     newvalues(:use, :use_when_creating, :ignore)
     munge do |value|
-      value = value ? value.to_sym : :ignore
-      if @resource.file && @resource.line && value != :ignore
-        # TRANSLATORS "source_permissions" is a parameter name and should not be translated
-        Puppet.puppet_deprecation_warning(_("The `source_permissions` parameter is deprecated. Explicitly set `owner`, `group`, and `mode`."), file: @resource.file, line: @resource.line)
-      end
-
-      value
+      value ? value.to_sym : :ignore
     end
   end
 end

data/lib/puppet/type/file.rb

@@ -27,11 +27,11 @@ Puppet::Type.newtype(:file) do
     downloaded from a remote source using the `source` attribute; the latter
     can also be used to recursively serve directories (when the `recurse`
     attribute is set to `true` or `local`). On Windows, note that file
-    contents are managed in binary mode; Puppet never automatically translates
+    contents are managed in binary mode; OpenVox never automatically translates
     line endings.
 
-    **Autorequires:** If Puppet is managing the user or group that owns a
-    file, the file resource will autorequire them. If Puppet is managing any
+    **Autorequires:** If OpenVox is managing the user or group that owns a
+    file, the file resource will autorequire them. If OpenVox is managing any
     parent directories of a file, the file resource autorequires them.
 
     Warning: Enabling `recurse` on directories containing large numbers of
@@ -80,11 +80,11 @@ Puppet::Type.newtype(:file) do
       (`File { backup => main }`), so it can affect all file resources.
 
       * If set to `false`, file content won't be backed up.
-      * If set to a string beginning with `.`, such as `.puppet-bak`, Puppet will
+      * If set to a string beginning with `.`, such as `.puppet-bak`, OpenVox will
         use copy the file in the same directory with that value as the extension
         of the backup. (A value of `true` is a synonym for `.puppet-bak`.)
-      * If set to any other string, Puppet will try to back up to a filebucket
-        with that title. Puppet automatically creates a **local** filebucket
+      * If set to any other string, OpenVox will try to back up to a filebucket
+        with that title. OpenVox automatically creates a **local** filebucket
         named `puppet` if one doesn't already exist. See the `filebucket` resource
         type for more details.
 
@@ -92,18 +92,25 @@ Puppet::Type.newtype(:file) do
 
       Backing up to a local filebucket isn't particularly useful. If you want
       to make organized use of backups, you will generally want to use the
-      primary Puppet server's filebucket service. This requires declaring a
+      primary OpenVox server's filebucket service. This requires declaring a
       filebucket resource and a resource default for the `backup` attribute
       in site.pp:
 
           # /etc/puppetlabs/puppet/manifests/site.pp
           filebucket { 'main':
             path   => false,                # This is required for remote filebuckets.
-            server => 'puppet.example.com', # Optional; defaults to the configured primary Puppet server.
+            server => 'puppet.example.com', # Optional; defaults to the configured primary OpenVox server.
           }
 
           File { backup => main, }
 
+      > **Note**: A central filebucket is shared by every node that backs up to it,
+        and stored content is addressed only by checksum, with no record of which
+        node submitted it. Treat anything backed up there as readable by every
+        certificate the server's `auth.conf` allows to reach the `file_bucket_file`
+        endpoint, and avoid pointing `backup` at a central filebucket for files whose
+        contents are sensitive. See the `filebucket` resource type for details.
+
       If you are using multiple primary servers, you will want to
       centralize the contents of the filebucket. Either configure your load
       balancer to direct all filebucket traffic to a single primary server, or use
@@ -149,7 +156,7 @@ Puppet::Type.newtype(:file) do
 
       * `false` --- The default behavior. The contents of the directory will not be
         automatically managed.
-      * `remote` --- If the `source` attribute is set, Puppet will automatically
+      * `remote` --- If the `source` attribute is set, OpenVox will automatically
         manage the contents of the source directory (or directories), ensuring
         that equivalent files and directories exist on the target system and
         that their contents match.
@@ -188,13 +195,13 @@ Puppet::Type.newtype(:file) do
   end
 
   newparam(:recurselimit) do
-    desc "How far Puppet should descend into subdirectories, when using
+    desc "How far OpenVox should descend into subdirectories, when using
       `ensure => directory` and either `recurse => true` or `recurse => remote`.
       The recursion limit affects which files will be copied from the `source`
       directory, as well as which files can be purged when `purge => true`.
 
       Setting `recurselimit => 0` is the same as setting `recurse => false` ---
-      Puppet will manage the directory, but all of its contents will be treated
+      OpenVox will manage the directory, but all of its contents will be treated
       as unmanaged.
 
       Setting `recurselimit => 1` will manage files and directories that are
@@ -241,7 +248,7 @@ Puppet::Type.newtype(:file) do
       whose content doesn't match what the `source` or `content` attribute
       specifies.  Setting this to false allows file resources to initialize files
       without overwriting future changes.  Note that this only affects content;
-      Puppet will still manage ownership and permissions."
+      OpenVox will still manage ownership and permissions."
     defaultto :true
   end
 
@@ -320,7 +327,7 @@ Puppet::Type.newtype(:file) do
   newparam(:show_diff, :boolean => true, :parent => Puppet::Parameter::Boolean) do
     desc "Whether to display differences when the file changes, defaulting to
         true.  This parameter is useful for files that may contain passwords or
-        other secret data, which might otherwise be included in Puppet reports or
+        other secret data, which might otherwise be included in OpenVox reports or
         other insecure outputs.  If the global `show_diff` setting
         is false, then no diffs will be shown even if this parameter is true."
 
@@ -353,14 +360,14 @@ Puppet::Type.newtype(:file) do
 
   newparam(:validate_cmd) do
     desc "A command for validating the file's syntax before replacing it. If
-      Puppet would need to rewrite a file due to new `source` or `content`, it
+      OpenVox would need to rewrite a file due to new `source` or `content`, it
       will check the new content's validity first. If validation fails, the file
       resource will fail.
 
       This command must have a fully qualified path, and should contain a
       percent (`%`) token where it would expect an input file. It must exit `0`
       if the syntax is correct, and non-zero otherwise. The command will be
-      run on the target system while applying the catalog, not on the primary Puppet server.
+      run on the target system while applying the catalog, not on the primary OpenVox server.
 
       Example:
 

data/lib/puppet/type/filebucket.rb

@@ -6,19 +6,18 @@ module Puppet
   Type.newtype(:filebucket) do
     @doc = <<-EOT
       A repository for storing and retrieving file content by cryptographic checksum. Can
-      be local to each agent node, or centralized on a primary Puppet server. All
-      puppet servers provide a filebucket service that agent nodes can access
+      be local to each agent node, or centralized on a primary OpenVox server. All
+      OpenVox servers provide a filebucket service that agent nodes can access
       via HTTP, but you must declare a filebucket resource before any agents
       will do so.
 
       Filebuckets are used for the following features:
 
       - **Content backups.** If the `file` type's `backup` attribute is set to
-        the name of a filebucket, Puppet will back up the _old_ content whenever
+        the name of a filebucket, OpenVox will back up the _old_ content whenever
         it rewrites a file; see the documentation for the `file` type for more
         details. These backups can be used for manual recovery of content, but
-        are more commonly used to display changes and differences in a tool like
-        Puppet Dashboard.
+        are more commonly used to display changes and differences.
 
       To use a central filebucket for backups, you will usually want to declare
       a filebucket resource and a resource default for the `backup` attribute
@@ -32,10 +31,25 @@ module Puppet
 
           File { backup => main, }
 
-      Puppet Servers automatically provide the filebucket service, so
+      OpenVox Servers automatically provide the filebucket service, so
       this will work in a default configuration. If you have a heavily
-      restricted Puppet Server `auth.conf` file, you may need to allow access to the
+      restricted OpenVox Server `auth.conf` file, you may need to allow access to the
       `file_bucket_file` endpoint.
+
+      > **Security note**: a central filebucket is shared by every node that backs
+        up to it. Content is addressed purely by checksum, and the service records no
+        association between stored content and the node that submitted it, so a
+        request for `/puppet/v3/file_bucket_file/<digest>/<checksum>` returns the
+        matching content to any client the server's `auth.conf` permits, regardless
+        of which node originally backed that file up. Retrieving content requires
+        knowing the checksum of the exact bytes, so this is not a general-purpose
+        read primitive, but you should treat a central filebucket as readable by
+        every certificate allowed to reach the endpoint and avoid backing up files
+        whose contents are sensitive. Since OpenVox 9 the default `auth.conf` grants
+        agents only the `HEAD` and `PUT` access they need in order to store backups,
+        and restricts `GET` to certificates carrying the `pp_cli_auth` extension. If
+        you restore remotely using some other administrative certificate, add a rule
+        of your own rather than widening the shipped one.
     EOT
 
     newparam(:name) do
@@ -98,7 +112,7 @@ module Puppet
     def mkbucket
       # Default is a local filebucket, if no server is given.
       # If the default path has been removed, too, then
-      # the puppetmaster is used as default server
+      # the OpenVox server is used as default server
 
       type = "local"
       args = {}

data/lib/puppet/type/group.rb

@@ -151,9 +151,9 @@ module Puppet
       desc "Configures the behavior of the `members` parameter.
 
         * `false` (default) --- The provided list of group members is partial,
-          and Puppet **ignores** any members that aren't listed there.
+          and OpenVox **ignores** any members that aren't listed there.
         * `true` --- The provided list of of group members is comprehensive, and
-          Puppet **purges** any members that aren't listed there."
+          OpenVox **purges** any members that aren't listed there."
       defaultto false
     end
 
@@ -162,7 +162,7 @@ module Puppet
         it is advisable to restrict names to the lowest common denominator,
         which is a maximum of 8 characters beginning with a letter.
 
-        Note that Puppet considers group names to be case-sensitive, regardless
+        Note that OpenVox considers group names to be case-sensitive, regardless
         of the platform's own rules; be sure to always use the same case when
         referring to a given group."
       isnamevar
@@ -197,10 +197,10 @@ module Puppet
     newparam(:attribute_membership) do
       desc "AIX only. Configures the behavior of the `attributes` parameter.
 
-        * `minimum` (default) --- The provided list of attributes is partial, and Puppet
+        * `minimum` (default) --- The provided list of attributes is partial, and OpenVox
           **ignores** any attributes that aren't listed there.
         * `inclusive` --- The provided list of attributes is comprehensive, and
-          Puppet **purges** any attributes that aren't listed there."
+          OpenVox **purges** any attributes that aren't listed there."
 
       newvalues(:inclusive, :minimum)
 

data/lib/puppet/type/notify.rb

@@ -5,7 +5,7 @@
 
 module Puppet
   Type.newtype(:notify) do
-    @doc = "Sends an arbitrary message, specified as a string, to the agent run-time log. It's important to note that the notify resource type is not idempotent. As a result, notifications are shown as a change on every Puppet run."
+    @doc = "Sends an arbitrary message, specified as a string, to the agent run-time log. It's important to note that the notify resource type is not idempotent. As a result, notifications are shown as a change on every OpenVox run."
 
     apply_to_all
 

data/lib/puppet/type/package.rb

@@ -17,7 +17,7 @@ module Puppet
       cannot.  For those package formats that cannot retrieve their own files,
       you can use the `source` parameter to point to the correct file.
 
-      Puppet will automatically guess the packaging format that you are
+      OpenVox will automatically guess the packaging format that you are
       using based on the platform you are on, but you can override it
       using the `provider` parameter; each provider defines what it
       requires in order to function, and you must meet those requirements
@@ -30,7 +30,7 @@ module Puppet
       resource; `Package[<NAME>]` is not a synonym for `Package[<TITLE>]` like
       it is for many other resource types.
 
-      **Autorequires:** If Puppet is managing the files specified as a
+      **Autorequires:** If OpenVox is managing the files specified as a
       package's `adminfile`, `responsefile`, or `source`, the package
       resource will autorequire those files."
 
@@ -431,7 +431,7 @@ module Puppet
 
         Different providers accept different values for `source`. Most providers
         accept paths to local files stored on the target system. Some providers
-        may also accept URLs or network drive paths. Puppet will not
+        may also accept URLs or network drive paths. OpenVox will not
         automatically retrieve source files for you, and usually just passes the
         value of `source` to the package installation command.
 
@@ -598,7 +598,7 @@ module Puppet
         option will automatically be quoted when passed to the uninstall
         command.
 
-        On Windows, this is the **only** place in Puppet where backslash
+        On Windows, this is the **only** place in OpenVox where backslash
         separators should be used.  Note that backslashes in double-quoted
         strings _must_ be double-escaped and backslashes in single-quoted
         strings _may_ be double-escaped.

data/lib/puppet/type/schedule.rb

@@ -3,8 +3,8 @@
 module Puppet
   Type.newtype(:schedule) do
     @doc = <<-'EOT'
-      Define schedules for Puppet. Resources can be limited to a schedule by using the
-      [`schedule`](https://puppet.com/docs/puppet/latest/metaparameter.html#schedule)
+      Define schedules for OpenVox. Resources can be limited to a schedule by using the
+      [`schedule`](https://docs.openvoxproject.org/openvox/latest/metaparameter.html#schedule)
       metaparameter.
 
       Currently, **schedules can only be used to stop a resource from being
@@ -12,11 +12,11 @@ module Puppet
       wouldn't be, and they cannot accurately specify a time when a resource
       should run.
 
-      Every time Puppet applies its configuration, it will apply the
+      Every time OpenVox applies its configuration, it will apply the
       set of resources whose schedule does not eliminate them from
       running right then, but there is currently no system in place to
       guarantee that a given resource runs at a given time.  If you
-      specify a very  restrictive schedule and Puppet happens to run at a
+      specify a very  restrictive schedule and OpenVox happens to run at a
       time within that schedule, then the resources will get applied;
       otherwise, that work may never get done.
 
@@ -31,13 +31,13 @@ module Puppet
             repeat => 1,
           }
 
-      With this schedule, the first time that Puppet runs between 2 and 4 AM,
+      With this schedule, the first time that OpenVox runs between 2 and 4 AM,
       all resources with this schedule will get applied, but they won't
       get applied again between 2 and 4 because they will have already
       run once that day, and they won't get applied outside that schedule
       because they will be outside the scheduled range.
 
-      Puppet automatically creates a schedule for each of the valid periods
+      OpenVox automatically creates a schedule for each of the valid periods
       with the same name as that period (such as hourly and daily).
       Additionally, a schedule named `puppet` is created and used as the
       default, with the following attributes:
@@ -195,7 +195,7 @@ module Puppet
     newparam(:period) do
       desc <<-EOT
         The period of repetition for resources on this schedule. The default is
-        for resources to get applied every time Puppet runs.
+        for resources to get applied every time OpenVox runs.
 
         Note that the period defines how often a given resource will get
         applied but not when; if you would like to restrict the hours
@@ -203,7 +203,7 @@ module Puppet
         during a maintenance window), then use the `range` attribute.
 
         If the provided periods are not sufficient, you can provide a
-        value to the *repeat* attribute, which will cause Puppet to
+        value to the *repeat* attribute, which will cause OpenVox to
         schedule the affected resources evenly in the period the
         specified number of times.  Take this schedule:
 
@@ -212,12 +212,12 @@ module Puppet
               repeat => 6,
             }
 
-        This can cause Puppet to apply that resource up to every 10 minutes.
+        This can cause OpenVox to apply that resource up to every 10 minutes.
 
-        At the moment, Puppet cannot guarantee that level of repetition; that
+        At the moment, OpenVox cannot guarantee that level of repetition; that
         is, the resource can applied _up to_ every 10 minutes, but internal
         factors might prevent it from actually running that often (for instance,
-        if a Puppet run is still in progress when the next run is scheduled to
+        if an OpenVox run is still in progress when the next run is scheduled to
         start, that next run will be suppressed).
 
         See the `periodmatch` attribute for tuning whether to match

data/lib/puppet/type/service.rb

@@ -11,24 +11,24 @@ module Puppet
     @doc = "Manage running services.  Service support unfortunately varies
       widely by platform --- some platforms have very little if any concept of a
       running service, and some have a very codified and powerful concept.
-      Puppet's service support is usually capable of doing the right thing, but
+      OpenVox's service support is usually capable of doing the right thing, but
       the more information you can provide, the better behaviour you will get.
 
       Puppet 2.7 and newer expect init scripts to have a working status command.
       If this isn't the case for any of your services' init scripts, you will
       need to set `hasstatus` to false and possibly specify a custom status
-      command in the `status` attribute. As a last resort, Puppet will attempt to
+      command in the `status` attribute. As a last resort, OpenVox will attempt to
       search the process table by calling whatever command is listed in the `ps`
       fact. The default search pattern is the name of the service, but you can
       specify it with the `pattern` attribute.
 
       **Refresh:** `service` resources can respond to refresh events (via
       `notify`, `subscribe`, or the `~>` arrow). If a `service` receives an
-      event from another resource, Puppet will restart the service it manages.
+      event from another resource, OpenVox will restart the service it manages.
       The actual command used to restart the service depends on the platform and
       can be configured:
 
-      * If you set `hasrestart` to true, Puppet will use the init script's restart command.
+      * If you set `hasrestart` to true, OpenVox will use the init script's restart command.
       * You can provide an explicit command for restarting with the `restart` attribute.
       * If you do neither, the service's stop and start commands will be used."
 
@@ -61,7 +61,7 @@ module Puppet
         wherever possible, it relies on local tools to enable or disable
         a given service. Default values depend on the platform.
 
-        If you don't specify a value for the `enable` attribute, Puppet leaves
+        If you don't specify a value for the `enable` attribute, OpenVox leaves
         that aspect of the service alone and your operating system determines
         the behavior."
 
@@ -175,12 +175,12 @@ module Puppet
         The init script's status command must return 0 if the service is
         running and a nonzero value otherwise. Ideally, these exit codes
         should conform to [the LSB's specification][lsb-exit-codes] for init
-        script status actions, but Puppet only considers the difference
+        script status actions, but OpenVox only considers the difference
         between 0 and nonzero to be relevant.
 
         If a service's init script does not support any kind of status command,
         you should set `hasstatus` to false and either provide a specific
-        command using the `status` attribute or expect that Puppet will look for
+        command using the `status` attribute or expect that OpenVox will look for
         the service name in the process table. Be aware that 'virtual' init
         scripts (like 'network' under Red Hat systems) will respond poorly to
         refresh events from other resources if you override the default behavior
@@ -240,7 +240,7 @@ module Puppet
         return 0 if the service is running and a nonzero value otherwise.
         Ideally, these exit codes should conform to [the LSB's
         specification][lsb-exit-codes] for init script status actions, but
-        Puppet only considers the difference between 0 and nonzero to be
+        OpenVox only considers the difference between 0 and nonzero to be
         relevant.
 
         If left unspecified, the status of the service will be determined

data/lib/puppet/type/stage.rb

@@ -4,7 +4,7 @@ Puppet::Type.newtype(:stage) do
   desc "A resource type for creating new run stages.  Once a stage is available,
     classes can be assigned to it by declaring them with the resource-like syntax
     and using
-    [the `stage` metaparameter](https://puppet.com/docs/puppet/latest/metaparameter.html#stage).
+    [the `stage` metaparameter](https://docs.openvoxproject.org/openvox/latest/metaparameter.html#stage).
 
     Note that new stages are not useful unless you also declare their order
     in relation to the default `main` stage.

data/lib/puppet/type/user.rb

@@ -16,9 +16,9 @@ module Puppet
       groups and generally uses POSIX APIs for retrieving information
       about them.  It does not directly modify `/etc/passwd` or anything.
 
-      **Autorequires:** If Puppet is managing the user's primary group (as
+      **Autorequires:** If OpenVox is managing the user's primary group (as
       provided in the `gid` attribute) or any group listed in the `groups`
-      attribute then the user resource will autorequire that group. If Puppet
+      attribute then the user resource will autorequire that group. If OpenVox
       is managing any role accounts corresponding to the user's roles, the
       user resource will autorequire those role accounts."
 
@@ -126,7 +126,7 @@ module Puppet
         automatically. This will likely result in the same user having
         different UIDs on different systems, which is not recommended. This is
         especially noteworthy when managing the same user on both Darwin and
-        other platforms, since Puppet does UID generation on Darwin, but
+        other platforms, since OpenVox does UID generation on Darwin, but
         the underlying tools do so on other platforms.
 
         On Windows, this property is read-only and will return the user's
@@ -149,7 +149,7 @@ module Puppet
 
         This attribute is not supported on Windows systems; use the `groups`
         attribute instead. (On Windows, designating a primary group is only
-        meaningful for domain accounts, which Puppet does not currently manage.)"
+        meaningful for domain accounts, which OpenVox does not currently manage.)"
 
       munge do |value|
         if value.is_a?(String) and value =~ /^[-0-9]+$/
@@ -223,26 +223,24 @@ module Puppet
         encryption formats and requirements.
 
         * Mac OS X 10.5 and 10.6, and some older Linux distributions, use salted SHA1
-          hashes. You can use Puppet's built-in `sha1` function to generate a salted SHA1
+          hashes. You can use OpenVox's built-in `sha1` function to generate a salted SHA1
           hash from a password.
         * Mac OS X 10.7 (Lion), and many recent Linux distributions, use salted SHA512
-          hashes. The Puppet Labs [stdlib][] module contains a `str2saltedsha512` function
+          hashes. The puppetlabs [stdlib](https://forge.puppet.com/modules/puppetlabs/stdlib) module contains a `str2saltedsha512` function
           which can generate password hashes for these operating systems.
         * OS X 10.8 and higher use salted SHA512 PBKDF2 hashes. When managing passwords
           on these systems, the `salt` and `iterations` attributes need to be specified as
           well as the password.
-        * macOS 10.15 and later require the salt to be 32 bytes. Because Puppet's user
+        * macOS 10.15 and later require the salt to be 32 bytes. Because OpenVox's user
           resource requires the value to be hex encoded, the length of the salt's
           string must be 64.
         * Windows passwords can be managed only in cleartext, because there is no Windows
           API for setting the password hash.
 
-        [stdlib]: https://github.com/puppetlabs/puppetlabs-stdlib/
-
         Enclose any value that includes a dollar sign ($) in single quotes (') to avoid
         accidental variable interpolation.
 
-        To redact passwords from reports to PuppetDB, use the `Sensitive` data type. For
+        To redact passwords from reports to OpenVoxDB, use the `Sensitive` data type. For
         example, this resource protects the password:
 
         ```puppet
@@ -388,18 +386,18 @@ module Puppet
         it is advisable to restrict names to the lowest common denominator,
         which is a maximum of 8 characters beginning with a letter.
 
-        Note that Puppet considers user names to be case-sensitive, regardless
+        Note that OpenVox considers user names to be case-sensitive, regardless
         of the platform's own rules; be sure to always use the same case when
         referring to a given user."
       isnamevar
     end
 
     newparam(:membership) do
-      desc "If `minimum` is specified, Puppet will ensure that the user is a
+      desc "If `minimum` is specified, OpenVox will ensure that the user is a
         member of all specified groups, but will not remove any other groups
         that the user is a part of.
 
-        If `inclusive` is specified, Puppet will ensure that the user is a
+        If `inclusive` is specified, OpenVox will ensure that the user is a
         member of **only** specified groups."
 
       newvalues(:inclusive, :minimum)
@@ -423,14 +421,14 @@ module Puppet
     end
 
     newparam(:managehome, :boolean => true, :parent => Puppet::Parameter::Boolean) do
-      desc "Whether to manage the home directory when Puppet creates or removes the user.
-        This creates the home directory if Puppet also creates the user account, and deletes the
-        home directory if Puppet also removes the user account.
-
-        This parameter has no effect unless Puppet is also creating or removing the user in the
-        resource at the same time. For instance, Puppet creates a home directory for a managed
-        user if `ensure => present` and the user does not exist at the time of the Puppet run.
-        If the home directory is then deleted manually, Puppet will not recreate it on the next
+      desc "Whether to manage the home directory when OpenVox creates or removes the user.
+        This creates the home directory if OpenVox also creates the user account, and deletes the
+        home directory if OpenVox also removes the user account.
+
+        This parameter has no effect unless OpenVox is also creating or removing the user in the
+        resource at the same time. For instance, OpenVox creates a home directory for a managed
+        user if `ensure => present` and the user does not exist at the time of the OpenVox run.
+        If the home directory is then deleted manually, OpenVox will not recreate it on the next
         run.
 
         Note that on Windows, this manages creation/deletion of the user profile instead of the

data/lib/puppet/type/whit.rb

@@ -1,8 +1,8 @@
 # frozen_string_literal: true
 
 Puppet::Type.newtype(:whit) do
-  desc "Whits are internal artifacts of Puppet's current implementation, and
-    Puppet suppresses their appearance in all logs. We make no guarantee of
+  desc "Whits are internal artifacts of OpenVox's current implementation, and
+    OpenVox suppresses their appearance in all logs. We make no guarantee of
     the whit's continued existence, and it should never be used in an actual
     manifest. Use the `anchor` type from the puppetlabs-stdlib module if you
     need arbitrary whit-like no-op resources."