openvox 9.0.0.pre.beta1 → 9.0.0.pre.beta2

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."

data/lib/puppet/type.rb

@@ -1238,18 +1238,18 @@ class Type
   newmetaparam(:noop) do
     desc "Whether to apply this resource in noop mode.
 
-      When applying a resource in noop mode, Puppet will check whether it is in sync,
+      When applying a resource in noop mode, OpenVox will check whether it is in sync,
       like it does when running normally. However, if a resource attribute is not in
-      the desired state (as declared in the catalog), Puppet will take no
+      the desired state (as declared in the catalog), OpenVox will take no
       action, and will instead report the changes it _would_ have made. These
-      simulated changes will appear in the report sent to the primary Puppet server, or
+      simulated changes will appear in the report sent to the primary OpenVox server, or
       be shown on the console if running puppet agent or puppet apply in the
       foreground. The simulated changes will not send refresh events to any
-      subscribing or notified resources, although Puppet will log that a refresh
+      subscribing or notified resources, although OpenVox will log that a refresh
       event _would_ have been sent.
 
       **Important note:**
-      [The `noop` setting](https://puppet.com/docs/puppet/latest/configuration.html#noop)
+      [The `noop` setting](https://docs.openvoxproject.org/openvox/latest/configuration.html#noop)
       allows you to globally enable or disable noop mode, but it will _not_ override
       the `noop` metaparameter on individual resources. That is, the value of the
       global `noop` setting will _only_ affect resources that do not have an explicit
@@ -1265,11 +1265,11 @@ class Type
   end
 
   newmetaparam(:schedule) do
-    desc "A schedule to govern when Puppet is allowed to manage this resource.
+    desc "A schedule to govern when OpenVox is allowed to manage this resource.
       The value of this metaparameter must be the `name` of a `schedule`
       resource. This means you must declare a schedule resource, then
       refer to it by name; see
-      [the docs for the `schedule` type](https://puppet.com/docs/puppet/latest/type.html#schedule)
+      [the docs for the `schedule` type](https://docs.openvoxproject.org/openvox/latest/type.html#schedule)
       for more info.
 
           schedule { 'everyday':
@@ -1290,21 +1290,21 @@ class Type
       attribute name, an array of attribute names, or `all`.
 
       Auditing a resource attribute has two effects: First, whenever a catalog
-      is applied with puppet apply or puppet agent, Puppet will check whether
+      is applied with puppet apply or puppet agent, OpenVox will check whether
       that attribute of the resource has been modified, comparing its current
       value to the previous run; any change will be logged alongside any actions
-      performed by Puppet while applying the catalog.
+      performed by OpenVox while applying the catalog.
 
       Secondly, marking a resource attribute for auditing will include that
       attribute in inspection reports generated by puppet inspect; see the
       puppet inspect documentation for more details.
 
       Managed attributes for a resource can also be audited, but note that
-      changes made by Puppet will be logged as additional modifications. (I.e.
+      changes made by OpenVox will be logged as additional modifications. (I.e.
       if a user manually edits a file whose contents are audited and managed,
       puppet agent's next two runs will both log an audit notice: the first run
       will log the user's edit and then revert the file to the desired state,
-      and the second run will log the edit made by Puppet.)"
+      and the second run will log the edit made by OpenVox.)"
 
     validate do |list|
       list = Array(list).collect(&:to_sym)
@@ -1371,7 +1371,7 @@ class Type
   end
 
   newmetaparam(:alias) do
-    desc "Creates an alias for the resource.  Puppet uses this internally when you
+    desc "Creates an alias for the resource.  OpenVox uses this internally when you
       provide a symbolic title and an explicit namevar value:
 
           file { 'sshdconfig':
@@ -1404,7 +1404,7 @@ class Type
             mode => '0644',
           }
 
-      There's no way here for the Puppet parser to know that these two stanzas
+      There's no way here for the OpenVox parser to know that these two stanzas
       should be affecting the same file.
 
       "
@@ -1445,7 +1445,7 @@ class Type
           }
 
       Tags are useful for things like applying a subset of a host's configuration
-      with [the `tags` setting](https://puppet.com/docs/puppet/latest/configuration.html#tags)
+      with [the `tags` setting](https://docs.openvoxproject.org/openvox/latest/configuration.html#tags)
       (e.g. `puppet agent --test --tags bootstrap`)."
 
     munge do |tags|
@@ -1577,7 +1577,7 @@ class Type
 
   newmetaparam(:require, :parent => RelationshipMetaparam, :attributes => { :direction => :in, :events => :NONE }) do
     desc "One or more resources that this resource depends on, expressed as
-      [resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+      [resource references](https://docs.openvoxproject.org/openvox/latest/lang_data_resource_reference.html).
       Multiple resources can be specified as an array of references. When this
       attribute is present:
 
@@ -1586,17 +1586,17 @@ class Type
       This is one of the four relationship metaparameters, along with
       `before`, `notify`, and `subscribe`. For more context, including the
       alternate chaining arrow (`->` and `~>`) syntax, see
-      [the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html)."
+      [the language page on relationships](https://docs.openvoxproject.org/openvox/latest/lang_relationships.html)."
   end
 
   newmetaparam(:subscribe, :parent => RelationshipMetaparam, :attributes => { :direction => :in, :events => :ALL_EVENTS, :callback => :refresh }) do
     desc "One or more resources that this resource depends on, expressed as
-      [resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+      [resource references](https://docs.openvoxproject.org/openvox/latest/lang_data_resource_reference.html).
       Multiple resources can be specified as an array of references. When this
       attribute is present:
 
       * The subscribed resources will be applied _before_ this resource.
-      * If Puppet makes changes to any of the subscribed resources, it will cause
+      * If OpenVox makes changes to any of the subscribed resources, it will cause
         this resource to _refresh._ (Refresh behavior varies by resource
         type: services will restart, mounts will unmount and re-mount, etc. Not
         all types can refresh.)
@@ -1604,12 +1604,12 @@ class Type
       This is one of the four relationship metaparameters, along with
       `before`, `require`, and `notify`. For more context, including the
       alternate chaining arrow (`->` and `~>`) syntax, see
-      [the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html)."
+      [the language page on relationships](https://docs.openvoxproject.org/openvox/latest/lang_relationships.html)."
   end
 
   newmetaparam(:before, :parent => RelationshipMetaparam, :attributes => { :direction => :out, :events => :NONE }) do
     desc "One or more resources that depend on this resource, expressed as
-      [resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+      [resource references](https://docs.openvoxproject.org/openvox/latest/lang_data_resource_reference.html).
       Multiple resources can be specified as an array of references. When this
       attribute is present:
 
@@ -1618,17 +1618,17 @@ class Type
       This is one of the four relationship metaparameters, along with
       `require`, `notify`, and `subscribe`. For more context, including the
       alternate chaining arrow (`->` and `~>`) syntax, see
-      [the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html)."
+      [the language page on relationships](https://docs.openvoxproject.org/openvox/latest/lang_relationships.html)."
   end
 
   newmetaparam(:notify, :parent => RelationshipMetaparam, :attributes => { :direction => :out, :events => :ALL_EVENTS, :callback => :refresh }) do
     desc "One or more resources that depend on this resource, expressed as
-      [resource references](https://puppet.com/docs/puppet/latest/lang_data_resource_reference.html).
+      [resource references](https://docs.openvoxproject.org/openvox/latest/lang_data_resource_reference.html).
       Multiple resources can be specified as an array of references. When this
       attribute is present:
 
       * This resource will be applied _before_ the notified resources.
-      * If Puppet makes changes to this resource, it will cause all of the
+      * If OpenVox makes changes to this resource, it will cause all of the
         notified resources to _refresh._ (Refresh behavior varies by resource
         type: services will restart, mounts will unmount and re-mount, etc. Not
         all types can refresh.)
@@ -1636,7 +1636,7 @@ class Type
       This is one of the four relationship metaparameters, along with
       `before`, `require`, and `subscribe`. For more context, including the
       alternate chaining arrow (`->` and `~>`) syntax, see
-      [the language page on relationships](https://puppet.com/docs/puppet/latest/lang_relationships.html)."
+      [the language page on relationships](https://docs.openvoxproject.org/openvox/latest/lang_relationships.html)."
   end
 
   newmetaparam(:stage) do
@@ -1649,7 +1649,7 @@ class Type
       By default, all classes are declared in the `main` stage. To assign a class
       to a different stage, you must:
 
-      * Declare the new stage as a [`stage` resource](https://puppet.com/docs/puppet/latest/type.html#stage).
+      * Declare the new stage as a [`stage` resource](https://docs.openvoxproject.org/openvox/latest/type.html#stage).
       * Declare an order relationship between the new stage and the `main` stage.
       * Use the resource-like syntax to declare the class, and set the `stage`
         metaparameter to the name of the desired stage.
@@ -1834,7 +1834,7 @@ class Type
       # like Puppet::Type::Ssh_authorized_key::ParameterProvider.
       desc <<-EOT
         The specific backend to use for this `#{to_s.split('::')[2].downcase}`
-        resource. You will seldom need to specify this --- Puppet will usually
+        resource. You will seldom need to specify this --- OpenVox will usually
         discover the appropriate provider for your platform.
       EOT
 
@@ -2152,7 +2152,7 @@ class Type
   #  to objects called from elsewhere, or not. ;-)</irony>
   #
   # @comment Types (which map to resources in the languages) are entirely composed of
-  #   attribute value pairs.  Generally, Puppet calls any of these things an
+  #   attribute value pairs.  Generally, OpenVox calls any of these things an
   #   'attribute', but these attributes always take one of three specific
   #   forms:  parameters, metaparams, or properties.
 

data/lib/puppet/util/character_encoding.rb

@@ -1,6 +1,6 @@
 # frozen_string_literal: true
 
-# A module to centralize heuristics/practices for managing character encoding in Puppet
+# A module to centralize heuristics/practices for managing character encoding in OpenVox
 
 module Puppet::Util::CharacterEncoding
   class << self
@@ -22,7 +22,7 @@ module Puppet::Util::CharacterEncoding
         if original_encoding == Encoding::UTF_8
           unless string_copy.valid_encoding?
             Puppet.debug {
-              _("%{value} is already labeled as UTF-8 but this encoding is invalid. It cannot be transcoded by Puppet.") % { value: string.dump }
+              _("%{value} is already labeled as UTF-8 but this encoding is invalid. It cannot be transcoded by OpenVox.") % { value: string.dump }
             }
           end
           # String is already valid UTF-8 - noop
@@ -44,7 +44,7 @@ module Puppet::Util::CharacterEncoding
         # error on ruby's part, ie Encoding::UndefinedConversionError on a
         # failure to encode!.
         Puppet.debug {
-          _("%{error}: %{value} cannot be transcoded by Puppet.") % { error: detail.inspect, value: string.dump }
+          _("%{error}: %{value} cannot be transcoded by OpenVox.") % { error: detail.inspect, value: string.dump }
         }
         string_copy
       end

data/lib/puppet/util/command_line.rb

@@ -135,7 +135,7 @@ module Puppet
               Puppet::ModuleTranslations.load_from_modulepath(configured_environment.modules)
               Puppet::ModuleTranslations.load_from_vardir(Puppet[:vardir])
 
-              # Puppet requires Facter, which initializes its lookup paths. Reset Facter to
+              # OpenVox requires OpenFact, which initializes its lookup paths. Reset OpenFact to
               # pickup the new $LOAD_PATH.
               Puppet.runtime[:facter].reset
             end

data/lib/puppet/util/execution.rb

@@ -106,7 +106,7 @@ module Puppet::Util::Execution
   #   elements should be the individual arguments to that executable.
   # @param options [Hash] a Hash of options
   # @option options [String] :cwd the directory from which to run the command. Raises an error if the directory does not exist.
-  #   This option is only available on the agent. It cannot be used on the master, meaning it cannot be used in, for example,
+  #   This option is only available on the agent. It cannot be used on the server, meaning it cannot be used in, for example,
   #   regular functions, hiera backends, or report processors.
   # @option options [Boolean]  :failonfail if this value is set to true, then this method will raise an error if the
   #   command is not executed successfully.

data/lib/puppet/util/filetype.rb

@@ -193,7 +193,7 @@ class Puppet::Util::FileType
     # Read a specific @path's cron tab.
     def read
       unless Puppet::Util.uid(@path)
-        Puppet.debug _("The %{path} user does not exist. Treating their crontab file as empty in case Puppet creates them in the middle of the run.") % { path: @path }
+        Puppet.debug _("The %{path} user does not exist. Treating their crontab file as empty in case OpenVox creates them in the middle of the run.") % { path: @path }
 
         return ""
       end
@@ -204,7 +204,7 @@ class Puppet::Util::FileType
       when /no crontab for/
         ""
       when /are not allowed to/
-        Puppet.debug _("The %{path} user is not authorized to use cron. Their crontab file is treated as empty in case Puppet authorizes them in the middle of the run (by, for example, modifying the cron.deny or cron.allow files).") % { path: @path }
+        Puppet.debug _("The %{path} user is not authorized to use cron. Their crontab file is treated as empty in case OpenVox authorizes them in the middle of the run (by, for example, modifying the cron.deny or cron.allow files).") % { path: @path }
 
         ""
       else
@@ -258,7 +258,7 @@ class Puppet::Util::FileType
     # Read a specific @path's cron tab.
     def read
       unless Puppet::Util.uid(@path)
-        Puppet.debug _("The %{path} user does not exist. Treating their crontab file as empty in case Puppet creates them in the middle of the run.") % { path: @path }
+        Puppet.debug _("The %{path} user does not exist. Treating their crontab file as empty in case OpenVox creates them in the middle of the run.") % { path: @path }
 
         return ""
       end
@@ -269,7 +269,7 @@ class Puppet::Util::FileType
       when /can't open your crontab/
         ""
       when /you are not authorized to use cron/
-        Puppet.debug _("The %{path} user is not authorized to use cron. Their crontab file is treated as empty in case Puppet authorizes them in the middle of the run (by, for example, modifying the cron.deny or cron.allow files).") % { path: @path }
+        Puppet.debug _("The %{path} user is not authorized to use cron. Their crontab file is treated as empty in case OpenVox authorizes them in the middle of the run (by, for example, modifying the cron.deny or cron.allow files).") % { path: @path }
 
         ""
       else
@@ -309,7 +309,7 @@ class Puppet::Util::FileType
     # Read a specific @path's cron tab.
     def read
       unless Puppet::Util.uid(@path)
-        Puppet.debug _("The %{path} user does not exist. Treating their crontab file as empty in case Puppet creates them in the middle of the run.") % { path: @path }
+        Puppet.debug _("The %{path} user does not exist. Treating their crontab file as empty in case OpenVox creates them in the middle of the run.") % { path: @path }
 
         return ""
       end
@@ -320,7 +320,7 @@ class Puppet::Util::FileType
       when /open.*in.*directory/
         ""
       when /not.*authorized.*cron/
-        Puppet.debug _("The %{path} user is not authorized to use cron. Their crontab file is treated as empty in case Puppet authorizes them in the middle of the run (by, for example, modifying the cron.deny or cron.allow files).") % { path: @path }
+        Puppet.debug _("The %{path} user is not authorized to use cron. Their crontab file is treated as empty in case OpenVox authorizes them in the middle of the run (by, for example, modifying the cron.deny or cron.allow files).") % { path: @path }
 
         ""
       else

data/lib/puppet/util/log.rb

@@ -116,7 +116,7 @@ class Puppet::Util::Log
     # loglevel changed
     @loglevel = loglevel
 
-    # Enable or disable Facter debugging
+    # Enable or disable OpenFact debugging
     Puppet.runtime[:facter].debugging(level == :debug)
   end
 
@@ -157,7 +157,7 @@ class Puppet::Util::Log
         newdestination(:console)
       end
 
-      # Re-raise (end exit Puppet) because we could not set up logging correctly.
+      # Re-raise (end exit OpenVox) because we could not set up logging correctly.
       raise detail
     end
   end

data/lib/puppet/util/logging.rb

@@ -145,7 +145,7 @@ module Logging
   end
 
   # Logs a warning whose origin comes from Puppet source rather than somewhere
-  # internal within Puppet.  Otherwise the same as deprecation_warning()
+  # internal within OpenVox.  Otherwise the same as deprecation_warning()
   #
   # @param message [String] The message to log (logs via warning)
   # @param options [Hash]
@@ -253,8 +253,8 @@ module Logging
     end
   end
 
-  # Sets up Facter logging.
-  # This method causes Facter output to be forwarded to Puppet.
+  # Sets up OpenFact logging.
+  # This method causes OpenFact output to be forwarded to OpenVox.
   def self.setup_facter_logging!
     Puppet.runtime[:facter]
     true

data/lib/puppet/util/plist.rb

@@ -46,7 +46,7 @@ module Puppet::Util::Plist
                                                   { :failonfail => true, :combine => true })
           return parse_plist(plist)
         rescue Puppet::ExecutionFailure => detail
-          message = _("Cannot read file %{file_path}; Puppet is skipping it.") % { file_path: file_path }
+          message = _("Cannot read file %{file_path}; OpenVox is skipping it.") % { file_path: file_path }
           message += '\n' + _("Details: %{detail}") % { detail: detail }
           Puppet.warning(message)
         end