Uploaded image for project: 'Puppet'
  1. Puppet
  2. PUP-6576

Deprecate the data_binding_terminus setting under the control of --strict

    Details

    • Type: Task
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.9.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Team:
      Puppet Developer Experience
    • Story Points:
      1
    • Sprint:
      PDS 2016-11-02, PDS 2016-11-16, PDS 2016-11-30, PDE 2016-12-14
    • Release Notes:
      Deprecation
    • Release Notes Summary:
      Deprecate data_binding_terminus settings other than 'hiera' and 'none', under the control of --strict
    • QA Risk Assessment:
      No Action
    • QA Risk Assessment Reason:
      deprecation warning, covered by unit tests

      Description

      https://docs.puppet.com/puppet/latest/reference/configuration.html#databindingterminus

      This setting ostensibly controls how Puppet does automatic class parameter lookup.

      I don't think it quite works that way anymore. AFAIK, everything goes through Puppet lookup, which delegates to Hiera for the first (global) layer of lookups.

      Should we remove this setting? Should we replace it with something else?

      UPDATE


      The data_binding_terminus setting should be deprecated as the goal is to have not singleton/global data configured. It should all be defined per environment and use lookup.
      To not drive people crazy the deprecation should use the --strict option to issue a deprecation warning in Puppet 4.9.0 at warning level for both strict=error and strict=warning. We do not want to make it an error quite yet as it requires having switched to lookup in all used environments.

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              nick.fagerlund Nicholas Fagerlund
              QA Contact:
              Eric Thompson
            • Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Zendesk Support