Uploaded image for project: 'Hiera'
  1. Hiera
  2. HI-503

Automatic Parameter Lookup Multi Hierarchy

    Details

    • Type: New Feature
    • Status: Closed
    • Priority: Normal
    • Resolution: Duplicate
    • Affects Version/s: HI 3.0.6
    • Fix Version/s: None
    • Component/s: Community, PE
    • Labels:
      None
    • Template:

      Description

      Currently since 1.x and still in 3.x there is a limitation of multi hierarchy in automatic parameter lookups.
      Many public component modules found online (including forge) utilize parameterized classes but if someone is using multi-hierarchy merging via deep or deeper merge_behavior this doesn't work and is known/documented limitation.
      Problem is this is fine probably for 90% of people but those people who are utilizing multi hierarchy lookups or different hiera backends (yaml/eyaml even at same hierarchy level) are now required to open pull requests to change:

      class foo ( $config = undef) {
      }
      class foo::config { 
        $config = $::foo::config
      }
      

      to

      class foo ( $config = undef) {
      }
      class foo::config (
        $config = hiera_hash('foo::config',$::foo::config)
      }
      

      While this is doable it's a work around for a long time known limitation.
      Can we correct the limitation so it works within the parameterized class?

        Attachments

          Issue Links

            Activity

              jsd-sla-details-panel

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  cdenneen Chris Denneen
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved:

                    Zendesk Support