Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Henrik Lindberg Release Notes Summary: Part of new feature Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Shaigy Nixon commented on PUP-4486 Re: Add a JSON data provider Validated in PUP-4485 , resolving. Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Shaigy Nixon assigned an issue to Shaigy Nixon Puppet / PUP-4486 Add a JSON data provider Change By: Shaigy Nixon Assignee: qa Shaigy Nixon Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg assigned an issue to qa Puppet / PUP-4486 Add a JSON data provider Change By: Henrik Lindberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.11#64026-sha1:78f6ec4) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Steve Barlow Sprint: Language 2015-08-19 , Language 2015-09-02 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider Thinking about datadir - which could default to the /data, and /data. If given and relative it should be relative to those roots. Absolute paths is generally a bad idea for these (on global places), but perhaps something that is needed to be able to temporarily point to something elsewhere on disk. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider I don't think that the hiera specific providers (e.g. Json, Yaml) should be bound the same way as the function/hiera environment/module-providers. The protocol is slightly different. I do think they should be injected though as it should be possible to plugin other providers. Since the backends are mentioned by symbolic name in hiera.yaml, there needs to be a way to lookup the "json", the "yaml", etc. Those that extend with a plugin must be able to specify this mapping. This means using a multibinding with the symbolic name as the key. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider Regarding file location for the JSON data that backs this provider. I assume that the provider will not be bound but rather instantiated by the Hiera data provider mentioned in PUP-4485. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Thomas Hallgren Comment: I seem to recall that we settled for a solution that uses a predetermined and unchangeable name and location for the json files that backs this provider. [~henrik.lindberg], do you have any preferences? I need two locations, one for env and one for the module. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider I seem to recall that we settled for a solution that uses a predetermined and unchangeable name and location for the json file that backs this provider. Henrik Lindberg, do you have any preferences? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider Summary of chat conversation about 'dots' and interpolation: (global) Hiera cannot use keys with '.' in them, since if an attempt is made to look up such a key, it means navigation The lookup function should not have such semantics, keys are just a string value; any post/processing navigation should be done on the value lookup returns. This means that lookup should skip looking up in global hiera if the key contains a '.' The data provider API should also allow any String key, dots in the key should not trigger any navigation. Navigation and interpolation of values the "hiera way" is a function that is performed by hiera backends. When a hiera backend interpolates a lookup it first drops of a part starting with a '.', looks up the first part (the key), and then applies the navigation. This prevents the 'dot navigation' syntax from leaking into the lookup/data-provider API. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 t
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider "You cannot lookup a value for a key with dots in it - it is an illegal puppet name anyway." Although you can have dots in the name in the following cases: when call the lookup function with a key that is a non-empty string when you use such a name in interpolation expressions At least the Hiera provider must be sensitive to those dots in both cases. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider "bringing interpolation to all implementations" means that interpolation expressions will be encountered and evaluated by all implementations. The evaluation is instant and takes place before merges etc. happen, just as they do in Hiera today (i.e. no need for lazy evaluation). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider The providers we are doing now are hiera specific data providers following the current hiera scheme as much as possible. I can imagine supporting a different version of that format some time in the future - to clean up and make the format sane. I think it may be premature to try to implement general json/yaml backends, or to think too much about what a better format should be (except possibly where there are implementation concerns we want to address) - for now just do what is required for backward compatible hiera data. Not sure about what "bringing interpolation to all implementations" means in the context of say the function data provider. Does that mean that users can get interpolation by returning interpolation expressions in strings? When using the function provider, there is also the opportunity to use more advanced lookup semantics - e.g. specify deep merge etc, but we have no way of making such calls be lazy. I see such functionality as a stretch goal and not covered by this ticket. Regarding "names" - we have keys, they follow puppet naming (no dots), and navigation of a resulting value of a lookup (has dots). You cannot lookup a value for a key with dots in it - it is an illegal puppet name anyway. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider No need to have two mechanisms. Just wanted to assert that we do intend to use names that have both double colons and dot-notations in them. There are alternatives such as allowing a name to be separated by either dots or double colon (but not both in the same name). Another thing to have in mind is that a JSON or YAML provider doesn't necessarily imply a hiera provider (or does it?). I intend to make the concept of interpolation available to all providers b.t.w. Not just by Hiera with JSON and YAML. I see that as implied when weaving this together. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider The lookup part can be qualified in the Puppet way with double colons, but from a hiera perspective the double colons are just part of the key - there is no difference in semantics between x::y::z and say xaayaaz except for the final step of directing a fully qualified key to the corresponding module data provider - e.g. x::a is directed to module a's provider if the global and environment providers did not find a resolution for the full key. The operations of applying dot notation expressions comes after the resolution of the name. Don't see why we need two lookup mechanisms? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider We use double colon to access module data a::b and in Hiera we recently introduced dot notation to navigate in hashes and arrays. We now face the possibility of names like a::b.c.d or a::b.3. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider > Another detail that we need to sort out is the Hiera qualified lookup using dot-separated names. Do we want two types of qualified names? Not sure what you mean by that, can you clarify? The format should be compatible with current hiera data. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider And you're OK with 'scope' being the default? Keeping it that way will be more backward compatible but having 'lookup' be the default seems more logical. 'scope' should be default, yes. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider Another detail that we need to sort out is the Hiera qualified lookup using dot-separated names. Do we want two types of qualified names? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider And you're OK with 'scope' being the default? Keeping it that way will be more backward compatible but having 'lookup' be the default seems more logical. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Steve Barlow Sprint: Language 2015-08- 05 19 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider Scope gets you all top scope variables - from facts (regular and trusted), server settings, as well as variables set in top scope. For that reason I think 'scope' is not too bad. I am more concerned about 'hiera' (implies a particular kind of lookup, but it isn't) - there I want the synonym 'lookup'. I can imagine that we create a better 'hiera' data format, and better interpolation at some point. For a first release I want things to be as compatible as possible. Maybe the format-version of data files is configurable in the 'hiera.yaml' as a backend parameter? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider So perhaps we should introduce a synonym the synonym for 'scope' like 'fact' or something that is more to the point? I really don't like 'scope'. It being the default in Hiera is also a real problem. I think one would assume that an interpolation performed in a data provider would do a real lookup by default, not just look at facts. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider 'scope' is an access to a variable in puppet's scope - has nothing to do with lookup and data binding (neither in current hiera, nor in what we are now building). It is basically for interpolating facts. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider I understand that. But in your previous comment you wrote that "'hiera' means lookup (data in modules)". I interpret that as 'hiera' would bypass the global lookup (i.e. global, environment, and then module) and instead go directly to the module. If not, then what's the difference between 'scope' and 'hiera'? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider No, you can use lookup without a qualified name; it should work just like all other lookups, first look in global hiera, then in the environment data provider, and then (if the name is qualified) in the module data provider for that name space. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider Using a 'data in modules' lookup implies that the name is qualified, i.e. module_name::key. That won't fly very well if we're trying to simulate legacy hiera behavior. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg commented on PUP-4486 Re: Add a JSON data provider Interpolation 'hiera' means lookup (data in modules), and 'scope, means looking up a variable in puppets global scope. Passing around a guard is ok in first implementation, but does not fully solve the problem since you can end up in a function data provider that calls back in. We cannot pass the guard around everywhere. We could keep it in the puppet context instead now that we know that it is always there. Global hiera cannot call any function (nor find anything from data in modules, so it can continue to work the way it does. henrik Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren commented on PUP-4486 Re: Add a JSON data provider Regarding interpolation. In order to prevent endless recursion, we need to pass a recursion guard somehow. Hiera does this in a 'context'. What mechanism do we want to use for the data provider implementation? A KISS approach is to extend the DataProvider.lookup with a fourth argument but I recall discussions about traversing stack frames. Hiera has the concept of "interpolation method". Instead of just writing "%{foo}", one can use the syntax "%{('foo')}" where is one of scope (the default), hiera, literal, or alias. Their mapping is not self evident. I will make the following assumptions for now: We add a recursion guard to the lookup call. If we have module binding to a 'hiera' data provider that in turn makes use of a JSON data provider (the one discussed here), then I assume that the hiera interpolation method should use that module specific data provider. Same thing would be true for an environment_data_provider bound to 'hiera'. This implies that the data_providers "below" the hiera data_provider must know their parent. What should happen if the JSON provider is used as a stand-alone? The scope method will result in a global lookup (like calling the lookup function). Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4486 Add a JSON data provider Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Steve Barlow updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Steve Barlow Sprint: Language 2015- 07 08 - 22 05 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Henrik Lindberg Fix Version/s: PUP 4.x Fix Version/s: PUP 4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Henrik Lindberg Sprint: Language 2015-07- 08 22 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Henrik Lindberg Sprint: Language 2015- 06 07 - 24 08 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-4486 Add a JSON data provider Change By: Kylo Ginsberg Sprint: Language 2015-06- 10 24 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4486) Add a JSON data provider
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-4486 Add a JSON data provider Issue Type: New Feature Assignee: Unassigned Created: 2015/04/29 6:08 AM Fix Versions: PUP 4.2.0 Priority: Normal Reporter: Henrik Lindberg Add a data provider for a JSON file. The provider is instantiated with a .json file representing a hash that is used to perform lookup. This implementation should be hiera-like in that it should perform interpolation as done by hiera version 2.0. Add Comment