Jira (HI-496) Hiera subkeys lookup should be configurable

2016-03-19 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru commented on  HI-496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 
 
HI-504 solves this issue 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (HI-496) Hiera subkeys lookup should be configurable

2016-02-20 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru commented on  HI-496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 
 
Henrik Lindberg Using a custom backend helps disabling subkey lookup.  Got one question though - 

HI-471
 doesn't seem to be integrated in the latest Puppet4 puppet-agent package (1.3.5). 
 
 
 
 
 
 
require "hiera/backend/yaml_backend" 
 
 
 
 
class Hiera 
 
 
 
 
  module Backend 
 
 
 
 
class Yaml_nosubkeys_backend < Yaml_backend 
 
 
 
 
  # When hiera backends define lookup_with_segments method 
 
 
 
 
  # subkey lookup is delegated to it. 
 
 
 
 
  # See HI-471 - https://github.com/puppetlabs/hiera/commit/5b4b8f 
 
 
 
 
  # We use this to disable subkey lookup (and thus allow dot separated keys in yaml files) 
 
 
 
 
  def lookup_with_segments(segments, scope, order_override, resolution_type, context) 
 
 
   

Jira (HI-496) Hiera subkeys lookup should be configurable

2016-01-28 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru commented on  HI-496 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
  Re: Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 
 
Please link this jira to the original request to see how the bacjend would look like. 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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 https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (HI-496) Hiera subkeys lookup should be configurable

2016-01-28 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Hiera /  HI-496 
 
 
 
  Hiera subkeys lookup should be configurable  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Affects Versions:
 

 HI 3.0.6 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/01/28 7:19 AM 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrian Muraru 
 
 
 
 
 
 
 
 
 
 
Hiera 3 introduced support for subkeys lookup: 
 
 
 
 
 
 
Qualified keys are composed of a top-level lookup key along with any number of additional subkeys, separated by dots.
 
 
 
 
 
 
 
While this is a cool feature it is breaking existing hiera configuration where . was used in the yaml key, e.g. 
 
 
 
 
 
 
my.key.with.dot: "text"
 
  

Jira (PUP-3863) hiera('some::key', undef) returns empty string

2015-04-16 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru commented on  PUP-3863 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: hiera('some::key', undef) returns empty string  
 
 
 
 
 
 
 
 
 
 
This is still listed in 3.7.5 Changelog: https://docs.puppetlabs.com/puppet/latest/reference/release_notes.html#future-parser-fixes-and-updates make it confusing for users 
 
 
 
 
 
 
 
 
 
 
 
 

 
 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-3908) Tidy type is too verbose when working of directories containing lot of files

2015-01-24 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru commented on  PUP-3908 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Tidy type is too verbose when working of directories containing lot of files  
 
 
 
 
 
 
 
 
 
 
https://github.com/puppetlabs/puppet/pull/3518 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.10#6340-sha1:7ea293a) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
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-3908) Tidy type is too verbose when working of directories containing lot of files

2015-01-24 Thread Adrian Muraru (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Adrian Muraru created an issue 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 Puppet /  PUP-3908 
 
 
 
  Tidy type is too verbose when working of directories containing lot of files  
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Improvement 
 
 
 

Affects Versions:
 

 PUP 3.7.3 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Components:
 

 Trivial 
 
 
 

Created:
 

 2015/01/24 1:16 AM 
 
 
 

Fix Versions:
 

 PUP 3.7.4 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Adrian Muraru 
 
 
 
 
 
 
 
 
 
 
We get a lot of notice messages for all files parsed by tidy type. 
 
 
 
 
 
 
== default: Notice: /Stage[main]/Module::Config/Tidy[/path/to/files]: Tidying File[/path/to/files/file1]