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

environment.conf modulepath should accept globs

          Details

          • Type: Improvement
          • Status: Closed
          • Priority: Normal
          • Resolution: Fixed
          • Affects Version/s: None
          • Fix Version/s: PUP 5.5.2, PUP 6.0.0
          • Component/s: None
          • Labels:
            None
          • Template:
          • Acceptance Criteria:
            Hide

            Existing behavior should not be impacted, but putting a glob in modulepath should cause that glob to be expanded per Ruby's Dir.glob matching criteria.

            Show
            Existing behavior should not be impacted, but putting a glob in modulepath should cause that glob to be expanded per Ruby's Dir.glob matching criteria.
          • Sub-team:
          • Team:
            Coremunity
          • Sprint:
            Platform Core KANBAN
          • Release Notes:
            New Feature
          • Release Notes Summary:
            The `modulepath` as defined in `environment.conf` can now accept globs in the path name.
          • QA Risk Assessment:
            No Action

            Description

            The "modulepath" parameter in environment.conf should support the use of globs in the path specification, but currently does not.

            The use of globs allows somewhat elegant solutions to problems not found in environments which require something more complex than a standard Puppet environment layout and workflow.

              Attachments

                Activity

                  jsd-sla-details-panel

                    People

                    • Assignee:
                      melissa Melissa Stone
                      Reporter:
                      seanmil Sean Millichamp
                    • Votes:
                      2 Vote for this issue
                      Watchers:
                      14 Start watching this issue

                      Dates

                      • Created:
                        Updated:
                        Resolved:

                        Zendesk Support