Jira (PUP-3268) Remove non-directory environment support
Title: Message Title Joshua Partlow commented on PUP-3268 Re: Remove non-directory environment support Fixed in aa68b8e Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2452) Refreshable feature on package type
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2452 Refreshable feature on package type Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3346) curl allows --insecure SSL connections
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3346 curl allows --insecure SSL connections Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3549) Debian init script status and stop actions are unsafe
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3549 Debian init script status and stop actions are unsafe Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3695) yum provider handling for --disableexcludes in :install_options
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3695 yum provider handling for --disableexcludes in :install_options Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title Kylo Ginsberg commented on PUP-3389 Re: Significant delay in puppet runs with growing numbers of directory environments Yeah +1 on backport to stable. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Josh Cooper commented on PUP-1270 Re: 'pkg' package provider does not understand IPS package versions properly Merged in 4526459 and acceptance fixes updated in 573cbacaf Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title Eric Sorenson commented on PUP-3389 Re: Significant delay in puppet runs with growing numbers of directory environments Yeah that looks awesome Joshua Partlow – I wish we hadn't just missed the PE3.7.1 cutoff or I would surely advocate for its inclusion there. Can any of the Watchers on this ticket who experienced this slowdown in their environment validate that the patch brings perf back into the realm of happiness for you? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3268) Remove non-directory environment support
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3268 Remove non-directory environment support Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title Joshua Partlow commented on PUP-3389 Re: Significant delay in puppet runs with growing numbers of directory environments Eric Sorenson I have a PR for this targeted to master. The speed up is huge for a test run of 1000 environment directories. I think we should backport this fix to stable as well. The fix itself will probably patch pretty cleanly; the spec changes will probably have conflicts since I recently adjusted those in the legacy environment merge, but it shouldn't be a big deal. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3268) Remove non-directory environment support
Title: Message Title Joshua Partlow commented on PUP-3268 Re: Remove non-directory environment support Windows spec failures... Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Ethan Brown commented on PUP-2789 Re: critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Clement XaT there appears to be an issue here when manipulating a group: Error: /Group[testgroup344]: Could not evaluate: Puppet::Util::Log requires a message However, I don't see any manifest code that shows the group declaration, so it's hard to diagnose this problem. If you have a manifest declaration that would be useful. I would also take a look at PUP-2628 which describes an issue that occurs when manipulating group membership on Windows. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1542) Puppet::Util::Log requires a message
Title: Message Title Ethan Brown commented on PUP-1542 Re: Puppet::Util::Log requires a message I have confirmed under other circumstances on Windows that the original fix for issue 17887 is incomplete. This particular message is unfortunate, because it masks the propagation of the real error information. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Ethan Brown Attachment: nodes.pp Attachment: site.pp Attachment: puppet.conf Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2789) critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc)
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2789 critical bug, windows agent : cant do some basic stuff (group creation, package installation, etc) Change By: Ethan Brown Attachment: output.txt Attachment: last_run_report.yaml Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3483) Systemd provider doesn't scan for changed units
Title: Message Title Ben S commented on PUP-3483 Re: Systemd provider doesn't scan for changed units I have a created a module myself that modifies systemd unit files and used execs. I can't see major benefits for Puppet doing the systemctl daemon-reload all the time with the package resource if it detects the service provider as systemd. Packages (should) do this as part of %post scripts Distributions rarely change the init scripts for packages, even after multiple version bumps When these init scripts do change, how often do they affect the service dependency tree? (requiring a daemon-reload) I think performing a systemctl daemon-reload should be left to modules. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3528) yumrepo needs sslverify value to be capitalized
Title: Message Title Ben S commented on PUP-3528 Re: yumrepo needs sslverify value to be capitalized I had a look into this, and there are actually are a number of yumrepo variables that require captilization for boolean values. Newer versions of yum don't seem to have a problem with the yum configuration using most forms of boolean, however this may not have always been the case, hence the acceptance of True/False only by yumrepo. I tried looking through the git logs for yum, but couldn't find anything definitive. However, my guess is that yum didn't always accept boolean forms other than True and False, since this is Python's boolean type. (See https://www.python.org/dev/peps/pep-0285/) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3742) Acceptance test Windows Gems
Title: Message Title Ethan Brown created an issue Puppet / PUP-3742 Acceptance test Windows Gems Issue Type: Task Affects Versions: PUP 3.7.3 Assignee: Unassigned Created: 2014/12/04 4:31 PM Priority: Normal Reporter: Ethan Brown Recently, we published Windows Puppet 3.7.3 gems that can't install by default with gem install. Facter 2.3.0 introduced a dependency on FFI 1.9.5+, but Puppet was pinned at 1.9.3. As a result, they conflicted. This could be avoided with some better acceptance tests on Windows that simply install the x86 and x64 gems and verify that they can do a basic run. In other words, we're looking for some automated smoke tests to ensure the packaging is correct. Add Comment
Jira (PUP-3742) Acceptance test Windows Gems
Title: Message Title Ethan Brown updated an issue Puppet / PUP-3742 Acceptance test Windows Gems Change By: Ethan Brown Labels: windows Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1043) Specifying file content by checksum should not use 'content' property
Title: Message Title Eric Sorenson commented on PUP-1043 Re: Specifying file content by checksum should not use 'content' property Ugh something just struck me about this, reading through PUP-1208 – the checksum property is already squatted upon by what we're calling checksum_type in this ticket. So we either need to break everyone currently specifying (non-functional BTW) alternative checksum types, or come up with a different name for the checksum value (like maybe checksum_value) and leave checksum as it is, meaning the type of checksum to use. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Charlie Sharpsteen commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used It will have to be 4.x, since this is a new feature. However, we still need to make a decision as to whether this is the right thing to do. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-686) --detailed-exit-codes not honored when --noop is used
Title: Message Title Rob Nelson commented on PUP-686 Re: --detailed-exit-codes not honored when --noop is used The redmine ticket suggests this be put in the 3.x branch. Is that still correct, or will this be deferred to 4.x? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3567) Remove current_environment check in Puppet::Indirector::Request#environment=
Title: Message Title Brian Cain assigned an issue to Brian Cain Puppet / PUP-3567 Remove current_environment check in Puppet::Indirector::Request#environment= Change By: Brian Cain Assignee: Brian Cain Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-296) hiera merging: remove values when :merge_behavior is set to deeper
Title: Message Title
Rob Nelson commented on HI-296
Re: hiera merging: remove values when :merge_behavior is set to deeper
Andreas,
Have you submitted a PR against hiera? Also, can you reference that PR instead of including the patch and clean up the other output if it's not included in the PR? The lack of proper formatting makes it difficult to read. You can wrap blocks in { noformat }
(without the spaces) before and after, that may help.
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
--
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-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Eric Thompson commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 thanks Roger Ignazio! https://tickets.puppetlabs.com/browse/QENG-1589 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Karl Mueller commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Cool, makes sense then Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-286) hiera array hierachy resolving
Title: Message Title Rob Nelson commented on HI-286 Re: hiera array hierachy resolving Klavs, can you provide some insight into why your use case is incompatible with the roles and profiles pattern and perhaps some additional custom facts? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2788) Puppet package source check fails with DFS share
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2788 Puppet package source check fails with DFS share Change By: Ethan Brown Fix Version/s: PUP 4.x Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3323) yum provider should be able to install from remote URLs
Title: Message Title Henrik Lindberg commented on PUP-3323 Re: yum provider should be able to install from remote URLs merged to master 445bd17 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3268) Remove non-directory environment support
Title: Message Title Henrik Lindberg commented on PUP-3268 Re: Remove non-directory environment support Merged to master 445bd17 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-2564) Specify UTF-8 as a default encoding for puppet
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2564 Specify UTF-8 as a default encoding for puppet Change By: Kylo Ginsberg Component/s: Server Component/s: Client Component/s: DOCS Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-237) Hiera behaviour with variables is inconsistent
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-237
Hiera behaviour with variables is inconsistent
Change By:
Rob Nelson
Suppose you have this hierarchy:{noformat}hiera.yaml:hierarchy: - "nodes/%{::clientcert}" - "datacenters/%{datacenter}" - commoncommon.yaml:classes: - datacenternodes/testnode.yaml:datacenter: mydatacenterdatacenters/mydatacenter.yaml:classes: - ntpntp::servers: - myntpserversite.pp that does hiera_include("classes")class "datacenter" do the following:$datacenter=hiera("datacenter")hiera_include("classes"){noformat}This gives inconsistent behavior:First pass, "\%{datacenter}" is not set, so nothing is done there. When "common" hierarchy is evaluated, Puppet processes "datacenter" class, get the value for "$datacenter" then do the hiera_include(). hiera_include() then get "datacenters/mydatacenter.yaml" classes, ie "ntp" but ntp settings are defaults, not those in file "datacenters/mydatacenter.yaml"That is to say : Puppet was able to get \%{datacenter} variable dynamically, was able to instantiate the class "ntp" dynamically, but does not evaluate the variables dynamically.I don't want to declare "datacenter" class for every node (Puppet principle : don't repeat yourself). I want to declare datacenter class as a common rule that exports a "\%{datacenter}" variable that allows me to include more hiera content dynamically, without having to push facts on the node that would require 2 passes of Puppet to achieve this.Actually my workaround is declaring in site.pp:$datacenter=hiera("datacenter", "")hiera_include("classes")so " \%{datacenter} " is set on first pass
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-237) Hiera behaviour with variables is inconsistent
Title: Message Title Rob Nelson commented on HI-237 Re: Hiera behaviour with variables is inconsistent Vincent, can you provide some example output of your first and second run and what provides the $datacenter value? If datacenter is a custom fact, that should be present on the first run and may indicate a problem outside of hiera itself. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Michael Smith commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back :native doesn't use the deep_merge gem, it does https://github.com/puppetlabs/hiera/blob/master/lib/hiera/backend.rb#L182 (the native Hash#merge) Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-237) Hiera behaviour with variables is inconsistent
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-237
Hiera behaviour with variables is inconsistent
Change By:
Rob Nelson
Suppose you have this hierarchy:{noformat}hiera.yaml:hierarchy: - "nodes/%{::clientcert}" - "datacenters/%{datacenter}" - commoncommon.yaml:classes: - datacenternodes/testnode.yaml:datacenter: mydatacenterdatacenters/mydatacenter.yaml:classes: - ntpntp::servers: - myntpserversite.pp that does hiera_include("classes")class "datacenter" do the following:$datacenter=hiera("datacenter")hiera_include("classes"){noformat}This gives inconsistent behavior:First pass, {{ "\ %{datacenter \ } }} " is not set, so nothing is done there. When "common" hierarchy is evaluated, Puppet processes "datacenter" class, get the value for "$datacenter" then do the hiera_include(). hiera_include() then get "datacenters/mydatacenter.yaml" classes, ie "ntp" but ntp settings are defaults, not those in file "datacenters/mydatacenter.yaml"That is to say : Puppet was able to get \ %{datacenter} variable dynamically, was able to instanciate instantiate the class "ntp" dynamically, but does not evaluate the variables dynamically.I don't want to declare "datacenter"class for every node (Puppet principle : don't repeat yourself). I want to declare datacenter class as a common rule that exports a " \ %{datacenter}" variable that allows me to include more hiera content dynamically, without having to push facts on the node that would require 2 passes of Puppet to achieve this.Actually my workaround is declaring in site.pp:$datacenter=hiera("datacenter","")hiera_include("classes")so "\ %{datacenter} " is set on first pass
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-237) Hiera behaviour with variables is inconsistent
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-237
Hiera behaviour with variables is inconsistent
Change By:
Rob Nelson
Suppose you have this hierarchy: {noformat}hiera.yaml :hierarchy: - "nodes/%{::clientcert}" - "datacenters/%{datacenter}" - commoncommon.yaml:classes: - datacenternodes/testnode.yaml:datacenter: mydatacenterdatacenters/mydatacenter.yaml:classes: - ntpntp::servers: - myntpserversite.pp that does hiera_include("classes")class "datacenter" do the following:$datacenter=hiera("datacenter")hiera_include("classes") {noformat} This gives inconsistent behavior:First pass, {{ %{datacenter \ } }} is not set, so nothing is done there. When "common" hierarchy is evaluated, Puppet processes "datacenter" class, get the value for "$datacenter" then do the hiera_include(). hiera_include() then get "datacenters/mydatacenter.yaml" classes, ie "ntp" but ntp settings are defaults, not those in file "datacenters/mydatacenter.yaml"That is to say : Puppet was able to get %{datacenter} variable dynamically, was able to instanciate the class "ntp" dynamically, but does not evaluate the variables dynamically.I don't want to declare "datacenter"class for every node (Puppet principle : don't repeat yourself). I want to declare datacenter class as a common rule that exports a "%{datacenter}" variable that allows me to include more hiera content dynamically, without having to push facts on the node that would require 2 passes of Puppet to achieve this.Actually my workaround is declaring in site.pp:$datacenter=hiera("datacenter","")hiera_include("classes")so %{datacenter} is set on first pass
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Karl Mueller commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back OK, I misread what you said. That sounds fine. I'm not sure how :native interacts with deep merge gem. (Is it loaded?) So I can't comment on that, since we don't use it. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3737) Can't Install Puppet Gem on Windows64 Bit Ruby 1.9.3 and 2.0
Title: Message Title Ethan Brown commented on PUP-3737 Re: Can't Install Puppet Gem on Windows64 Bit Ruby 1.9.3 and 2.0 I apologize. My instructions were incomplete. Facter 2.2.0 requires ~> 1.9.3, which means it will install the latest available ffi (the important thing is that it doesn't require at least 1.9.5. So the full workaround requires: Installing FFI 1.9.3 Installing Facter 2.2.0 Installing Puppet Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3389) Significant delay in puppet runs with growing numbers of directory environments
Title: Message Title Joshua Partlow assigned an issue to Joshua Partlow Puppet / PUP-3389 Significant delay in puppet runs with growing numbers of directory environments Change By: Joshua Partlow Assignee: Joshua Partlow Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3737) Can't Install Puppet Gem on Windows64 Bit Ruby 1.9.3 and 2.0
Title: Message Title Mark Dasco commented on PUP-3737 Re: Can't Install Puppet Gem on Windows64 Bit Ruby 1.9.3 and 2.0 I get the following trying to apply the workaround: D:\Wng.Infrastructure\vagrant>ruby -v ruby 2.0.0p247 (2013-06-27) [x64-mingw32] D:\Wng.Infrastructure\vagrant>gem install facter -v 2.2.0 Fetching: ffi-1.9.6-x64-mingw32.gem (100%) Successfully installed ffi-1.9.6-x64-mingw32 Fetching: win32-dir-0.4.9.gem (100%) Successfully installed win32-dir-0.4.9 Fetching: win32-security-0.2.5.gem (100%) Successfully installed win32-security-0.2.5 Fetching: facter-2.2.0-x64-mingw32.gem (100%) Successfully installed facter-2.2.0-x64-mingw32 Parsing documentation for ffi-1.9.6-x64-mingw32 Installing ri documentation for ffi-1.9.6-x64-mingw32 Parsing documentation for win32-dir-0.4.9 Installing ri documentation for win32-dir-0.4.9 Parsing documentation for win32-security-0.2.5 Installing ri documentation for win32-security-0.2.5 Parsing documentation for facter-2.2.0-x64-mingw32 Installing ri documentation for facter-2.2.0-x64-mingw32 Done installing documentation for ffi, win32-dir, win32-security, facter after 7 seconds 4 gems installed D:\Wng.Infrastructure\vagrant>gem install puppet ERROR: While executing gem ... (Gem::DependencyError) Unable to resolve dependencies: puppet requires ffi (= 1.9.3) Facter-2.2.0 holds a dependency to ffi-1.9.6 ?!?!? Looks like i'll just have to build from source. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3268) Remove non-directory environment support
Title: Message Title Joshua Partlow commented on PUP-3268 Re: Remove non-directory environment support FR: So, after this PR is in, there should be only one way to specify environments for Puppet, and that would be by creating directories in the environmentpath. The environmentpath is no longer a feature flag, and must be set to something. It has a default of "$confdir/environments" (so it doesn't have to be explicitly set in puppet.conf, but it can't be set to nothing /in/ puppet.conf). The manifestdir and templatedir settings have been removed. The manifest, modulepath and config_version settings can only be set in an environment.conf, or provided as commandline switches (not particularly relevant for config_version). Setting them in puppet.conf will raise an error. There were areas in the acceptance suite that showed failures when legacy environments were yanked. The two primary areas (ignoring tests that were explicitly testing the old static/dynamic envs or relying on setting manifest or modulepath directly) were module tests that were tripping over a bare configuration (no $confdir/environments/production directory environment) that was giving them a fallback production environment with no modulepath, and file_content/file_metadata calls during catalog application in an apply or agent run where a File resource was calling back to a content or source parameter pointing to a "puppet:///foo" reference. The later case was attempting to look up non-existent directory environments on the agent rather than using the 'remote' reference environment contained in the catalog. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
Jira (HI-231) Hiera's recursion breaks if a backend returns nil
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-231
Hiera's recursion breaks if a backend returns nil
Change By:
Rob Nelson
We have hiera using the result of a hiera call as a data source, like this: {noformat} :backends: - site - yaml:hierarchy: - %{hiera('site')} - defaults {noformat} The "site" backend can return either nil (no data found), or a string representing the "site code" (i.e LAB), so that we can then have a specific YAML file per site.This all works well, unless the "site" backend returns nil, in which case hiera gets itself stuck in a loop until it fails with a SystemStackError.A snippet of the Hiera output is below. For ease of reproduction, site_backend always returns nil. \ # hiera -d myvalueDEBUG: Tue Nov 26 10:39:37 + 2013: site_backend returning nil (key is myvalue)DEBUG: Tue Nov 26 10:39:37 + 2013: Hiera YAML backend startingDEBUG: Tue Nov 26 10:39:37 + 2013: Looking up myvalue in YAML backendDEBUG: Tue Nov 26 10:39:37 + 2013: site_backend returning nil (key is site)DEBUG: Tue Nov 26 10:39:37 + 2013: Looking up site in YAML backendDEBUG: Tue Nov 26 10:39:37 + 2013: site_backend returning nil (key is site)[... snip ...]DEBUG: Tue Nov 26 10:39:37 + 2013: site_backend returning nil (key is site)DEBUG: Tue Nov 26 10:39:37 + 2013: Looking up site in YAML backend/usr/lib/ruby/site_ruby/1.8/hiera/console_logger.rb:9:in `debug': stack level too deep (SystemStackError)from /usr/lib/ruby/site_ruby/1.8/hiera/fallback_logger.rb:39:in `debug'from /usr/lib/ruby/site_ruby/1.8/hiera.rb:35:in `debug'from /usr/lib/ruby/site_ruby/1.8/hiera/backend/site_backend.rb:5:in `lookup'from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:174:in `lookup'from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `each'from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `lookup'from /usr/lib/ruby/site_ruby/1.8/hiera/interpolate.rb:43:in `hiera_interpolate'from /usr/lib/ruby/site_ruby/1.8/hiera/interpolate.rb:13:in `send' ... 1751 levels...from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `each'from /usr/lib/ruby/site_ruby/1.8/hiera/backend.rb:171:in `lookup'from /usr/lib/ruby/site_ruby/1.8/hiera.rb:60:in `lookup'from /usr/bin/hiera:221
Add Comment
Jira (HI-121) Add hiera_resources similar to hiera_include
Title: Message Title Rob Nelson commented on HI-121 Re: Add hiera_resources similar to hiera_include That's pretty awesome, I'm tired of the hiera lookup + create_resource pattern myself so I'm game to give it a shot. Someday. Maybe Christmas "break"! Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Jeremy T. Bouse commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Okay... I ran this under a CentOS 6.5 Vagrant host and it does not clean-up the CSR and provided me with the following: [root@puppetmaster ~]# puppet cert list -a "puppetagent.puppetdebug.vlan" (SHA256) B2:86:B6:35:38:0B:87:68:52:FA:D9:1E:FD:79:2E:72:37:79:D9:23:85:95:55:26:95:59:34:F0:92:75:16:18 + "puppetmaster.puppetdebug.vlan" (SHA256) 5B:89:25:EA:60:22:EC:3F:66:EE:76:46:3B:55:03:2C:5B:24:7D:1E:9F:33:C4:51:FF:A7:2F:99:C6:7B:BB:5D (alt names: "DNS:puppet", "DNS:puppet.puppetdebug.vlan", "DNS:puppetmaster.puppetdebug.vlan") [root@puppetmaster ~]# puppet cert clean puppetagent.puppetdebug.vlan Error: Could not find a serial number for puppetagent.puppetdebug.vlan This was also using the Puppetlabs repo version 3.7.3 so I'm not sure off-hand why the same version code on different distributions would behave differently like this. Add Comment
Jira (PUP-1916) puppet cert clean cannot remove signing requests
Title: Message Title Jeremy T. Bouse commented on PUP-1916 Re: puppet cert clean cannot remove signing requests Okay... I ran this under a CentOS 6.5 Vagrant host and it does not clean-up the CSR and provided me with the following: [root@puppetmaster ~]# puppet cert list -a "puppetagent.puppetdebug.vlan" (SHA256) B2:86:B6:35:38:0B:87:68:52:FA:D9:1E:FD:79:2E:72:37:79:D9:23:85:95:55:26:95:59:34:F0:92:75:16:18 + "puppetmaster.puppetdebug.vlan" (SHA256) 5B:89:25:EA:60:22:EC:3F:66:EE:76:46:3B:55:03:2C:5B:24:7D:1E:9F:33:C4:51:FF:A7:2F:99:C6:7B:BB:5D (alt names: "DNS:puppet", "DNS:puppet.puppetdebug.vlan", "DNS:puppetmaster.puppetdebug.vlan") [root@puppetmaster ~]# puppet cert clean puppetagent.puppetdebug.vlan Error: Could not find a serial number for puppetagent.puppetdebug.vlan This was also using the Puppetlabs repo version 3.7.3 so I'm not sure off-hand why the same version code on different distributions would behave differently like this. Add Comment
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: {noformat} ---:backends: - json:hierarchy: - % \ {fqdn} \ - % \ {pop} \ - common:json: :datadir: - /etc/puppet/private/ \ - /etc/puppet/environments/% \ {environment}/hiera_data_store/ \ - /etc/puppet/environments/% \ {environment}/rebirth_data_store/ \ - /etc/puppet/environments/% \ {environment}/satellite_system_groups/ {noformat} At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-2563) Remove 1.8.7 support in the ruby code base
Title: Message Title Peter Huene commented on PUP-2563 Re: Remove 1.8.7 support in the ruby code base Fixed for the above merged into master with Josh's latest fix. We should now gracefully terminate (with error) when run under 1.8.7. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-225) allow interleaved querying of backends
Title: Message Title Rob Nelson commented on HI-225 Re: allow interleaved querying of backends Kjetil, do you have a link to the PR and was it accepted? I don't see any relevant config option in the documentation for hiera yet. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Kurt Wall commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 Kylo Ginsberg or Eric Thompson Can you address Roger Ignazio's question? I don't think it has, but I've been wrong before. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: {{ --- }} {{ :backends: - json }} {{ :hierarchy: - %\{fqdn \ } }} {{ \ \ - %\{pop} }} {{ \ \ - common }} {{ :json: }} {{\ :datadir: - /etc/puppet/private/ }} {{ \ \ - /etc/puppet/environments/%\{environment}/hiera_data_store/ }} {{ \ \ - /etc/puppet/environments/%\{environment}/rebirth_data_store/ }} {{ \ \ - /etc/puppet/environments/%\{environment}/satellite_system_groups/ }} At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:{{---}}{{:backends: - json}}{{:hierarchy: - %\{fqdn}}}{{\- %\{pop}}}{{\- common}}{{:json:}}{{ :datadir: - /etc/puppet/private/}}{{\- /etc/puppet/environments/%\{environment}/hiera_data_store/}}{{\- /etc/puppet/environments/%\{environment}/rebirth_data_store/}}{{\- /etc/puppet/environments/%\{environment}/satellite_system_groups/}}At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: {{ --- }} {{ :backends: - json }} {{ :hierarchy: - %\{fqdn} }} {{ \- %\{pop} }} {{ \- common }} {{ :json: }} {{ :datadir: - /etc/puppet/private/ }} {{ \- /etc/puppet/environments/%\{environment}/hiera_data_store/ }} {{ \- /etc/puppet/environments/%\{environment}/rebirth_data_store/ }} {{ \- /etc/puppet/environments/%\{environment}/satellite_system_groups/ }} At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:{{---}}{{:backends: - json}}{{:hierarchy: - %\{fqdn \ }}}{{\ \ - %\{pop}}}{{\ \ - common}}{{:json:}}{{ \ :datadir: - /etc/puppet/private/}}{{\ \ - /etc/puppet/environments/%\{environment}/hiera_data_store/}}{{\ \ - /etc/puppet/environments/%\{environment}/rebirth_data_store/}}{{\ \ - /etc/puppet/environments/%\{environment}/satellite_system_groups/}}At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:---:backends: - json:hierarchy: - % % \ {fqdn} }} - %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/- /etc/puppet/environments/%{environment}/satellite_system_groups/At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:---:backends: - json:hierarchy: - %\{fqdn} \ - % \ {pop} \ - common:json: :datadir: - /etc/puppet/private/ \ - /etc/puppet/environments/% % \ {environment}/hiera_data_store/ \ - /etc/puppet/environments/% \ {environment}/rebirth_data_store/ \ - /etc/puppet/environments/% \ {environment}/satellite_system_groups/At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Roger Ignazio commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 Saw this ticket was closed, has this new configuration been added to our Puppet Solaris acceptance job(s) in Jenkins? Or is there a separate ticket where I should do that? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: {quote} ---:backends: - json:hierarchy: - %{fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/% % {environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/- /etc/puppet/environments/%{environment}/satellite_system_groups/ {quote} At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:---:backends: - json:hierarchy: - % % {fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/- /etc/puppet/environments/%{environment}/satellite_system_groups/At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:{ { quote} ---:backends: - json }} :hierarchy: - %{fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/ {{ - /etc/puppet/environments/ \ %{environment}/satellite_system_groups/ {quote } } At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:{{--- }} :backends: - json }} :hierarchy: - %{fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/{{- /etc/puppet/environments/\%{environment}/satellite_system_groups/}}At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: {{this}} {{ --- }} :backends: - json {{ :hierarchy: - %{fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/ {{ - /etc/puppet/environments/%{environment}/satellite_system_groups/ }} At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-121) Add hiera_resources similar to hiera_include
Title: Message Title Justin Lambert commented on HI-121 Re: Add hiera_resources similar to hiera_include I started on a module, but got sidetracked and haven't ever gone back to it. It looks like the URL has been updated: http://blog.yo61.com/assigning-resources-to-nodes-with-hiera-in-puppet/. If you get the ambition to do it I'd still be interested in it. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this:{{---}}:backends: - json:hierarchy: - %{fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/{{- /etc/puppet/environments/ \ %{environment}/satellite_system_groups/}}At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: {{this}} ---:backends: - json{{:hierarchy: - %{fqdn}}}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/- /etc/puppet/environments/%{environment}/satellite_system_groups/At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: ``` ---:backends: - json {{ :hierarchy: - %{fqdn} }} - %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/- /etc/puppet/environments/%{environment}/satellite_system_groups/ ``` At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Kurt Wall commented on PUP-3057 Re: Ensure that acceptance tests run on Solaris 10 This passed acceptance. Running a local test for a sanity check, but resolving anyway. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-148) Support multiple backends of the same type
Title: Message Title
Rob Nelson updated an issue
Hiera / HI-148
Support multiple backends of the same type
Change By:
Rob Nelson
It would be great if Hiera could support multiple backends of the same type.Currently I make my own modifications to hiera and hiera-json to support multiple JSON data stores. My code is terrible, but available here:https://github.com/lukebigum/hierahttps://github.com/lukebigum/hiera-jsonAnd it works with a configuration file like this: ``` ---:backends: - json:hierarchy: - %{fqdn}- %{pop}- common:json: :datadir: - /etc/puppet/private/- /etc/puppet/environments/%{environment}/hiera_data_store/- /etc/puppet/environments/%{environment}/rebirth_data_store/- /etc/puppet/environments/%{environment}/satellite_system_groups/ ``` At the moment this allows me to separate out hiera keys into functional directories. For example some of the JSON data stores above are populated by scripts, others are edited by hand and some are outside an RCS system. The data stores are searched top to bottom, like the hierarchy.My future plan with this is to use use the hierarchy of data stores to be able to allow Developers some control over what hiera data is defined. Something like the following would give Devs the ability to write any JSON they want into their own data store while my modifications to hiera allow our Administrators to override any hiera keys (the search stops on the first key found). The config file would look like this::json: :datadir: - /etc/puppet/systems_data_store/- /etc/puppet/dev_data_store/
Add Comment
This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (HI-121) Add hiera_resources similar to hiera_include
Title: Message Title Rob Nelson commented on HI-121 Re: Add hiera_resources similar to hiera_include Justin, did you ever create a module based on this, as discussed in the Redmine ticket? Also, I can't get to your website, is it offline or a connectivity issue? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1072) support HTTP(S) URL as the file 'source'
Title: Message Title Peter Huene updated an issue Puppet / PUP-1072 support HTTP(S) URL as the file 'source' Change By: Peter Huene Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3605) Puppet doesn't remove users from groups
Title: Message Title Peter Huene updated an issue Puppet / PUP-3605 Puppet doesn't remove users from groups Change By: Peter Huene Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3605) Puppet doesn't remove users from groups
Title: Message Title Peter Huene updated an issue Puppet / PUP-3605 Puppet doesn't remove users from groups Change By: Peter Huene Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1270) 'pkg' package provider does not understand IPS package versions properly
Title: Message Title Peter Huene updated an issue Puppet / PUP-1270 'pkg' package provider does not understand IPS package versions properly Change By: Peter Huene Fix Version/s: PUP 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3469) fix zpool tests on solaris10
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-3469 fix zpool tests on solaris10 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3057 Ensure that acceptance tests run on Solaris 10 Change By: Kurt Wall QA Contact: Eric Thompson Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Eric Thompson updated an issue Puppet / PUP-3638 Remove the manifest handling code from the util/rdoc parsers. Change By: Eric Thompson QA Contact: Kurt Wall Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3057) Ensure that acceptance tests run on Solaris 10
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3057 Ensure that acceptance tests run on Solaris 10 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3469) fix zpool tests on solaris10
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3469 fix zpool tests on solaris10 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3702) zone provider should inherit /sbin on solaris10
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3702 zone provider should inherit /sbin on solaris10 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1916) puppet cert clean cannot remove signing requests
Title: Message Title Jeremy T. Bouse commented on PUP-1916 Re: puppet cert clean cannot remove signing requests This seems to work fine from what I can see with 3.7.3 I ran the following using Vagrant with master and agent hosts. root@puppetmaster:~# puppet -V 3.7.3 root@puppetmaster:~# puppet cert list -a root@puppetmaster:~# service puppetmaster start [ ok ] Starting puppet master. root@puppetmaster:~# puppet cert list -a + "puppetmaster.puppetdebug.vlan" (SHA256) 8E:B5:B5:8C:B2:BD:C9:79:39:2D:67:C9:D5:39:35:7B:58:44:62:54:15:87:1A:26:67:69:BE:78:F8:42:6A:62 (alt names: "DNS:puppet", "DNS:puppet.puppetdebug.vlan", "DNS:puppetmaster.puppetdebug.vlan") I then logged into my agent and ran root@puppet
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Michael Smith commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back I'm not sure what you mean; the change I'm implementing is No change when :deep_merge => :native When :deep_merge => :deep or :deep_merge => :deeper, change from giving a warning to giving an error and exiting if the deep_merge gem isn't installed Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Eric Thompson commented on PUP-3638 Re: Remove the manifest handling code from the util/rdoc parsers. custom type verified: [root@yf7p66isxcn95ea puppet]# ls /etc/puppet/modules/food/lib/puppet/type/ database.rb [root@yf7p66isxcn95ea puppet]# puppet doc --mode rdoc --modulepath /etc/puppet/modules/ --reference database [root@yf7p66isxcn95ea puppet]# grep -r database doc/ doc/food/__types__.html: doc/food/__types__.html: doc/food/__types__.html: database doc/food/__types__.html: lib/puppet/type/database.rb
Jira (PUP-1098) Package/source should accept puppet:// files
Title: Message Title Rob Nelson commented on PUP-1098 Re: Package/source should accept puppet:// files Redmine #4074 and #11865 seem to agree that this is needed but have a weird circular reference where each says to see the other. Charlie, I'm not sure who this should be assigned to, could you help determine who can make the decision on this? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1098) Package/source should accept puppet:// files
Title: Message Title Rob Nelson updated an issue Puppet / PUP-1098 Package/source should accept puppet:// files Change By: Rob Nelson Assignee: Charlie Sharpsteen Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Karl Mueller commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back IMO, it should be the former. :deep_merge => :native means you need need the deep_merge gem for a valid configuration. In that scenario, when require 'deep_merge' fails, then you have an error. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1095) option to ignore remote filebucket failures, or treat as non-blocking errors
Title: Message Title Jason Antman commented on PUP-1095 Re: option to ignore remote filebucket failures, or treat as non-blocking errors For the record, the DR plan explained above is pretty much braindead. As is configuring the filebucket that way. This is no longer an issue for me, and anyone else who's using the setup I described above is in desperate need of rethinking their puppet deployment plan. I vote for closing this. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3702) zone provider should inherit /sbin on solaris10
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-3702 zone provider should inherit /sbin on solaris10 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Henrik Lindberg commented on PUP-3638 Re: Remove the manifest handling code from the util/rdoc parsers. Eric Thompson Merged your fix to the documentation and examples. 540e91e Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-405) Remove ActiveRecord stored configs
Title: Message Title
Kurt Wall commented on PUP-405
Re: Remove ActiveRecord stored configs
Verified in master at SHA=NN. The thin_storeconfigs and async_storeconfigs settings are gone, storeconfigs_backend defaults to puppetdb, and storeconfigs is false:
$ xexec bundle exec puppet apply -e "\$n = [1, 2]; Notify <|\$n|> { require => File['/tmp/foo'] }" --thin_storeconfigs=true --async_storeconfigs=true
Error: Could not parse application options: invalid option: --thin_storeconfigs=true
$ xexec bundle exec puppet apply -e "\$n = [1, 2]; Notify <|\$n|> { require => File['/tmp/foo'] }" --async_storeconfigs=true
Error: Could not parse application options: invalid option: --async_storeconfigs=true
$ xexec bundle exec puppet config print storeconfigs_backend storeconfigs
storeconfigs_backend = puppetdb
storeconfigs = false
Jira (HI-274) :merge_behavior with deep_merge gem missing should error instead of falling back
Title: Message Title Michael Smith commented on HI-274 Re: :merge_behavior with deep_merge gem missing should error instead of falling back Just making it an error when you request the setting makes sense to me as well. Anyone else we should pull in for discussion? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3728) Cron type uses incorrect month when month name is provided
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-3728 Cron type uses incorrect month when month name is provided Change By: Kylo Ginsberg Fix Version/s: PUP 4.0.0 Fix Version/s: PUP 3.7.4 Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3665) future parser collector override with Resource reference does not work
Title: Message Title Kurt Wall updated an issue Puppet / PUP-3665 future parser collector override with Resource reference does not work Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3740) Update puppet package dependencies to require ruby 1.9.3 or greater
Title: Message Title Josh Cooper commented on PUP-3740 Re: Update puppet package dependencies to require ruby 1.9.3 or greater There's also puppet as a gem Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3741) Puppet certificate reovke issue on Puppetmaster.
Title: Message Title jennifer kim created an issue Puppet / PUP-3741 Puppet certificate reovke issue on Puppetmaster. Issue Type: Bug Affects Versions: PUP 3.2.4 Assignee: Andy Parker Components: Server Created: 2014/12/04 12:18 PM Environment: Puppet master : CentOS 6.4 Puppet agent : CentOS 6.4 Priority: Normal Reporter: jennifer kim Hello, I have a question about revoking certificate. It is okay when puppet agents generate certificate first time, but we have the below error message when regenerating puppet certificate after installing CentOS on agents or deleting /var/lib/puppet/ssl/* Error: Could not request certificate: The certificate retrieved from the master does not match the agent's private key. Certificate fingerprint: 40:71:07:E1:93:5E:3E:1E:C2:1B:AC:55:7D:EA:1D:0C:B5:A6:21:88:50:68:2E:DC:22:F2:61:54:75:FB:76:FE To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficat
Jira (PUP-1079) Exported resources is exporting to the database with --noop flag
Title: Message Title Rob Nelson commented on PUP-1079 Re: Exported resources is exporting to the database with --noop flag Verified with Jason that this is now a critical issue, --noop is now unusable. This appears to need some engineering decisions on how to go forward or to leave as is. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3740) Update puppet package dependencies to require ruby 1.9.3 or greater
Title: Message Title Michael Stahnke commented on PUP-3740 Re: Update puppet package dependencies to require ruby 1.9.3 or greater This should be covered by the All in One agent work. /cc Matthaus Owens Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-1076) please make config_version available as a variable
Title: Message Title Jason Antman commented on PUP-1076 Re: please make config_version available as a variable For me this is more of a "nice to have" rather than a must-have. First off, what I probably want is this available as a fact, not a variable. But I can do that easy enough myself - my original idea was to use this variable to write it out as a fact in /etc/facts.d. Use case - we set our config_version to be the environment name (usually a git branch, or "production" for master) and the git commit hash, i.e. 'production/16a426640214e7ba8ac47d4d21ea1dcdba085357'. We leverage this heavily in our Jenkins-based automated testing, ensuring that a given branch has run successfully on a set of nodes (by pulling reports from PuppetDB). It would be really useful if this were easier to retrieve, i.e. just as a fact. Moreover, it would be a lot simpler to `facter -p config_version` to determine the last config version that was run on a machine, as opposed to how we do it now (using PuppetBoard to find the node, then the latest report, then the config_version for that report). Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3740) Update puppet package dependencies to require ruby 1.9.3 or greater
Title: Message Title Josh Cooper created an issue Puppet / PUP-3740 Update puppet package dependencies to require ruby 1.9.3 or greater Issue Type: Bug Assignee: Release Engineering Components: RE Created: 2014/12/04 12:02 PM Priority: Normal Reporter: Josh Cooper Update rpm, deb, gem packages to require ruby 1.9.3 as puppet will no longer run on pre-1.9.3. Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e)
Jira (PUP-1076) please make config_version available as a variable
Title: Message Title Rob Nelson commented on PUP-1076 Re: please make config_version available as a variable This is a 4 year old ticket (from Redmine). Jason is going to add his use case. John, can you detail your use case as well? Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Eric Thompson commented on PUP-3638 Re: Remove the manifest handling code from the util/rdoc parsers. more verification, same bat-SHA, same bat-Linux: [root@yf7p66isxcn95ea facter]# puppet doc --mode rdoc --modulepath /etc/puppet/modules/ [root@yf7p66isxcn95ea facter]# ls custom1.rb doc [root@yf7p66isxcn95ea facter]# ls doc/ created.rid doc food.html images index.html js rdoc.css table_of_contents.html [root@yf7p66isxcn95ea facter]# cat doc/food.html
Jira (PUP-3638) Remove the manifest handling code from the util/rdoc parsers.
Title: Message Title Eric Thompson commented on PUP-3638 Re: Remove the manifest handling code from the util/rdoc parsers. Henrik Lindberg no ticket, just maint/master PR: https://github.com/puppetlabs/puppet/pull/3381 let me know if you think it needs a ticket Add Comment This message was sent by Atlassian JIRA (v6.3.7#6337-sha1:2ed701e) -- 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.
