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

puppet module validate

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Won't Do
    • Affects Version/s: PUP 4.4.0
    • Fix Version/s: None
    • Component/s: PMT
    • Labels:
      None
    • Environment:

      N/A

    • Template:

      Description

      In my opinion, the puppet module face should have a validate option that can take a path to a module (e.g. /etc/puppetlabs/code/environments/production/foo or more likely /some/local/repo/foo)

      The idea is that it would be used by a more junior or novice admin who is manually creating a module to validate the structure. It might observe that "manifests" is missing (perhaps called "manifest" or validating that each of the manifests is appropriately named so puppet can find it (class foo::bar is in bar.pp). Additionally, it could recursively call puppet parser validate on each manifest, validate erb, yaml, etc. as appropriate.

      This would help new users (such as those who take fundamentals, practitioner, etc.) to troubleshoot more easily. Additionally, it would lower the bar to entry for new users of puppet who don't take our trainings.

      Additionally, it could be helpful to people getting ready to publish a module to ensure that its ready to go.

        Attachments

          Activity

            People

            Assignee:
            Unassigned
            Reporter:
            paul.anderson Paul Anderson
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Zendesk Support