Uploaded image for project: 'Puppet Development Kit'
  1. Puppet Development Kit
  2. PDK-1616

Update validators to work in a Control Repo context

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: PDK 1.17.0
    • Component/s: None
    • Template:
    • Acceptance Criteria:
      • Has tests to prove that the behaviour changes correctly when in a module or control repo context.
    • Team:
      Puppet Developer Experience
    • Release Notes:
      New Feature
    • Release Notes Summary:
      Hide
      The PDK can now optionally validate Control Repositories! This is a new feature and requires the 'controlrepo' feature flag to be set.

      Note that validation generally requires a Gemfile, much like a Puppet Module. The PDK will try and validator without a Gemfile but you may find it doesn't behave as you would like. We're working on making a better way to manage the Gemfile's in Control Repositories.

      Show
      The PDK can now optionally validate Control Repositories! This is a new feature and requires the 'controlrepo' feature flag to be set. Note that validation generally requires a Gemfile, much like a Puppet Module. The PDK will try and validator without a Gemfile but you may find it doesn't behave as you would like. We're working on making a better way to manage the Gemfile's in Control Repositories.
    • QA Risk Assessment:
      Needs Assessment

      Description

      This ticket will track the work to update all existing validators to work correctly in a Control Repo context

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              glenn.sarti Glenn Sarti
              Reporter:
              glenn.sarti Glenn Sarti
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Zendesk Support