Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.4.0
    • Component/s: None
    • Labels:
      None
    • Release Notes:
      Bug Fix
    • Release Notes Summary:
      Hide
      The pluginsync setting is deprecated. By default, puppet will automatically do a pluginsync when requesting a new catalog, and will not pluginsync when applying a cached catalog. If pluginsync is specified explicitly on the command line or puppet.conf, then puppet will continue to observe the value of the setting.
      Show
      The pluginsync setting is deprecated. By default, puppet will automatically do a pluginsync when requesting a new catalog, and will not pluginsync when applying a cached catalog. If pluginsync is specified explicitly on the command line or puppet.conf, then puppet will continue to observe the value of the setting.

      Description

      The pluginsync setting should be deprecated and a warning issued if the setting is specified explicitly on the command line or puppet.conf. In 5.x, the setting will be removed. The motivation is because catalog and plugins can be inconsistent with the following combinations:

      pluginsync=false
      use_cached_catalog=false
      

      Will cause the agent to get the latest catalog, but use older plugins. The new catalog may reference property/parameters that the old plugins don't know how to manage, or the agent may not have any plugins. Worse, the agent run may succeed, but due to semantic differences between the catalog and plugins, not achieve the desired state.

      OR

      pluginsync=true
      use_cached_catalog=true
      

      Will cause the agent to use an old catalog with the latest plugins. The new pluginsync may have removed support for managing property/parameters contained in the catalog.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                josh Josh Cooper
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support