Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Henrik Lindberg Fix Version/s: HI 3.0.0 Fix Version/s: HI 3.0.1 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Henrik Lindberg Affects Version/s: HI 2.0.0 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Thompson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Thompson QA Status: Reviewed 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Thompson commented on HI-374
Re: Update hiera defaults to reflect current best practices
validated on ubuntu14.04 at agent SHA:
[root@jhm22h1e2ehvpxc ~]# cat /etc/puppetlabs/code/hiera.yaml
---
:backends:
- yaml
:hierarchy:
- "nodes/%{::trusted.certname}"
- common
:yaml:
# datadir is empty here, so hiera uses its defaults:
foo: bar
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Thompson Assignee: QA Eric Thompson 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Kurt Wall updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Kurt Wall QA Status: Reviewed 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Kurt Wall updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Kurt Wall QA Status: Reviewed 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Kylo Ginsberg assigned an issue to QA Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: QA 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Nicholas Fagerlund commented on HI-374 Re: Update hiera defaults to reflect current best practices Hiera 3 requires Puppet 4+, roger that. 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices Note that this means Hiera 3.0.0 will not work with puppet 3.x with its default configuration which does not include trusted facts (they are opt in in 3.x). 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices Merged to master at: a1ebbb2 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices All hail to Nicholas Fagerlund... will fix up the PR to reflect his wisdom. Thanks Gary Larizza. 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Gary Larizza commented on HI-374 Re: Update hiera defaults to reflect current best practices That's absolutely a good idea. I don't have any reason why it wouldn't be wise/recommended, and totally defer to the sage wisdom of Nicholas Fagerlund! 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices I am prepared to take the PR and fix it up. There is however one loose end to tie up. Should we use what Nick is suggesting - the secure variant instead of ::clientcert or not ? Eric pinged Nick Walker and Gary Larizza. (Now pinging again). 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices Nick Walker Try searching for "structured facts hiera", which works the same way, only starting from $facts instead of $trusted. 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Thompson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Thompson QA Risk Severity: Low QA Risk Probability: Medium QA Risk Severity Reason: just defaults. less friction for users QA Risk Assessment: Medium QA Risk Assessment Reason: qa validate for another check, no way to automate? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Nick Walker commented on HI-374 Re: Update hiera defaults to reflect current best practices Seems reasonable to me since this will only affect new users. I had a thought that for users upgrading their certs would have been generated before trusted facts existed and that might cause an issue but that should be a non-issue since this is for new users only (existing users keep their existing hiera.yaml). I don't know much about trusted facts but assuming it "just works" then I'm for it. I googled "trusted facts hiera" and couldn't find anything on the subject. 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Sorenson commented on HI-374 Re: Update hiera defaults to reflect current best practices Ahh good catch Nicholas Fagerlund – Nick Walker Gary Larizza what do you think about that ^^^ 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Nicholas Fagerlund commented on HI-374
Re: Update hiera defaults to reflect current best practices
Ping. Since Hiera 2 only ships with Puppet versions that have $trusted enabled by default, let's stop using the insecure $clientcert variable. The hierarchy should include
certname/%{::trusted.certname}
instead.
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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg commented on HI-374 Re: Update hiera defaults to reflect current best practices Mark Butcher Can you update the PR to reflect the changes as per the description? 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{certname/%\{certname \} }}} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%\{environment\}/hieradata}}This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc0
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{certname/%\{certname\} _ } }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%\{environment\}/hieradata}}This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:db
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{certname/%\{certname\} _ }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%\{environment\}/hieradata }}This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Henrik Lindberg
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{ certname/%\{certname\} }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%\{environment\}/hieradata }}This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc0
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Henrik Lindberg Assignee: Henrik Lindberg 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 (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Rob Reynolds updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Rob Reynolds
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{ certname/%\{certname\} }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%\{environment\}/hieradata }}This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Rob Reynolds updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Rob Reynolds
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{certname/%\{certname\} }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%\{environment\}/hieradata }}This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just { { certname/% \ {certname \ } }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{ /code/environments/% \ {environment \ }/hieradata }} This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#63
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just { { certname/%{certname} }} and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{ /code/environments/%{environment}/hieradata }} This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc0
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (just {{certname/%{certname} }} ' and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root, then {{/code/environments/%{environment}/hieradata}} This (somewhat unfortunately from a timing standpoint, but without any real downside) triggers another semver major and therefore will be released as Hiera 3.0.0.---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title
Eric Sorenson updated an issue
Hiera / HI-374
Update hiera defaults to reflect current best practices
Change By:
Eric Sorenson
*Updated to reflect action plan*The config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation.There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices ( no 'global', just a {{certname/%{certname} }} ' node' and {{common}} levels.2. update the helper methods in [Hiera::Util|https://github.com/puppetlabs/hiera/blob/master/lib/hiera/util.rb#L30-L36] to reflect the AIO pathing changes that point to the OS-specific root , ' then {{/code/environments/%{ environment ' }/hieradata}} This (somewhat unfortunately from a timing standpoint , but without any real downside) triggers another semver major and 'common' therefore will be released as Hiera 3.0.0. ---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet.
Add Comment
This message was se
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Sorenson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Sorenson *Updated to reflect action plan*The hiera.yaml config that hiera ships with is pretty out-of-date and hasn't been updated to reflect the way most hiera deployments work. We should update this to eliminate setup friction so that it works immediately after installation. There are two parts to the change:1. update the default hierarchy in hiera.yaml to incorporate current best practices (no 'global', just a 'node', 'environment', and 'common' ---*Original description*Presently, hiera is not configured to work out of the box with puppet for several reasons: - hiera should be maintained as a standalone project- hiera requires a config file to be in place to start- we include the config file from the hiera project in the puppet packageLeading to the following unfortunate results: - the config file used by hiera after the puppet package is installed is not useful for configuring puppet, requiring upfront effort from users (pe or foss). This also becomes a CS burden.- persistence of hiera.yaml customization is complicated by overwrites of hiera.yaml on package installationA potential two part solution would solve the problems above: - [~josh] proposed a modification to hiera to allow it to run without a config file.- we could package a usable hiera.yaml.example file that could serve as a real world example for hiera-only users and a springboard for users of hiera with puppet. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (HI-374) Update hiera defaults to reflect current best practices
Title: Message Title Eric Sorenson updated an issue Hiera / HI-374 Update hiera defaults to reflect current best practices Change By: Eric Sorenson Summary: Update hiera .yaml defaults to reflect current best practices and defaults 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.
