Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5395
There's no way to set resolution_type when using data bindings
Change By:
Thomas Hallgren
Because it's the responsibility of the caller to set `resolution_type` in hiera, and there is no explicit caller when using data bindings, there's no way to tell hiera to use the array (append) or hash (merge) resolutions. This is a pretty bad flaw as it prevents sophisticated lookups like deep merges (or, well, any merges at all) when using the fancy data bindings. UPDATEThis new feature allows the default lookup options to be individually controlled per parameter by binding a hash to the key {{lookup_options}}, where each key in that hash is the fully qualified name of a parameter. The value should be a hash that defines the default lookup options for that key.The {{lookup_options}} are looked up with hash-merge, making it possible to compose the content of the {{lookup_options}} hash using multiple sources (data files in a hierarchy, across, global hiera, environment data provider and module providers. With data in modules in effect, this means that a module can specify the behavior of its own parameters (e.g. 'merge' for some of its keys). At higher priority layers no action needs to be taken except if there is a desire to change the default specification.The options bound per key under {{lookup_options}} are also used as the defaults for the {{lookup}} function. Note that the defaults does not apply to the {{hiera_xxx}} family of functions, they continue to work as before (as these functions themselves represents specifying some of the options (e.g. hiera_array is for arrays, and hiera_hash is for hashes). It is recommended to always use the {{lookup}} function instead of the {{hiera_xxx}} functions since they a) work with "data in modules", and b) makes use of the default lookup options. The only thing that can be specified (currently) is the {{merge}} option (as specified by the {{lookup}} function). This means that the behavior can be one of the strings: {{first}}, {{unique}}, {{hash}}, {{merge}}, {{deep}}, or a hash with its {{strategy}} key set to one of those strings, and where further options are {{knock_out_prefix}}, {{sort_merged_arrays}}, {{unpack_arrays}}, and {{merge_hash_arrays}} - (See the {{lookup}} function for details). The {{lookup_options}} will never be found when used as the key in a regular lookup. It's not considered to be _data_ in the normal sense but rather _meta_data_ describing the _data_. Also, there is never a need to prefix the {{lookup_options}} key with a module name since the module name will be determined by looking at the key that initiated the lookup.
Add
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings I updated the description. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings The "hash" is a distinct merge type. A "hash" merge refers to that type (i.e. a naïve merge of hashes). A "deep" merge can be performed on both hashes and arrays so the term "hash" isn't really related to "deep", nor does one imply the other. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Nicholas Fagerlund commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings This ticket description is still insufficient. Module data appears to only be accessed for keys of the form ::. Does lookup_options get an exception to this? It appears to, based on my preliminary testing. What is the nature of this exception? Can a module set hash keys governing lookup keys outside its namespace, or is it limited to those within its namespace? Has this behavior been proven in the testing that's taken place so far? Where? By "hash merge," do you mean the naïve hash merge where the higher-level sources will just knock out the entire value of the "merge" key? Or a deep merge? 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Eric Thompson Assignee: qa Eric Thompson 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Eric Thompson commented on PUP-5395
Re: There's no way to set resolution_type when using data bindings
validated on redhat7 at stable SHA: using the some manifests from the lookup function test in lookup.rb
[root@ivcig3f3n4xejso production]# cat /etc/puppetlabs/code/environments/production/manifests/site.pp
node default {
include data_module
}
[root@ivcig3f3n4xejso production]# cat /etc/puppetlabs/code/environments/production/
environment.conf hieradata/lib/ manifests/modules/
[root@ivcig3f3n4xejso production]# cat /etc/puppetlabs/code/environments/production/hieradata/common.yaml
---
lookup_options:
data_module::hash_name:
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Eric Thompson commented on PUP-5395
Re: There's no way to set resolution_type when using data bindings
without the lookup_options hash: (note the second lookup provides the lookup merge method in the call to lookup())
[root@ivcig3f3n4xejso production]# puppet agent -t --server $(hostname -f)
Info: Using configured environment 'production'
Info: Retrieving pluginfacts
Info: Retrieving plugin
Info: Caching catalog for ivcig3f3n4xejso.delivery.puppetlabs.net
Info: Applying configuration version '1447369188'
Notice: hash_name hiera lookup_options {module_hash_key => hiera_value}
Notice: /Stage[main]/Data_module/Notify[hash_name hiera lookup_options {module_hash_key => hiera_value}]/message: defined 'message' as 'hash_name hiera lookup_options {module_hash_key => hiera_value}'
Notice: hash_name {module_hash_key => hiera_value, env_hash_key => env_class_a}
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Eric Thompson commented on PUP-5395
Re: There's no way to set resolution_type when using data bindings
and with the lookup_options hash in the data binded function:
Info: Caching catalog for ivcig3f3n4xejso.delivery.puppetlabs.net
Info: Applying configuration version '1447369759'
Notice: hash_name hiera lookup_options {module_hash_key => hiera_value, env_hash_key => env_class_a}
Notice: /Stage[main]/Data_module/Notify[hash_name hiera lookup_options {module_hash_key => hiera_value, env_hash_key => env_class_a}]/message: defined 'message' as 'hash_name hiera lookup_options {module_hash_key => hiera_value, env_hash_key => env_class_a}'
Notice: hash_name {module_hash_key => hiera_value, env_hash_key => env_class_a}
Notice: /Stage[main]/Data_module/Notify[hash_name {module_hash_key => hiera_value, env_hash_key => env_class_a}]/message: defined 'message' as 'hash_name {module_hash_key => hiera_value, env_hash_key => env_class_a}'
Notice: Applied catalog in 0.03 seconds
[root@ivcig3f3n4xejso production]# cat modules/data_module/lib/puppet/functions/data_module/data.rb
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Josh Cooper Component/s: DOCS 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Steve Barlow Flagged: Impediment 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Eric Thompson QA Status: Reviewed 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Kenn Hussey Flagged: Impediment 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Probability Reason: specified lookup merge type per data_binding QA Risk Assessment: Medium QA Risk Probability: Low QA Risk Severity: Medium QA Highest Test Level Reason: should be added to existing tests Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Steve Barlow Flagged: Impediment 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Steve Barlow Sprint: Language 2015-10-28, Language 2015-11-11 , Language 2015-12-02 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Sean Griffin Status: Ready for CI Test Assignee: qa 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-5395
There's no way to set resolution_type when using data bindings
Change By:
Thomas Hallgren
Because it's the responsibility of the caller to set `resolution_type` in hiera, and there is no explicit caller when using data bindings, there's no way to tell hiera to use the array (append) or hash (merge) resolutions. This is a pretty bad flaw as it prevents sophisticated lookups like deep merges (or, well, any merges at all) when using the fancy data bindings. UPDATEThis new feature allows the default lookup options to be individually controlled per parameter by binding a hash to the key {{lookup_options}}, where each key in that hash is the fully qualified name of a parameter. The value should be a hash that defines the default lookup options for that key.The {{lookup_options}} are looked up with hash-merge, making it possible to compose the content of the {{lookup_options}} hash using multiple sources (data files in a hierarchy, across, global hiera, environment data provider and module providers. With data in modules in effect, this means that a module can specify the behavior of its own parameters (e.g. 'merge' for some of its keys). At higher priority layers no action needs to be taken except if there is a desire to change the default specification.The options bound per key under {{lookup_options}} are also used as the defaults for the {{lookup}} function. Note that the defaults does not apply to the {{hiera_xxx}} family of functions, they continue to work as before (as these functions themselves represents specifying some of the options (e.g. hiera_array is for arrays, and hiera_hash is for hashes). It is recommended to always use the {{lookup}} function instead of the {{hiera_xxx}} functions since they a) work with "data in modules", and b) makes use of the default lookup options. The only thing that can be specified (currently) is the {{merge}} option (as specified by the {{lookup}} function). This means that the behavior can be one of the strings: {{ first}}, {{ unique}}, {{hash}}, {{merge}}, {{deep}}, or a hash with its {{strategy}} key set to one of those strings, and where further options are {{knock_out_prefix}}, {{sort_merged_arrays}}, {{unpack_arrays}}, and {{merge_hash_arrays}} - (See the {{lookup}} function for details). [~thomas.hallgren] Please review the updated description for correctness.
Add Comment
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Henrik Lindberg, description reviewed and edited. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings PR 4397 merged to master at: af57b50 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren please ping when you have reviewed (or possibly edited) the updated description in this ticket? 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Assignee: Henrik Lindberg Thomas Hallgren 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Added PR-4397 to address the problem that I found. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren Can you make sure the documentation for the lookup function gets updated as well. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5395
There's no way to set resolution_type when using data bindings
Change By:
Henrik Lindberg
Release Notes Summary:
This adds a new feature to automatic data binding and the lookup function that allows the lookup options to be defined in the data by binding keys in a hash bound to the key {{lookup_options}}. This makes it possible to get deep merge behavior for select class parameters.
Release Notes:
New Feature
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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5395
There's no way to set resolution_type when using data bindings
Change By:
Henrik Lindberg
Because it's the responsibility of the caller to set `resolution_type` in hiera, and there is no explicit caller when using data bindings, there's no way to tell hiera to use the array (append) or hash (merge) resolutions. This is a pretty bad flaw as it prevents sophisticated lookups like deep merges (or, well, any merges at all) when using the fancy data bindings. UPDATEThis new feature allows the default lookup options to be individually controlled per parameter by binding a hash to the key {{lookup_options}}, where each key in that hash is the fully qualified name of a parameter. The value should be a hash that defines the default lookup options for that key.The {{lookup_options}} are looked up with hash-merge, making it possible to compose the content of the {{lookup_options}} hash using multiple sources (data files in a hierarchy, across, global hiera, environment data provider and module providers. With data in modules in effect, this means that a module can specify the behavior of its own parameters (e.g. 'merge' for some of its keys). At higher priority layers no action needs to be taken except if there is a desire to change the default specification.The options bound per key under {{lookup_options}} are also used as the defaults for the {{lookup}} function. Note that the defaults does not apply to the {{hiera_xxx}} family of functions, they continue to work as before (as these functions themselves represents specifying some of the options (e.g. hiera_array is for arrays, and hiera_hash is for hashes). It is recommended to always use the {{lookup}} function instead of the {{hiera_xxx}} functions since they a) work with "data in modules", and b) makes use of the default lookup options. The only thing that can be specified (currently) is the {{merge}} option (as specified by the {{lookup}} function). This means that the behavior can be one of the strings: {{unique}}, {{hash}}, {{merge}}, {{deep}}, or a hash with its {{strategy}} key set to one of those strings, and where further options are {{knock_out_prefix}}, {{sort_merged_arrays}}, {{unpack_arrays}}, and {{merge_hash_arrays}} - (See the {{lookup}} function for details).[~thomas.hallgren] Pleas review the updated description for correctness.
Add Comment
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5395
There's no way to set resolution_type when using data bindings
Change By:
Henrik Lindberg
Because it's the responsibility of the caller to set `resolution_type` in hiera, and there is no explicit caller when using data bindings, there's no way to tell hiera to use the array (append) or hash (merge) resolutions. This is a pretty bad flaw as it prevents sophisticated lookups like deep merges (or, well, any merges at all) when using the fancy data bindings. UPDATEThis new feature allows the default lookup options to be individually controlled per parameter by binding a hash to the key {{lookup_options}}, where each key in that hash is the fully qualified name of a parameter. The value should be a hash that defines the default lookup options for that key.The {{lookup_options}} are looked up with hash-merge, making it possible to compose the content of the {{lookup_options}} hash using multiple sources (data files in a hierarchy, across, global hiera, environment data provider and module providers. With data in modules in effect, this means that a module can specify the behavior of its own parameters (e.g. 'merge' for some of its keys). At higher priority layers no action needs to be taken except if there is a desire to change the default specification.The options bound per key under {{lookup_options}} are also used as the defaults for the {{lookup}} function. Note that the defaults does not apply to the {{hiera_xxx}} family of functions, they continue to work as before (as these functions themselves represents specifying some of the options (e.g. hiera_array is for arrays, and hiera_hash is for hashes). It is recommended to always use the {{lookup}} function instead of the {{hiera_xxx}} functions since they a) work with "data in modules", and b) makes use of the default lookup options. The only thing that can be specified (currently) is the {{merge}} option (as specified by the {{lookup}} function). This means that the behavior can be one of the strings: {{unique}}, {{hash}}, {{merge}}, {{deep}}, or a hash with its {{strategy}} key set to one of those strings, and where further options are {{knock_out_prefix}}, {{sort_merged_arrays}}, {{unpack_arrays}}, and {{merge_hash_arrays}} - (See the {{lookup}} function for details).[~thomas.hallgren] Pleas Please review the updated description for correctness.
Add Comment
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Henrik Lindberg Component/s: DOCS 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Merged to master at: cfe8d3e 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Rob Nelson commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Documentation PR https://github.com/puppetlabs/puppet-docs/pull/565 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Steve Barlow Sprint: Language 2015-10-28 , Language 2015-11-11 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings One thing that isn't covered in this ticket is how to integrate the lookup of the lookup_options with the lookup explain capability. The current explanation will show how entries are merged but not the origin of the merge options. Perhaps we need some ways to control such output so that clutter can be avoided when it's not desired. Since it doesn't affect the lookup functionality I think it deserves a ticket of it's own. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren Yes, please file a separate ticket for 'lookup explain lookup_options'. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Rob Nelson commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren Awesome, that looks like quite a lot of changes but the resulting work for the user looks much better. Is the lookup_options key itself looked up using a deep merge, so you can define your parameter key wherever you want? I believe so from the diffs but best to verify. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Rob Nelson commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings I could put lookup_options: modulex::paramy in one yaml and lookup_options: modulea::paramb in another yaml. Sounds great to me! If my understanding is correct I can submit a new docs PR for review. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Rob Nelson that is what we decided - it will be a hash lookup (not deep) since we think it would be confusing if the options per key also got merged - that means that the overall options are merged, but it is "priority" between what is stated per key. Does that make sense? 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Rob Nelson Yes it merges those into one `lookup_options`. It does not merge what is under the modulex::parmay or modulea::paramb keys though. It means you can define the default data with merge behavior options in each module's "data in modules" data and they will compose nicely. You can then simply bind what will be merged into those values in the environment (or globally). If you need to override the behavior (and say, not merge, you can override the lookup_options: modulex::paramx). 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren assigned an issue to Henrik Lindberg Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Assignee: Thomas Hallgren Henrik Lindberg 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Added PUP-5437 for the explain functionality. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Henrik Lindberg Assignee: Henrik Lindberg Thomas Hallgren 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Henrik Lindberg, forget about my previous comment about module name prefix on the lookupoptions key. I did some refactoring that god rid of the need to do that. Regarding deep merging the lookupoptions. Is that really what we want? In my mind a hash merge is a better fit since it would allow keys to be added but not altered or "knocked out". Another thing that bugs me slightly is the naming convention. Why do we want lookupoptions and not lookup_options? IMO, the latter is more aligned with names of other options in the puppet/hiera world. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Just to be sure, hash merge for lookup_options would allow the entire key to be overridden at a higher precedence level - right? That is important since a designer of a module could specify that a particular key (in that module) should use say a deep merge and a user wants to override that in an environment and only use a given data value. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Yes, hash merge means that highest priority wins and since the merge is performed on the containing lookup_options hash, the key will essentially be overridden (the higher prio key is found first and then retained during merge). 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Agree that: lookup_options is better than lookupoptions (I keep reading that as "lookupop"-tions ). we want a hash merge (not a deep merge) Regarding namespacing lookup_options, It is actually more problematic to use the puppet:: namespace as there are several modules that use that name to manage puppet itself. And since they are meta, they may even end up managing the notion of "lookup_option" :-o.. So, even if far from ideal - the "topscope" is actually the least problematic. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings John Bollinger The intent is to deprecate the hiera_xxx functions sometime in the 4.x series. As the functionality for "data in modules"/"lookup" is brand new in puppet 4.3.0 we want it to be use a bit before we start banging on the big drum and doing the deprecations. If all goes well, the idea is to do that in Puppet 4.4.0. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title John Bollinger commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Is it ok if we leave the hiera_xxx functions as they are since they have the style that implies that the user knows the data configuration? Instead users should use the lookup function where the lookup options from data files becomes the default if not given as an argument to lookup. If the lookup() function honors the lookup options specified in the data, then I would be satisfied for hiera() to not do so. I agree that it does not make sense for the behavior of the hiera_xxx() functions to change in any case, but I do still recommend that those functions be deprecated. If lookup() behaves as suggested then the hiera() function should be deprecated, too. Overall, this could be less surprising than altering hiera() to sometimes perform hash-merge or array lookups. If deprecation is too strong to be palatable at this time, then at minimum start strongly promoting use of lookup() and the in-data lookup options as superior practice, which it is. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings All keys in a module are qualified with the module name. In fact, the module data provider is selected based on this key. A key that isn't prefixed with the module name will hence never reach a module data provider which means that the keys like lookupoptions or lookupoptions::* will never be found in a module. So in a module, the format must instead be: mysql::lookupoptions mysql::server::override_options: merge: deep 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
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren Hm (the need to use a module name in the lookupoptions key) - how do you see that working. I imagined we would simply do a lookup of "lookupoptions" with deep merge and get all of them. Does this mean we need to do a lookup per module? 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Henrik Lindberg, the way I see it, using the hiera_xxx functions is similar to explicitly specify the options with a parameter when using the lookup function. I.e. the user expresses a desire to override the default and should be able to do so. Therefore I'm in favor of keeping the hiera_xxx functions as they are. Another reason for this is that I view them as legacy functions that should be deprecated eventually. As such, it's better to just leave them as they are. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings I question the use of a global parameter like hiera_advanced_parameter_bindings or data_binding_lookupoptions to control the behavior. If the intent is to make the lookup behavior an aspect of the data itself, then there should be no global override. Performance wise it shouldn't matter much if the behavior is instead controlled by checking the existence of the lookupoptions::* key. It has already been parsed into a hash. One thing that could make a small difference performance wise would be if we, instead of using a lookupoptions::* key, would use a lookupoptions key with an associated object where the subkeys are specified. That would avoid unnecessary string concatenations in order to build keys. E.g. instead of this: lookupoptions::mysql::server::override_options: merge: deep we could have this: lookupoptions: mysql::server::override_options: merge: deep Now the backend only needs to check of the presence of lookupoptions once and then use it's presence to control its behavior for all lookups. The actual key used for a lookup can also be used inside of the lookupoptions object. No more string concatenation. To really do a deep(er) merge will of course consume some more CPU-cycles but having a global flag to control this will not help. If
Jira (PUP-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thomas Hallgren also brought up (in a conversation we had) that it is confusing if the lookup options are not also the default lookup options when performing a lookup using the lookup function, and I agreed to that. For the hiera_xxx functions it may become problematic, since they are themselves already specifying one aspect of the lookup (the type), and there is a global parameter in hiera.yaml controlling how hash lookup is expected to work. As an example, should a hiera (priority) lookup perform a merge if the lookup options in hiera data specifies this, or is the call to hiera (priority) the way the user specifies that it should not do a merge (no matter what the default is)? It was for these reasons I originally said that the lookup options should only have effect for automatic data binding. Opinions? Is it ok if we leave the hiera_xxx functions as they are since they have the style that implies that the user knows the data configuration? Instead users should use the lookup function where the lookup options from data files becomes the default if not given as an argument to lookup. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Also agree to that we do not really need a puppet setting. If the lookupoptions key is there - the feature is on. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Henrik Lindberg Fix Version/s: PUP 4.3.0 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Sounds like a good plan. I think this will even satisfy John Bollinger's request for consistent lookup behavior. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings That is nice. Needs to do a lookup of "lookupoptions" with a deep merge to avoid having to have central definition of all lookup options. But that is fine, far less expensive that looking up each lookupoption for each and every parameter. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings My knowledge on YAML is failing me. Does the merge allow the same key to appear multiple times in one hash declaration? I.e. code lookupoptions: mysql_server: ... ... lookupoptions: apache: ... code If this is an issue, then that would be a usability minus compared to the lookupoptions::* keys. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings There can only be one lookupoptions object per file which means that all overrides would be declared in one place (per file). I think there's both pros and cons to that approach. Not sure one outweighs the other. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings True. So yes, I guess we can go with this design instead. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Assignee: Thomas Hallgren 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Scope Change Category: Found Scope Change Reason: Deemed important for 4.3. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Thomas Hallgren Sprint: Language 2015- 11 10 - 11 28 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Rob Nelson commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings I like the idea of a lookupoptions key, that does seem more appealing than a global setting even if it's slightly more verbose. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Felix Frank Labels: hiera parameter redmine 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Felix Frank Component/s: Community 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Felix Frank assigned an issue to Rob Nelson Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Felix Frank Assignee: Andrew Parker Rob Nelson 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Michael Smith updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Michael Smith Story Points: 1 Sprint: Client 2015-11-11 Scrum Team: Language 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Josh Cooper commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Henrik Lindberg We reviewed this in PR triage and looked good. Rob Nelson discovered a pre-existing order dependent test failure, and I filed that as PUP-5401. I'm putting this in your teams sprint backlog. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Josh Cooper Sprint: Client Language 2015-11-11 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Henrik Lindberg commented on PUP-5395 Re: There's no way to set resolution_type when using data bindings Thanks Josh Cooper and Rob Nelson. I noted the ticket about the test order failure. Also commented on the PR. 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-5395) There's no way to set resolution_type when using data bindings
Title: Message Title Rob Nelson moved an issue Puppet / PUP-5395 There's no way to set resolution_type when using data bindings Change By: Rob Nelson Key: HI PUP - 118 5395 Project: Hiera Puppet 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.
