Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Fix Version/s: PUP 4.10.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Issue Type: New Feature Assignee: Unassigned Created: 2017/03/10 5:15 AM Priority: Normal Reporter: Henrik Lindberg In order to be able to filter or modify a value bound at a lower precedence in ways that the built in hiera interpolation or aliasing features can handle it is of great value to be able to lookup the value that would be the result of lower precedence entries and return that. This mechanism should be available via the $context object via a lookup_below(key). This method takes a no args lambda that is called if the lookup results in not_found. If no lambda is given and the lookup_below(key) results in not_found that also becomes the result of the function calling lookup_below (it does not return to it). The rest of the arguments to the lookup_below are the same as for a lookup. As an example a user may do something like this for the lookup of key return "some prefix: #{context.lookup_below(key)" Without the lookup_below feature this is impossible since a lookup of the same key would lead to an endless rec
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Team: Puppet Developer Experience Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Fix Version/s: PUP 4.10.0 Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22 , PDE 2017-04-05 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Wouldn't it be of interest for a function in the global layer to bypass the environment layer? Use of "below" will block that. Why not have a #lookup_in_layer(key, layer) instead, with the same constraints as in PUP-7333, i.e. a module would not be allowed to use that function, an environment would only be allowed to use 'module', but global could use both 'environment' and 'module'. I think that would vouch for some consistency between this ticket and PUP-7333.< /p> Alternatively, change the semantics in PUP-7333 to only allow the layer below, which would prevent the global from bypassing environment. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy I don't understand the use case for that. The purpose of "lookup_below" is to be able to transform or filter what would otherwise have been returned for a given key. I also don't understand how a lookup_in_layer would be an alternative, it would need "lookup in levels below in same layer" as well. Also given PUP-7333, you don't really know the ordering of layers and levels. So something like "below" is needed as a filtering/transforming function would otherwise have constraints on where it can be placed. The name can naturally be something other than "lookup_below", but it is important that it returns the result that would have been returned if the function calling lookup_below did not exist. The suggestion to change PUP-7333 to say "layer below" would be fine, but "below" is not the same thing in both cases - in this ticket "below" means all levels in all layers that are below the level making the call. In PUP-7333 it would need to mean the layer below this layer. That change in 7333 would work for me. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Strike my proposal regarding change to lookup_below. It's fine as it is. I've come to realize that it's PUP-7333 I'm worried about. Let's move the discussion to that ticket. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy When discussing this - we found a design flaw. A function cannot simply filter without the framework knowing it is filtering as that would produce strange results when a merge lookup is performed (it would merge the unfiltered and filtered results). New proposal: A new kind of function: filter_key is added. It has a signature that is the same as the lookup_key function, but with an added parameter value_below. The framework will call this function "on the way up the hierarchy" after having produced the partial result that is produced by all definitions/levels/layers below the filter_key entry. The call is then made to the given function and the partial result is given as the value_below. If the function wishes to do no filtering it simply returns the found value. If it wants to replace it with something else, it returns that value. If it wants to, it can call context.not_found to filter out the value completely. The value_below is not just the value since the lookup below can result in both undef and a not_found exception. To enable the function to react to all situations the value_below is therefore a Struct[found => Boolean, value => Any]. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy It's unclear to me how the result from this filter would participate in a merge. Let's assume that we have the participants A, F, B, and C where F is the filter. Without the filter, A, B, and C would be merged. What should be merged instead? Is it A, F, and C or just A and F? I.e. does F "take over" all subsequent entries or just the next one? If it's the latter, then I assume that F should be fed the already merged result of B and C? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy A follow-up question is of course if it wouldn't be better if the F took over everything so that the framework stops processing at F. Instead it's up to F to do the rest using a lookup_below. That will give F a chance to override merge strategies and even change the key. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Alternative proposal. Combine the ability to reorder layers with the ability to add a filter. Make it clear what it is that a filter acts on by declaring a sub-hierarchy: hierarchy: - name: Common path: common.yaml - sub_hierarchy: filter: # optional lookup_key function acting on sub-hierarchy using Context methods. hierarchy: # normal hierarchy - name: Roles
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy I don't see how that solves "default hierarchy" inside of a module. Including the underlying layer more than once is too weird. For every filter I want I must introduce one sub hierarchy. I must be explicit about the lower layer or the filter will not filter data from lower layer(s). I also struggle to come up with meaningful use cases where I would need an actual nested hierarchy (except for the default hierarchy in a module, but that cannot be intermixed into the regular hierarchy). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy The default hierarchy of a module will still be consulted when everything else fails, and only then. And you don't need to introduce any more hierarchy elements than before. Just organize them differently (which also highlights what the filter is using). I'd consider that a very useful way to declare what it is you are doing. The filters are in fact mechanism that introduces nesting. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Revised version of my alternative proposal. Instead of using the term sub_hierarchy, we should simply use hierarchy for the nested hierarchies as well and allow that a hierarchy has a filter functions. Filter functions can be inserted anywhere in a hierarchy as a single string element (as opposed to the hash elements used for other hierarchy entries). A filter then acts on everything "below" its declaration. In essence, this means that a filter doesn't need to act on a sub hierarchy. I may (if declared as the first element in a hierarchy), but it can also be declared in arbitrary places in a flat hierarchy, e.g.: hierarchy: - name: Common path: common.yaml - my_filter_func - name: Filtered data path: filtered.yaml Logically, this would be exactly the same as declaring: hierarchy:
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy So, are you saying that if the filter is in the top level hierarchy, then all entries below it in the same hierarchy and all entries in all lower layers are filtered? (assuming that the next layer down is not specifically referenced and therefore ends up last in the top hierarchy in the hiera.yaml in question). If that is true, then this proposal is workable. I still think the extra ability to have a sub hierarchy may be overkill. (I understand that this is made possible because it becomes a composition of uniform parts which is nice because of its generality). One thing to note - it must be possible to pass options to a filter function (e.g. you want to replace "blue" with "green" and don't want that hardcoded in the function itself). You may also want to call the same filter function with different arguments in different places in the hierarchy, and you therefore need a name for the entry to understand explain output. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Yes, that's what I'm saying. Having sub hierarchies might be overkill, but please consider that their presence solves three problems. The ability to reorder (PUP-7333), since any hierarchy containing a sub-hierarchy is prevented from continuing with the next layer. The ability to have more than one filter that acts on diverse parts of the hierarchy. The ability to add unfiltered parts after the filter. If options are needed, then the filter function cannot be an array. It must be a hash, and as such, must be uniquely identified from normal hierarchy entries. Perhaps by using the unique key 'filter' for the function. Locations (urls, paths, globs, mapped paths) must be forbidden. While using 'options' as a key might be appealing at first, we might want to consider some other key to avoid that it is assigned the 'options' from the 'defaults' entry. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy I don't understand your comment in #1 - It must naturally be possible to filter what comes from a lower layer - the feature is more or less useless otherwise. Are you saying that it is illegal to reference a layer in a subhierarchy? Thus, if you want to filter a layer you must have your filter in the hiera.yaml's top hierarchy? The #2 is the feature I think is overkill and that would require allowing lower layer multiple times in different sub hierarchies in order to be of real and general value. I can however accept that you can do this as there may be cases where you are combining some backends in the same layer and you need to filter something locally. The filter acts like a wrapper where you can introduce your own post processing. The #3 seems useful. If answer to my question about #1 is 'yes', then the combination of filtered sublayer with an unfiltered thing after the filter does not seem possible... If #1 is really "only the top hierarchy, or one of the sub-hierarchies may include the lower layer(s), then it works. Some details: Options are required path(s)/glob(s)/mapped-paths not supported (error) uri support is useful - for example, may filter by talking to a service and need a URL. Seems strange if not the same param ("uri") for this. I think using a different name for "options" is more confusing than applying the general rule. Also think filter functions are more likely to take parameters than being completely hardcoded, having to pass an empty options hash to override defaults is therefore a very rare operation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Of course you should filter what comes from a lower layer. That's why I propose that it works the way it does. A sub-hierarchy takes over the responsibility for the lower layers from it's parent. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy So if I have a sub hierarchy then it automatically filters the lower layer(s)? That was surprising. What if I have two sub hierarchies ? Confused. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy This is covered in my original proposal (starts with "Alternative proposal."). See #3 above "pros" and also what I mention as a caveat. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy How I think it would work is that you can include the lower layer(s) anywhere - either in the top hierarchy in the hiera.yaml, or in a sub hierarchy. If it is not included anywhere, it is placed last in the top hierarchy. You are only allowed to include the lower level(s) once in a hiera.yaml. Is this correct? Then it works for me. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy That's not how I intended it, but what you propose would work too. I though of a hierarchy as something that always includes the lower layers except when it contains a sub-hierarchy. When it does, the sub-hierarchy "takes over" that responsibility. This behavior is consistent with how the top layer works today (it traverses lower layers without any explicit instruction to do so). In a nested sub-hierarchy, that "take over" would still result in just one hierarchy (the leaf) actually performing the traversal. The exception would be when there are multiple parallel sub-hierarchies, in which case, each leaf would traverse the lower layers unless that could somehow be blocked. That would be solved by adding a keyword for blocking such traversal. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy I prefer it the way I described. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Thomas Hallgren commented on PUP-7332 Re: add ability to lookup "below" in hierarchy How do you propose that "include the lower layers here" is declared? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title David McTavish updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: David McTavish Labels: final_triage Add Comment This message was sent by Atlassian Jira (v8.13.2#813002-sha1:c495a97) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.179591.1489151703000.20913.1638811380043%40Atlassian.JIRA.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22, PDE 2017-04-05 , PDE 2017-04-19 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Eric Sorenson commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Is this truly necessary? Has anyone asked for it? It seems like in practice it could lead to a great deal of complexity. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy Eric Sorenson the intention of this feature is to be an open way of handling various requests for additions/changes/custom "deep merge" behaviors and requests for interpolation functions. The typical thing asked for is the need to exclude values from a collection and where "knockout prefix" cannot do the job. There has been no requests for general filtering, but I suspect that is because users have not yet encountered the situations where it becomes important (as they are just starting out using hiera 5 features). The alternative when not being able to filter is to change manifests to use manual calls to lookup rather than using APL as that is the only way a user can modify the returned values. At the moment as we are discussing how to implement this feature, it has snowballed into a proposal for "filtered-sub-hierarchy" which I think is conceptually overly complex. Even if it is how the implementation would work I don't think that is something users really need to be able to do. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Eric Sorenson Fix Version/s: PUP 5.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19 , PDE 2017-05-03 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19, PDE 2017-05- 03 17 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19, PDE 2017-05- 17 31 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Ethan Brown Team: Puppet Developer Experience Agent Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Ethan Brown Labels: triaged Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Ethan Brown updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Ethan Brown Sprint: PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19, PDE 2017-06-07 Agent N+1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-7332 add ability to lookup "below" in hierarchy Change By: Henrik Lindberg Sprint: PDE 2017-03-22, PDE 2017-04-05, PDE 2017-04-19, Agent N+1 Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-7332) add ability to lookup "below" in hierarchy
Title: Message Title Henrik Lindberg commented on PUP-7332 Re: add ability to lookup "below" in hierarchy I read through this again - and I find the subhierarchy idea too complex to understand. If PUP-7333 ends up being that you can define where the lower precedence layer(s) are inserted with insert_next, then you have the ability to define the order of all levels in all layers. You should then be able to insert a filter anywhere in there to filter a particular key or set of keys. When resolving simply skip over the filter, when the value from lower precedence levels is known at the point where the filter is, the filter function is called with the key and the resolved value. What it returns replaces what was resolved. It should have a regexp that keys must match in order for the filter to kick in (without such a regexp it would be called for every key). Different merge strategies does not affect the filtering as it applies to the normal resolution, then there is a replacement (or not), that value is then merged with other higher precedence resolutions. With such an implementation there is no need for the earlier proposed "lookup_below" feature. Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.