Jira (PUP-6982) Allow keys to be specified by pattern in lookup_options

[Thomas Hallgren (JIRA)]

Title: Message Title

Thomas Hallgren commented on PUP-6982   Re: Allow keys to be specified by pattern in lookup_options Here is a test that patterns must start with module name. The fact that a lookup_option trumps merge behavior is not part of this ticket, but here is a test for that. The fact that a lookup_option always wins (not part of this ticket either) is covered in this test. Here are the main reasons for choosing the '^' character over '/ /'. 1. The patterns live in the same namespace as other keys. It's not unlikely that users have keys that are paths. A Path may start and end with '/' 2. The '^' character anchors the pattern at the start, and it must be anchored. If it isn't, we cannot verify that it starts with a module name. 3. '/ /' is normally used instead of quotes. We cannot do that here since the parser will be JSON, YAML (or Hocon or something else). So the string must be quoted anyway. #2 above also answers the question regarding "line start-with". The '^' is indeed part of the regexp. It's not just a marker for a pattern. Add Comment   This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.