Jira (HI-46) Hiera should support alternate environments
Title: Message Title Eric Sorenson updated an issue Hiera / HI-46 Hiera should support alternate environments Change By: Eric Sorenson Currently hiera supports one `hiera.yaml` file hardcoded to be in the same location as `puppet.conf` (which is the `config` puppet directive.Having separate `hiera.yaml`'s per puppet environment would go along with having separate `site.pp`'s, modules, etc. per environment.UPDATE--- This feature is released in Puppet 4.4 / PE 2016.1 - See the full documentation here: https://docs.puppet.com/puppet/latest/reference/lookup_quick.html[~ripienaar] has a blog series about it too: https://www.devco.net/archives/2016/03/13/the-puppet-4-lookup-function.php Please see PUP-4474 for the work on "data in modules" which also covers "data in environments". TL;DR - yes it will be possible to have hiera data per environment, as well as hiera data in a module, and all of that in combination with the existing global hiera.Use this ticket to comment on use-cases if you like, as the PUP-4474 and related tickets are about the implementation and thus are far more detailed/technical. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-4660) Stop checking Puppet.features.external_facts?
Title: Message Title Josh Cooper commented on PUP-4660 Re: Stop checking Puppet.features.external_facts? For better or worse, puppet's .gemspec is only used when running puppet from source, and that's where we bumped the facter dependency. The packaging repo uses the dependencies in ext/project_data.yaml to build puppet as a gem, and there we already had a dependency on facter > 2. For example, puppet 4.5.2 gem shows the correct facter dependency: https://rubygems.org/gems/puppet/versions/4.5.2. So I think we're ok to make this change in puppet 4.y. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1406) mountpoints size and used values can be corrupt on 32-bit linux or bsd
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-1406 mountpoints size and used values can be corrupt on 32-bit linux or bsd Change By: Kylo Ginsberg Summary: Big mountpoints size and used values become negativ can be corrupt on 32-bit linux or bsd Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4660) Stop checking Puppet.features.external_facts?
Title: Message Title Kylo Ginsberg commented on PUP-4660 Re: Stop checking Puppet.features.external_facts? One question here is whether bumping the facter minimum up a major (i.e. from 1.7 to 2.0) requires a puppet major. If so, this should have a fixVersion of puppet 5. Thoughts Josh Cooper? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23
Title: Message Title
Kylo Ginsberg updated an issue
Puppet / PUP-5649
"syncversion" maybe obsolete for selmodule type in Fedora >= 23
Change By:
Kylo Ginsberg
Under CentOS 7, semodule -l (which the selmodule provider uses to check the loaded module version) returns a version number, e.g. (from CentOS 7): {code} root@srv-cfgmgt ~ # semodule -labrt 1.4.1 accountsd 1.1.0 acct 1.6.0 afs 1.9.0 aiccu 1.1.0 aide 1.7.1 ajaxterm 1.0.0 alsa 1.12.2 {code} Under Fedora 23, the output looks like this (e.g. no version specified): {code} # semodule -l | head -10abrtaccountsdacctafsaiccuaideajaxtermalsaamandaamtu {code} This causes "syncversion" to *always* report true when set, and always result in an active resource.My policycoreutils level on F23 is policycoreutils-2.4-18.fc23.x86_64
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5649 "syncversion" maybe obsolete for selmodule type in Fedora >= 23 Change By: Kylo Ginsberg Sprint: Client Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-5649 "syncversion" maybe obsolete for selmodule type in Fedora >= 23 Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6397) File autorequire in Mount causes dependency loops
Title: Message Title Kylo Ginsberg commented on PUP-6397 Re: File autorequire in Mount causes dependency loops I haven't had a chance to look at this one, but ping Matt Schuchard for possible insight (since you worked on the linked PUP-6099 ). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-2362 ssh_authorized_keys temporary file Operation not permitted Change By: Kylo Ginsberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2362) ssh_authorized_keys temporary file Operation not permitted
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-2362 ssh_authorized_keys temporary file Operation not permitted Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6461) pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases)
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6461 pip package provider with "ensure => latest" displays version change when there is none (problem parsing the output string in some cases) Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6266) Systemd provider with ubuntu 16.04
Title: Message Title Kylo Ginsberg assigned an issue to Unassigned Puppet / PUP-6266 Systemd provider with ubuntu 16.04 Change By: Kylo Ginsberg Assignee: Kylo Ginsberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti commented on PUP-6473 Re: FFI 1.9.11 has a bug when running on Windows Additional PR raised for modsync https://github.com/puppetlabs/modulesync_configs/pull/73 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4809) Yumrepo type says uppercase values are allowed when they are not
Title: Message Title William Hopper assigned an issue to Unassigned Puppet / PUP-4809 Yumrepo type says uppercase values are allowed when they are not Change By: William Hopper Assignee: William Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Henrik Lindberg updated an issue
Hiera / HI-522
deeper merge not being respected
Change By:
Henrik Lindberg
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as: {code} :hierarchy: - "%{::fqdn}" - common:merge_behavior: deeper:deep_merge_options: :knockout_prefix: '--' {code} I have also installed the gem using: {code} puppetserver gem install deep_merge {code} In common.yaml I have something like: {code} foo: - bar: "hello" - baz: "world" {code} and then in my node's yaml file I have {code} foo: - "hello" {code} When performing a run w/ {{ hiera("foo", {}) }} I'm only getting a single item when I would expect two
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Kyle Decot updated an issue
Hiera / HI-522
deeper merge not being respected
Change By:
Kyle Decot
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as::hierarchy: - "%{::fqdn}" - common:merge_behavior: deeper:deep_merge_options: :knockout_prefix: '--'I have also installed the gem using:puppetserver gem install deep_mergeIn common.yaml I have something like:foo: - bar: "hello" - baz: "world"and then in my node's yaml file I havefoo: - "hello"When performing a run w/ hiera("foo", {}) I'm only getting a single item when I would expect two
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5649 "syncversion" maybe obsolete for selmodule type in Fedora >= 23 Change By: Henrik Lindberg Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title Henrik Lindberg updated an issue Hiera / HI-522 deeper merge not being respected Change By: Henrik Lindberg Scrum Team: Language Component/s: Community Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title Henrik Lindberg commented on HI-522 Re: deeper merge not being respected IIRC, you have to use hiera_hash to get hash lookup and merges. The key that you are looking up needs to be a hash everywhere; you have a key that is bound to a string value, and then expect that to be merged with a hash? Can you start by trying to use hiera_hash instead of hiera and report back? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title Henrik Lindberg assigned an issue to Kyle Decot Hiera / HI-522 deeper merge not being respected Change By: Henrik Lindberg Assignee: Kyle Decot Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5831) Add a Binary type and runtime object
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5831 Add a Binary type and runtime object Change By: Henrik Lindberg Sprint: Language 2016-06-15 Triage , Language 2016- 07 06 - 27 15 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6454) cannot call functions with blocks in epp <%= ?
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6454 cannot call functions with blocks in epp <%= ? Change By: Henrik Lindberg Sprint: Language 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6312) Load XPP instead of .pp if present and feature flag is on
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6312 Load XPP instead of .pp if present and feature flag is on Change By: Henrik Lindberg Sprint: Language 2016-07-27 Triage Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6291) Add 'abs' support to Numeric.new
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6291 Add 'abs' support to Numeric.new Change By: Henrik Lindberg Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6233) Serivce SMF restart should use -s
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6233 Serivce SMF restart should use -s Change By: Eric Thompson Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6304) Add string formatting rules to String.new
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6304 Add string formatting rules to String.new Change By: Henrik Lindberg Sprint: Language Triage 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6233) Serivce SMF restart should use -s
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6233 Serivce SMF restart should use -s Change By: Eric Thompson Release Notes Summary: solaris 11.2+ SMF service restarts were returning prior to the service restarting. They will now be synchronous. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6347) new function (String): programmatic representation escapes for Ruby language and not Puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6347 new function (String): programmatic representation escapes for Ruby language and not Puppet Change By: Henrik Lindberg Sprint: Language Triage 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6314) Numeric.new (and subtypes) does not accept whitespace between sign and leading digit
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6314 Numeric.new (and subtypes) does not accept whitespace between sign and leading digit Change By: Henrik Lindberg Sprint: Language Triage 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6346) new function (String): not all string-based conversions respect width and precision
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6346 new function (String): not all string-based conversions respect width and precision Change By: Henrik Lindberg Sprint: Language Triage 2016-07-27 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Acceptance Criteria: That the serialization support for Pcore contains:* ability to serialize rich data types (beyond the constraints imposed by a particular serialization technology).* implementation objects should be free of serialization technology concerns; they should deal with Pcore serialization only (that is, no Json, MsgPack etc. knowledge encoded in objects.* Serialization should be guided by Pcore meta model associated with an objectAs there is no user facing logic (yet) - it is accepted that features are demonstrated with unit tests. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Release Notes Summary: This is part of a larger feature and at this point, this enabling technology is not user facing. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5909 Implement a PCore serializer for JSON Machine to Machine Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5909) Implement a PCore serializer for JSON Machine to Machine
Title: Message Title Henrik Lindberg commented on PUP-5909 Re: Implement a PCore serializer for JSON Machine to Machine merged to master at: 33bfac1 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6233) Serivce SMF restart should use -s
Title: Message Title Eric Thompson commented on PUP-6233 Re: Serivce SMF restart should use -s against solaris 11.1 at master puppet-agent SHA: 9ebaca9b0ca2390aff7b86ef868c66d42a4d3755 as expected, no -s synchronous option root@myv8h1p74knb9h7:~# puppet resource service sendmail ensure=running --debug Debug: Runtime environment: puppet_version=4.6.0, ruby_version=2.1.9, run_mode=user, default_encoding=UTF-8 [] Debug: Executing: '/usr/bin/svcs -H -o state,nstate sendmail' Debug: Finishing transaction 81847770 Debug: Storing state Debug: Stored state in 0.01 seconds Debug: Executing: '/usr/bin/svcs -H -o state,nstate sendmail'
Jira (PDB-2851) reject POST query requests that are missing content-type
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2851 reject POST query requests that are missing content-type Issue Type: Bug Assignee: Unassigned Created: 2016/07/05 2:08 PM Priority: Normal Reporter: Wyatt Alt Currently if a POST query is issued without the Content-Type header, PDB will return all results from the endpoint as if no query were supplied, which can be very confusing. Instead the query should error with a nice message. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6233) Serivce SMF restart should use -s
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6233 Serivce SMF restart should use -s Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6431) puppet parser validate stalls when run over SSH with no manifest specified
Title: Message Title Eric Thompson commented on PUP-6431 Re: puppet parser validate stalls when run over SSH with no manifest specified this... might be a feature. testing works around this by specifying is_tty to beaker #on DSL method options. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6233) Serivce SMF restart should use -s
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6233 Serivce SMF restart should use -s Change By: Eric Thompson QA Risk Assessment: High Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title
Eric Thompson commented on PUP-6463
Re: Accessing a required parameter that is unassigned causes bad error message
covered well via unit tests. validating anyway, for kicks... puppet-agent master SHA: 9ebaca9b0ca2390aff7b86ef868c66d42a4d3755
root@jg3iiu6yse03viw:~# puppet apply default_ref.pp
Error: Evaluation Error: Error while evaluating a Function Call, Class[Breaking]: expects a value for parameter $first at /root/default_ref.pp:7:3 on node jg3iiu6yse03viw.delivery.puppetlabs.net
root@jg3iiu6yse03viw:~# cat default_ref.pp
class breaking (
String $first,
String $second = $first,
){}
node default {
include breaking
Jira (PUP-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Andrew Henroid updated an issue Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Andrew Henroid Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Andrew Henroid updated an issue Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Andrew Henroid Scope Change Category: Adopted Scope Change Reason: onboarding Sprint: Client 2016-07-13 (HA, 1.5.3) Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1405) Facter does not like next hop flags in ip route output
Title: Message Title Andrew Henroid assigned an issue to Andrew Henroid Facter / FACT-1405 Facter does not like next hop flags in ip route output Change By: Andrew Henroid Assignee: Andrew Henroid Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6004) should_modify_gid acceptance tests should generate an unused unique id
Title: Message Title Eric Thompson commented on PUP-6004 Re: should_modify_gid acceptance tests should generate an unused unique id Sean Griffin FYI Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Peter Souter commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards Still missing as of 3.4.0 (commit 02d18bb74bae8f707ed974d8a8421fd79f3f9ee9): architecture augeasversion boardmanufacturer boardproductname boardserialnumber domain fqdn hardwaremodel hostname interfaces ipaddress
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Rob Reynolds assigned an issue to James Pogran Puppet / PUP-6473 FFI 1.9.11 has a bug when running on Windows Change By: Rob Reynolds Assignee: James Pogran Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Rob Reynolds commented on PUP-6473 Re: FFI 1.9.11 has a bug when running on Windows Modsync PR merged in at https://github.com/puppetlabs/modulesync_configs/commit/99efa61397653903cee4f81592c3d8f70bfd34e5 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti commented on PUP-6473 Re: FFI 1.9.11 has a bug when running on Windows PR Raised for modsync https://github.com/puppetlabs/modulesync_configs/pull/72 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti commented on PUP-6473 Re: FFI 1.9.11 has a bug when running on Windows PR Raised to pin the gem https://github.com/puppetlabs/puppet/pull/5085 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1451) Update ubuntu kernel version fact regex in facter acceptance tests
Title: Message Title Sean Griffin assigned an issue to qa Facter / FACT-1451 Update ubuntu kernel version fact regex in facter acceptance tests Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Kyle Decot updated an issue
Hiera / HI-522
deeper merge not being respected
Change By:
Kyle Decot
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as: :hierarchy: - "%{::fqdn}" - common:merge_behavior: deeper:deep_merge_options: :knockout_prefix: '--'I have also installed the gem using:puppetserver gem install deep_mergeIn common.yaml I have something like:foo: - bar: "hello" - baz: "world"and then in my node's yaml file I havefoo: "hello"When performing a run w/ hiera("foo", {}) I'm only getting a single item when I would expect two
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (HI-522) deeper merge not being respected
Title: Message Title
Kyle Decot created an issue
Hiera / HI-522
deeper merge not being respected
Issue Type:
Bug
Affects Versions:
HI 3.1.1
Assignee:
Unassigned
Components:
Community
Created:
2016/07/05 12:03 PM
Priority:
Normal
Reporter:
Kyle Decot
When performing `puppet agent -t` on my node I am not receiving the hiera values that I expect. I have specified the deeper merge strategy as:
:hierarchy:
"%{::fqdn}"
common :merge_behavior: deeper :deep_merge_options: :knockout_prefix: '--'
I have also installed the gem using:
puppetserver gem install deep_merge
In common.yaml I have something like:
foo:
Jira (HI-519) Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8
Title: Message Title Kylo Ginsberg commented on HI-519 Re: Hiera Filecache doesn't support encoding / doesn't load JSON backend files as UTF-8 Yeah this sounds like just a bug-fix, not a feature, so I'd consider this a Z. However, AFAICT, we haven't released 3.2.1 yet. If so, it would be 3.2.1. If I missed something and there is a 3.2.1 release, then yeah, this would be 3.2.2. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti updated an issue Puppet / PUP-6473 FFI 1.9.11 has a bug when running on Windows Change By: Glenn Sarti Priority: Normal Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2850) puppet-client-tools 1.0.1 has no `puppet-db status`
Title: Message Title Andrew Roetker commented on PDB-2850 Re: puppet-client-tools 1.0.1 has no `puppet-db status` The `puppet-db status` command is only on the master branch currently. The released version of the CLI (1.0.1) corresponds to the stable branch (https://github.com/puppetlabs/puppetdb-cli/blob/stable/README.md). The master branch and the status command should be released in the coming weeks! Thanks for using the CLI though and raising the issue, I'll make sure to note the feature has not been released yet in the README. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2850) puppet-client-tools 1.0.1 has no `puppet-db status`
Title: Message Title Stefan Heijmans created an issue PuppetDB / PDB-2850 puppet-client-tools 1.0.1 has no `puppet-db status` Issue Type: Bug Affects Versions: PDB CLI 1.0.1 Assignee: Unassigned Components: PuppetDB Created: 2016/07/05 11:47 AM Environment: Centos 7.2/RHEL7.2 x86_64 puppet-agent-1.5.2 puppetdb-4.1.2 puppet-client-tools-1.0.1 Priority: Normal Reporter: Stefan Heijmans The README.md shows that there is a `puppet-db status` available. $ puppet-db status
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti assigned an issue to Glenn Sarti Puppet / PUP-6473 FFI 1.9.11 has a bug when running on Windows Change By: Glenn Sarti Assignee: Glenn Sarti Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6390) Acceptance: unpin run order for service_enable_linux test
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6390 Acceptance: unpin run order for service_enable_linux test Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6463) Accessing a required parameter that is unassigned causes bad error message
Title: Message Title Sean Griffin assigned an issue to qa Puppet / PUP-6463 Accessing a required parameter that is unassigned causes bad error message Change By: Sean Griffin Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti commented on PUP-6473 Re: FFI 1.9.11 has a bug when running on Windows Example with FFI 1.9.11 PS C:\source\puppet> bundle exec puppet version C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/ffi-1.9.11-x64-mingw32/lib/ffi/library.rb:126:in `rescue in block (2 levels) in ffi_lib': undefined method `start_with?' for :shell32:Symbol (NoMethodError) from C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/ffi-1.9.11-x64-mingw32/lib/ffi/library.rb:111:in `block (2 levels) in ffi_lib' from C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/ffi-1.9.11-x64-mingw32/lib/ffi/library.rb:110:in `each' from C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/ffi-1.9.11-x64-mingw32/lib/ffi/library.rb:110:in `block in ffi_lib' from C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/ffi-1.9.11-x64-mingw32/lib/ffi/library.rb:100:in `map' from C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/ffi-1.9.11-x64-mingw32/lib/ffi/library.rb:100:in `ffi_lib' from C:/source/puppet/.bundle/gems/ruby/2.1.0/gems/win32-dir-0.4.9/lib/win32/dir/functions.rb:25:in `'
Jira (PUP-4634) Add some timings/metrics in report
Title: Message Title Maggie Dreyer updated an issue Puppet / PUP-4634 Add some timings/metrics in report Change By: Maggie Dreyer Sprint: i18n Client 2016-07-27 facter.conf Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-84) Add the ability to generate only JSON
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-84 Add the ability to generate only JSON Issue Type: Improvement Assignee: Unassigned Created: 2016/07/05 11:36 AM Fix Versions: PDOC 0.5.0 Priority: Normal Reporter: Hailee Kenney Whether it's a rake task, a subcommand, or both we need to add a way to generate only the single JSON file and not the entire doc directory of HTML pages. I'm not sure if it's possible to also prevent yard from producing the additional output like the .yardoc directory, but either way we need to clearly define what will be generated and where so that it can be automatically scrapped as appropriate. Add Comment
Jira (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Michael Smith commented on FACT-1428 Re: FreeBSD facts are missing from Facter 3.X onwards This is apparently still in-progress, despite some merges. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6473) FFI 1.9.11 has a bug when running on Windows
Title: Message Title Glenn Sarti created an issue Puppet / PUP-6473 FFI 1.9.11 has a bug when running on Windows Issue Type: Bug Assignee: Unassigned Created: 2016/07/05 11:22 AM Priority: Normal Reporter: Glenn Sarti FFI 1.9.11 was released on July 5th 2016 however it seems to have a bug when running on Windows and specifying a library via a symbol (as opposed to a string). There is an issue raised on Github for it. https://github.com/ffi/ffi/issues/506 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-1913) Puppet user resource should respect the forcelocal option
Title: Message Title
Agustin commented on PUP-1913
Re: Puppet user resource should respect the forcelocal option
I am seeing some strange behavior when using forge module kyleanderson/consul for instance.
I have authenticaion via pam with ldap. The module creates ok the local user, but when it runs again and all subsequent runs, take 60 more seconds than before. It used to take 4 secs the whole run, but as the consul module tries to eval the User consul, it seems it searches in my entire ldap and takes 60 seconds more. I put on my site.pp to default to User { forcelocal => true }
but no luck. It still wastes 60 seconds on User.
Package: 1.75 Last run: 1467731830 User: 51.14 Config retrieval: 6.60 Total: 61.44 Version: Config: 1467731750 Puppet: 4.5.2
How can i help? Cheers!
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1432) Fixup OpenBSD networking facts
Title: Message Title Michael Smith updated an issue Facter / FACT-1432 Fixup OpenBSD networking facts Change By: Michael Smith Release Notes Summary: Release notes should be in FACT-1148. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1339) swap fact on OpenBSD
Title: Message Title Michael Smith updated an issue Facter / FACT-1339 swap fact on OpenBSD Change By: Michael Smith Fix Version/s: FACT 2.4.7 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1339) swap fact on OpenBSD
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1339 swap fact on OpenBSD Change By: Michael Smith Status: Open Ready for Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title William Hopper commented on PUP-6384 Re: Acceptance: test that agent failover behavior works correctly Ah, yeah, this is happening because the Windows installer adds server to puppet.conf by default, thus causing the conflicting settings warning when we run with server_list via the command line. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1432) Fixup OpenBSD networking facts
Title: Message Title John Duarte commented on FACT-1432 Re: Fixup OpenBSD networking facts Peter Huene or Michael Smith, could you add a release note to this ticket? Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1432) Fixup OpenBSD networking facts
Title: Message Title John Duarte updated an issue Facter / FACT-1432 Fixup OpenBSD networking facts Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1432) Fixup OpenBSD networking facts
Title: Message Title John Duarte updated an issue Facter / FACT-1432 Fixup OpenBSD networking facts Change By: John Duarte QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1434) Recognize "wxallowed" as mount option
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1434 Recognize "wxallowed" as mount option Change By: Michael Smith Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1428) FreeBSD facts are missing from Facter 3.X onwards
Title: Message Title Michael Smith updated an issue Facter / FACT-1428 FreeBSD facts are missing from Facter 3.X onwards Change By: Michael Smith Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1434) Recognize "wxallowed" as mount option
Title: Message Title Michael Smith updated an issue Facter / FACT-1434 Recognize "wxallowed" as mount option Change By: Michael Smith Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1447) Debug logging when Windows identity resolution fails throws an exception
Title: Message Title Michael Smith updated an issue Facter / FACT-1447 Debug logging when Windows identity resolution fails throws an exception Change By: Michael Smith Fix Version/s: FACT 3.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-83) Define a proper JSON schema for strings
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-83 Define a proper JSON schema for strings Issue Type: Improvement Assignee: Unassigned Created: 2016/07/05 9:33 AM Priority: Normal Reporter: Hailee Kenney In order to ensure that strings produces JSON in a way that's consistent and workable. The language and docs teams should work together to define a schema that makes sense and will suit the needs of the docs team. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6398) Executing parallel specs on Windows is not reliable
Title: Message Title Craig Gomes assigned an issue to Ethan Brown Puppet / PUP-6398 Executing parallel specs on Windows is not reliable Change By: Craig Gomes Assignee: Ethan Brown Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5649) "syncversion" maybe obsolete for selmodule type in Fedora >= 23
Title: Message Title Ben Ford commented on PUP-5649 Re: "syncversion" maybe obsolete for selmodule type in Fedora >= 23 This is going to be the behavior in RHEL/CentOS 8, so we should get on top of this soon. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Eric Thompson assigned an issue to Maggie Dreyer Puppet / PUP-6384 Acceptance: test that agent failover behavior works correctly Change By: Eric Thompson Assignee: Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6384 Acceptance: test that agent failover behavior works correctly Change By: Eric Thompson Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Eric Thompson commented on PUP-6384 Re: Acceptance: test that agent failover behavior works correctly Maggie Dreyer this is failing on windows: https://jenkins.puppetlabs.com/job/platform_puppet_intn-van-sys_master/284/ Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6384) Acceptance: test that agent failover behavior works correctly
Title: Message Title Eric Thompson updated an issue Puppet / PUP-6384 Acceptance: test that agent failover behavior works correctly Change By: Eric Thompson Issue Type: Task CI Blocker Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-60 Strings skips docs for the log message functions Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-61) Strings finds bogus "function_definition" function
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-61 Strings finds bogus "function_definition" function Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-63) Blizzard of errors and warnings when run against core code
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-63 Blizzard of errors and warnings when run against core code Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-82) Ensure the strings gem can be managed via bundler in docs scripts
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-82 Ensure the strings gem can be managed via bundler in docs scripts Issue Type: Improvement Assignee: Unassigned Created: 2016/07/05 7:45 AM Fix Versions: PDOC 0.5.0 Priority: Normal Reporter: Hailee Kenney Because the docs team would like to use strings in their automated doc extraction scripts, we need to ensure that the gem can be used and managed with bundler in that context. It needs to work out of the box and can’t contaminate the user’s environment outside of bundler. There's not really any reason to believe that this won't work, but since it's essential we should verify it. The scripts in question live here Add Comment
Jira (PDOC-59) Improve behavior of Strings to support integration into Docs workflow
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-59 Improve behavior of Strings to support integration into Docs workflow Change By: Hailee Kenney Fix Version/s: PDOC 0.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6472) Puppet Lookup does not interpolate local variables from calling scope
Title: Message Title Henrik Lindberg commented on PUP-6472 Re: Puppet Lookup does not interpolate local variables from calling scope CJ Toolseram Allowing the configuration to differ based on local scope is a really bad idea. In large installations there are millions of look ups from different contexts - changing the configuration per context means that cache has to be completely invalidated. That will have a severe performance impact. A change such as that will simply not be accepted; hence the "won't do" closing. The implementations of both hiera and lookup are public, they are in the hiera and puppet git repositories at git hub. So, not sure what "code" you want to get access to that would not be there. The "lookup" functionality is only marked as experimental as we wanted to reserved the right to modify its API. No such things have yet been found and we are very close to removing the "experimental" flag on the lookup feature. Also, please do not make comments private to developers only as this is an open source project. We only use that when there is sensitive user information in a post, or when there is something truly internal to puppet inc of administrative nature (links to support tickets, and the like). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title Thomas Hallgren updated an issue Puppet / PUP-5887 Interpolation in interpolation nested string does not work. Change By: Thomas Hallgren Scope Change Category: Found Scope Change Reason: TODO list is empty. Sprint: Language Triage 2016-07-13 Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-5887 Interpolation in interpolation nested string does not work. Change By: Thomas Hallgren Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title
Henrik Lindberg commented on PUP-5887
Re: Interpolation in interpolation nested string does not work.
This should be an error. There must be an _expression_ to interpolate or you do not need the interpolation at all. One could argue that the language should support this, and that it is the same as interpolating undef / empty string. The only time that would be of value is if a user wants to temporarily comment out an interpolation and thus leaving no _expression_ at all. Otherwise it is a big difference having an empty string, or _expression_ evaluating to empty string/undef in the interpolation as you probably forgot something and thus it should be flagged.
I think we should continue to treat this as an error: {code:puppet}} notice "${}" # fails with syntax error.
But, if others think it is of value to be able to comment out an _expression_ when testing/hacking, I can accept that we relax the requirement that there must be exactly one _expression_ there.
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
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
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title
Thomas Hallgren commented on PUP-5887
Re: Interpolation in interpolation nested string does not work.
I see one more discrepancy:
notice "${""}" # ok, prints an empty string
notice "${}" # fails with syntax error.
Is it correct to assume that both should work or both should fail?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title
Henrik Lindberg commented on PUP-5887
Re: Interpolation in interpolation nested string does not work.
You get the same error if $foo has a value.
notice "${"a"}" # works, notices 'a'
$foo = 'a'
notice "${"$foo"}" # fails with syntax error
notice "${"${foo}"}" # fails with syntax error
notice "${undef}" # emits warning "undef is an unknown variable"
function x() { undef }
notice "${x()}" # ok, prints an empty string
Lexing is not right - there should be no syntax errors. There is also a problem with 'undef' not being recognized. If there is an _expression_ that returns undef it works the way it is supposed to, but not when undef is given as a keyword.
Add Comment
Jira (PUP-6472) Puppet Lookup does not interpolate local variables from calling scope
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6472 Puppet Lookup does not interpolate local variables from calling scope Change By: Henrik Lindberg Summary: Puppet Lookup does only went through the module hieradata once not interpolate local variables from calling scope Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6472) Puppet Lookup does only went through the module hieradata once
Title: Message Title Henrik Lindberg commented on PUP-6472 Re: Puppet Lookup does only went through the module hieradata once I am closing this as a won't fix - letting local variables have an impact on the hierarchy would be both confusing and inefficient. We already have --strict_variables, which should really also be applied to interpolation of variables in the hiera config as well. It is really a separate ticket, plus additional discussion about the implications (not all nodes have the same facts, etc). Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5887) Interpolation in interpolation nested string does not work.
Title: Message Title
Thomas Hallgren commented on PUP-5887
Re: Interpolation in interpolation nested string does not work.
If ${foo} results in undef (which becomes an empty string), then the first _expression_ is the same as "${}" and the syntax error is correct. It doesn't say that it is on the closing double qoute, it reports two single quotes, i.e. "syntax error at " which I interpret as "syntax error at empty string". So is this really a bug?
Add Comment
This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
