On Wednesday, April 1, 2015 at 5:17:54 PM UTC-5, Thomas Hallgren wrote:
>
> John,
>
> We're seem to be talking past each other here. The description in HI-14
> mentions facts specifically and that too is available. I can declare this
> for instance:
>
> days_up: "%{scope('system_uptime.days')}"
>
> or simply:
>
> days_up: "%{system_uptime.days}"
>
> and it returns the 'days' item from the structured fact 'system_uptime'.
> IMO, that's "traversing structured data in interpolation tokens, with
> especial focus on structured fact values" but it's obviously not what
> you're looking for.
>
No, that's *exactly* what I'm looking for. I am pleased and somewhat
mollified to find that it's actually included. However, it seems not to be
described anywhere in the docs -- neither in the release notes, nor in the
section of the main (2.0.0) docs that deals with interpolation.
The flip side, however, is that the altered behavior of key interpretation,
although attributed to HI-14 in the release notes and in the git log, *is
no part of the feature actually requested in HI-14*, or in any of its
duplicates. HI-14 has apparently been hijacked to implement an altogether
different behavior than was requested and which acceptance of that ticket
approved. All of the documentation around this ticket, other than the
ticket itself, focuses on the key interpretation side. The bulk of the new
tests focus on the key interpretation side. Even the initial answer to my
question here focused on key interpretation. That HI-14's actual requested
behavior was implemented, too, as an apparent afterthought, is little
consolation.
With the key interpretation difference being a breaking change, the change
management process has *failed* if that behavior change indeed was nowhere
requested or approved. Therefore, as a matter of a disciplined approach to
process, I would like to see the key interpretation part of the change
backed out. Realistically, I have no expectation that that will actually
happen. What needs to happen, though, is that the release notes be updated
to document the key interpretation change as a breaking change, and that at
least the main docs document the extended interpolation behavior (at all).
Were I in PL's management, I would have additional items for that list.
John
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-dev/673143a1-1d76-448d-a402-a518135748c0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
