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

Pick up bindings from module's Metadata.json

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 4.3.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Epic Link:
    • Story Points:
      3
    • Sprint:
      Language 2015-08-05, Language 2015-08-19
    • Release Notes:
      New Feature
    • Release Notes Summary:
      A module's {{metadata.json}} can now define the name of a 'data in modules' data provider directly without the need of specifying the same using the lower level bindings system which required ruby coding.

      Description

      With the configuration of a modue's data provider moving to Metadata.json, the initialization of the bindings system must also look in this metadata to map and add the appropriate bindings.

      This could either be done by one of the existing bindings provider (that scans modules) or added as yet another bindings provider. The former is probably both easier and has better performance as it avoids yet another scan of all modules on the module path.

      Also see PUP-4489 that defines the metadata in question that needs to be mapped and added as bindings.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                henrik.lindberg Henrik Lindberg
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support