Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Change By: Maggie Dreyer Labels: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.221398.1510332362000.112979.1569368820212%40Atlassian.JIRA.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Change By: Maggie Dreyer Component/s: Language Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.221398.1510332362000.112977.1569368761097%40Atlassian.JIRA.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Change By: Henrik Lindberg If a class has many parameters and you want to make all hash parameters have hash or deep merge and all array parameters to have unique merge while all non collection values have firt first found strategy then it is not possible to define all of that with one pattern for the class itself. Instead you would need to individually list all keys, or be very clever with the use of suffixes on the parameter names (for example plural 's', or 'list' for arrays, and 'map' or 'hash' on hashes) and the pattern match on those.It would be great to be able to specify some kind of combined pattern 'first+unique+hash/deep'. and that they apply to the respective data type being found.This only applies for a pattern based lookup_options since everywhere else the lookup is for a single key - although there is no harm in having this as a "i don't know what the type is" but please merge/unique hashes and arrays... Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Change By: Henrik Lindberg Issue Type: Bug New Feature Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns See PUP-8144 for the original request (for clarity in documentation). Change By: Henrik Lindberg Team: Platform Core Add Comment This message was sent by Atlassian JIRA (v7.0.2#70111-sha1:88534db) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-8146) consider combined merge strategies for lookup_option with patterns
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-8146 consider combined merge strategies for lookup_option with patterns Issue Type: Bug Assignee: Unassigned Created: 2017/11/10 8:46 AM Priority: Normal Reporter: Henrik Lindberg If a class has many parameters and you want to make all hash parameters have hash or deep merge and all array parameters to have unique merge while all non collection values have firt found strategy then it is not possible to define all of that with one pattern for the class itself. Instead you would need to individually list all keys, or be very clever with the use of suffixes on the parameter names (for example plural 's', or 'list' for arrays, and 'map' or 'hash' on hashes) and the pattern match on those. It would be great to be able to specify some kind of combined pattern 'first+unique+hash/deep'. and that they apply to the respective data type being found. This only applies for a pattern based lookup_options since everywhere else the lookup is for a single key - although there is no harm in having this as a "i don't know what the type is" but please merge/unique hashes and arrays... Add Comment
