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

`puppet module build` should use `metadata.json` as input format

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PUP 3.6.0
    • Component/s: None
    • Labels:
      None
    • Template:
    • Story Points:
      1
    • Sprint:
      Week 2014-4-30 to 2014-5-7

      Description

      `puppet module build`

      This action is most impacted by this change though we will maintain compatibility with users still using Modulefile as their input format. Here's how that will work when a user initiates build.

      • If the user provides a Modulefile at the root of their module, PMT will use it exclusively to build the release and issue a deprecation warning. Let's call this the legacy build process.
      • If the user provides a metadata.json file at the root of their module, PMT will use it exclusively to build the release. Let's call this the v3 build process.
      • If the user providers both a Modulefile and metadata.json, PMT will use the v3 build process, ignoring the Modulefile but issuing a warning against including both files in the module root.
        The legacy build process will issue a deprecation warning but will otherwise behave as it does today.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              pieter Pieter van de Bruggen
              Reporter:
              pieter Pieter van de Bruggen
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support