Jira (HI-420) Deep merging not working with Hiera 3.0.1
Title: Message Title Sivakalyan Chintakana commented on HI-420 Re: Deep merging not working with Hiera 3.0.1 Henrik Lindberg Not sure if it's a regression. This is the first time I'm trying to do this. My hiera.yaml is at /etc/puppetlabs/code/hiera.yaml. I know it works since my hierarchy as defined is working. Thanks, Siva 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 (HI-420) Deep merging not working with Hiera 3.0.1
Title: Message Title Sivakalyan Chintakana commented on HI-420 Re: Deep merging not working with Hiera 3.0.1 I'm using a forge module that uses create_resources to create the hiera lookups. There aren't any other specific hiera_hash calls. So, deep merging doesn't apply to create_resources? 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 (HI-420) Deep merging not working with Hiera 3.0
Title: Message Title Sivakalyan Chintakana created an issue Hiera / HI-420 Deep merging not working with Hiera 3.0 Issue Type: Bug Affects Versions: HI 3.0.1 Assignee: Unassigned Created: 2015/07/13 10:44 PM Environment: CentOS 7 64 bit Puppet server 2.1.1 Puppet 4.2 Puppet agent 1.2.1 Hiera 3.0.1 Priority: Major Reporter: Sivakalyan Chintakana Hi, 1. I've enabled deep merging in hiera.yaml. --- :backends:
Jira (HI-420) Deep merging not working with Hiera 3.0.1
Title: Message Title Sivakalyan Chintakana updated an issue Hiera / HI-420 Deep merging not working with Hiera 3.0.1 Change By: Sivakalyan Chintakana Summary: DeepmergingnotworkingwithHiera3.0 .1 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 (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Henrik Lindberg Please close the ticket. Using puppet apply to test worked.
$ cat hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{::fqdn}
- environment/%{::environment}
- global
:yaml:
# datadir is empty here, so hiera uses its defaults:
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Looks like :: is required while setting the variables on the command line.
$ hiera -d message environment=production
DEBUG: 2015-06-02 01:10:56 +: Hiera YAML backend starting
DEBUG: 2015-06-02 01:10:56 +: Looking up message in YAML backend
DEBUG: 2015-06-02 01:10:56 +: Looking for data source global
nil
$ hiera -d message ::environment=production
DEBUG: 2015-06-02 01:11:11 +: Hiera YAML backend starting
DEBUG: 2015-06-02 01:11:11 +: Looking up message in YAML backend
DEBUG: 2015-06-02 01:11:11 +: Looking for data source environment/production
Jira (PUP-4667) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana created an issue
Puppet / PUP-4667
datadir in hiera.yaml not interpolating %{::environment}
Issue Type:
Bug
Affects Versions:
PUP 4.1.0
Assignee:
Unassigned
Components:
Puppet Server
Created:
2015/05/28 2:05 PM
Environment:
CentOS 7 Openstack VM R10k 1.3.2
Fix Versions:
PUP 4.1.0
Priority:
Critical
Reporter:
Sivakalyan Chintakana
Hi,
Using the environment variable or r10k_environment fact in the datadir field in hiera.yaml doesn't work.
$ cat /etc/puppetlabs/code/hiera.yaml — :backends:
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Removed the :: in front of environment variable and restarted puppet server. Same issue persists.
$ cat /etc/puppetlabs/code/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{::fqdn}
- environment/%{::environment}
- global
:yaml:
:datadir: /etc/puppetlabs/code/hieradata/%{environment}
Jira (HI-376) datadir in hiera.yaml not interpolating %{::environment}
Title: Message Title
Sivakalyan Chintakana commented on HI-376
Re: datadir in hiera.yaml not interpolating %{::environment}
Henrik Lindberg I haven't used it in a manifest yet. However, I use it in the hierarchy and works fine when I have the full path in the :datadir.
$ cat /etc/puppetlabs/code/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- nodes/%{::fqdn}
- environment/%{::environment}
- global
:yaml:
