Jira (PUP-6525) Add Ranges to DSL
Title: Message Title Kyle Chickering created an issue Puppet / PUP-6525 Add Ranges to DSL Issue Type: Improvement Affects Versions: PUP 4.5.2 Assignee: Unassigned Components: DSL Created: 2016/07/19 7:03 PM Environment: All Priority: Minor Reporter: Kyle Chickering Add ranges to the puppet DSL Currently for a resource that may take a number as a namevar, declaring multiple resources looks something like this: resource { ['1', '2', '3', '4', '5']:
Jira (PUP-6343) Add catalog apply time to Puppet::Util::Metric "time" category
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-6343 Add catalog apply time to Puppet::Util::Metric "time" category Change By: Adam Bottchen Sprint: Client Triage Component/s: Client 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-6344 metrics.time.total does not correlate to time reported in log Change By: Adam Bottchen Component/s: Client 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-6344) metrics.time.total does not correlate to time reported in log
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-6344 metrics.time.total does not correlate to time reported in log Change By: Adam Bottchen 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-6524) The shell used with exec resource provider=shell should be configurable
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-6524 The shell used with exec resource provider=shell should be configurable Change By: Adam Bottchen Sprint: Client Triage 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-6524) The shell used with exec resource provider=shell should be configurable
Title: Message Title Adam Bottchen moved an issue Puppet / PUP-6524 The shell used with exec resource provider=shell should be configurable Change By: Adam Bottchen Component/s: puppet Component/s: Client Key: PE PUP - 14558 6524 Project: Puppet Enterprise [Internal] 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-5463) undef not usable in collector search?
Title: Message Title Geoff Williams updated an issue Puppet / PUP-5463 undef not usable in collector search? Change By: Geoff Williams CS Priority: Needs Priority CS Impact: Requesting CS assessment of this bug. Support are hitting this with Optus: 2200nodes/$460K product sold.Dylan Ratcliffe has come up with a really ugly workaround for this customer that involves duplicating a built in type and conditionally altering the defaults. This places the maintenance burden on the customer and could make future upgrades problematic.It would be a neater solution for all involved if we could simply fix the bug in the puppet agent. Support ticket is here: https://puppetlabs.zendesk.com/agent/tickets/20119 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-1466) Facter warns aboutIt difficulty parsing routing entries on Fedora 24
Title: Message Title Martin Jackson created an issue Facter / FACT-1466 Facter warns aboutIt difficulty parsing routing entries on Fedora 24 Issue Type: Bug Assignee: Unassigned Created: 2016/07/19 5:15 PM Priority: Normal Reporter: Martin Jackson Under some circumstances (such as when running libvirtd with the standard NAT network, or any situation where the route output includes "linkdown"), Facter complains about not being able to parse route output: 2016-07-19 19:04:33.871180 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got '192.168.6.0/24 dev br6 proto kernel scope link src 192.168.6.1 metric 425 linkdown' 2016-07-19 19:04:33.872683 WARN puppetlabs.facter - Could not process routing table entry: Expected a destination followed by key/value pairs, got 'fe80::/64 dev br6 proto kernel metric 256 linkdown pref medium' Here is the ip route output: 192.168.1.0/24 proto zebra metric 20 nexthop via 192.168.5.2 dev br5 weight 1 nexthop via 192.168.5.3 dev br5 weight 1 192.168.4.0/24 proto zebra metric 20 nexthop via 192.168.5.2 dev br5 weight 1 nexthop via 192.168.5.3 dev br5 weight 1 192.168.5.0/24 dev br5 proto kernel scope link src 192.168.5.15 metric 425 192.168.6.0/24 dev br6 proto kernel scope link src 192.168.6.1 metric 425 linkdown 192.168.129.0/24 dev br900 proto kernel scope link src 192.168.129.15 metric 425 rpm -qf /usr/sbin/ip iproute-4.4.0-3.fc24.x86_64 It is not clear that this actually causes a problem, but the warning messages are a bit jarring.
Jira (PDB-2888) Add flag for turning off JSONB related storage in PuppetDB
Title: Message Title Larry Copeland updated an issue PuppetDB / PDB-2888 Add flag for turning off JSONB related storage in PuppetDB Change By: Larry Copeland Attachment: Screen Shot 2016-07-15 at 11.30.19 PM.png 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-2892) Nested implicit subqueries fail unless trivial
Title: Message Title Ryan Whitehurst updated an issue PuppetDB / PDB-2892 Nested implicit subqueries fail unless trivial Change By: Ryan Whitehurst Basically, if you have nested subqueries, if the query for the middle one is anything other than just a wrapper around the deepest one, PDB fails saying "No implicit relationship for entity 'foo'". This seems to be true for any valid relationship. This happens when submitting both an AST query or a PQL query . Examples:{code}[rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=nodes { certname = "bar" and resources { type = "Foo" } }'[][rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=facts [value] { name = "fqdn" and nodes { resources { type = "Foo" } } }'[][rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=facts { name = "fqdn" and nodes { certname = "bar" and resources { type = "Foo" } } }'No implicit relationship for entity 'resources'[rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=["from", "facts", ["and", ["=", "name", "fqdn"], ["subquery", "nodes", ["subquery", "resources", ["=", "type", "Foo"]'[][rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=["from", "facts", ["and", ["=", "name", "fqdn"], ["subquery", "nodes", ["and", ["=", "certname", "bar"], ["subquery", "resources", ["=", "type", "Foo"]]'No implicit relationship for entity 'resources' # this one is kind of weird [rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query= ["from", "facts", ["and", ["=", "name", "fqdn"], ["subquery", "nodes", ["and", ["subquery", "facts", ["=", "name", "foo"]]'No implicit relationship for entity 'facts'[rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query= reports { environments { resources { type = "Foo" } } }'[][rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=reports { environments { name = "bar" and resources { type = "Foo" } } }'No implicit relationship for entity 'resources'[rw@pe-mom2-test ~]curl -sXGET localhost:8080/pdb/query/v4 -d 'query=facts { name = "foo" and nodes { facts { name = "bar" } } }'[][rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=facts { name = "foo" and nodes { certname = "baz" and facts { name = "bar" } } }'No implicit relationship for entity 'facts'{code} Add Comment
Jira (PDB-2892) Nested implicit subqueries fail unless trivial
Title: Message Title Ryan Whitehurst created an issue PuppetDB / PDB-2892 Nested implicit subqueries fail unless trivial Issue Type: Bug Assignee: Unassigned Created: 2016/07/19 4:09 PM Priority: Normal Reporter: Ryan Whitehurst Basically, if you have nested subqueries, if the query for the middle one is anything other than just a wrapper around the deepest one, PDB fails saying "No implicit relationship for entity 'foo'". This seems to be true for any valid relationship. This happens when submitting both an AST query or a PQL query Examples: [rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=nodes { certname = "bar" and resources { type = "Foo" } }' [] [rw@pe-mom2-test ~]$ curl -sXGET localhost:80
Jira (PDB-2891) Spaces around parens in PQL generate a parse error
Title: Message Title Andrew Roetker assigned an issue to Andrew Roetker PuppetDB / PDB-2891 Spaces around parens in PQL generate a parse error Change By: Andrew Roetker Assignee: Andrew Roetker 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-2891) Spaces around parens in PQL generate a parse error
Title: Message Title Ryan Whitehurst created an issue PuppetDB / PDB-2891 Spaces around parens in PQL generate a parse error Issue Type: Bug Assignee: Unassigned Created: 2016/07/19 3:37 PM Priority: Normal Reporter: Ryan Whitehurst [rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=resources { type = "Foo" and (title = "bar" or title = "baz")'} [] [rw@pe-mom2-test ~]$ curl -sXGET localhost:8080/pdb/query/v4 -d 'query=resources { type = "Foo" and ( title = "bar" or title = "baz" ) }'
Jira (PDB-2890) Investigate convergence test failure
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2890 Investigate convergence test failure Issue Type: Bug Assignee: Rob Browning Created: 2016/07/19 3:29 PM Priority: Normal Reporter: Rob Browning https://jenkins-enterprise.delivery.puppetlabs.net/job/enterprise_pe-puppetdb-extensions_unit-clj-puppetdb_master/692/JDK=oraclejdk8,PUPPETDB_DBTYPE=postgres,label=integration/console Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PDB-2889) stockpile: don't skip token values
Title: Message Title Rob Browning created an issue PuppetDB / PDB-2889 stockpile: don't skip token values Issue Type: Bug Assignee: Rob Browning Created: 2016/07/19 3:26 PM Priority: Normal Reporter: Rob Browning 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Nicholas Fagerlund commented on PUP-6496 Re: Add support for using hocon for main hiera config file OK. How about: Leave it in "needs information" Unassign Jane Move it to the PUP-6484 epic ? 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Henrik Lindberg commented on PUP-6496 Re: Add support for using hocon for main hiera config file Nicholas Fagerlund I think it depends on what is decided wrt. a "global layer" - should we have one? If so, how do we migrate? This ticket should be blocked on that decision at least. 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-3375) File Diffs on Windows
Title: Message Title Kenaz Kwa commented on PUP-3375 Re: File Diffs on Windows Elizabeth Plumb Can you outline the scenario that Putnam is looking for here? To clarify, as Josh points out, there are a couple ways to do this – the easiest in my mind using the cmd fc tool: C:\temp>more test1.txt test1 C:\temp>more test2.txt test1 test2 test3 C:\temp>fc test1.txt test2.txt Comparing files test1.txt and TEST2.TXT
Jira (PUP-6496) Add support for using hocon for main hiera config file
Title: Message Title Nicholas Fagerlund commented on PUP-6496 Re: Add support for using hocon for main hiera config file Henrik Lindberg Yeah! Should we close this as a duplicate of PUP-6512? Or close it wontfix since its original description referred to hiera.yaml (classic)? Or do something else? 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-6310) Specify the PCore Serialization formats
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6310 Specify the PCore Serialization formats Change By: Henrik Lindberg Sprint: Language 2016-08-10 (3rd 1.6.0 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-6255) Add documentation for Object.new in function new
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6255 Add documentation for Object.new in function new Change By: Henrik Lindberg Sprint: Language 2016-08-10 (3rd 1.6.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-3170) Cap integer and float sizes
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-3170 Cap integer and float sizes Change By: Henrik Lindberg Sprint: Language 2016-08-10 (3rd 1.6.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-6252) reorganize documentation of function 'new'
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6252 reorganize documentation of function 'new' Change By: Henrik Lindberg Sprint: Language 2016-08-10 (3rd 1.6.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-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 2016-08-10 (3rd 1.6.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-6512) Change hiera.yaml (v4) to lookup.conf
Title: Message Title Nicholas Fagerlund commented on PUP-6512 Re: Change hiera.yaml (v4) to lookup.conf OK, I'm fine with that. 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Henrik Lindberg commented on PUP-6496 Re: Add support for using hocon for main hiera config file Ping Nicholas Fagerlund - this relates to the "finishing of lookup" 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6496 Add support for using hocon for main hiera config file Change By: Henrik Lindberg Fix Version/s: PUP 4.6.x Fix Version/s: PUP 4.7.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-6476) Add Hocon support to Puppet
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Henrik Lindberg Fix Version/s: PUP 4.6.x Fix Version/s: PUP 4.7.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-6476) Add Hocon support to Puppet
Title: Message Title Henrik Lindberg commented on PUP-6476 Re: Add Hocon support to Puppet Changed version from 4.6.x to 4.7.0 since this is a new feature, not just a bug fix. Hocon libraries also needs to be included in the builds - that is too much for a .z release. 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-6512) Change hiera.yaml (v4) to lookup.conf
Title: Message Title Henrik Lindberg commented on PUP-6512 Re: Change hiera.yaml (v4) to lookup.conf If we are making changes to the 4 format, we should bump it to 5. Typically an implementation would accept several versions (all that are still supported). This is particularly important for modules. Basically it is the content of a hash that changes version - the fact that it comes from a .yaml or .hocon is something different. 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-2857) export: use Files/copy to transfer data
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2857 export: use Files/copy to transfer data Change By: Ryan Senior Fix Version/s: PDB 4.1.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 (PUP-6500) Investigate end to end workflow of puppet generate with code manager and r10k
Title: Message Title Peter Huene commented on PUP-6500 Re: Investigate end to end workflow of puppet generate with code manager and r10k Zachary Smith with respect to my issue #2 above, is there some context such as an environment variable or another mechanism our tool could key off of to determine the environment being deployed? 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-6500) Investigate end to end workflow of puppet generate with code manager and r10k
Title: Message Title Peter Huene commented on PUP-6500 Re: Investigate end to end workflow of puppet generate with code manager and r10k I was able to successfully hook in our generate tool by editing /opt/puppetlabs/server/data/code-manager/r10k.yaml to include this line: postrun: ["/usr/local/bin/puppet", "generate", "types", "--environment=production", "--environmentpath=/etc/puppetlabs/code-staging/environments"] and then triggering a deploy with puppet-code deploy production --wait. I used a nearly default template for the branch at: https://github.com/peterhuene/code-manager-test I verified that the modules with types have a pcore subdirectory in them (note: the output of the tool is out-of-date with respect to latest design decisions) and the output of the tool is correct. 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-1386) puppet agents complain about master not-being UTF-8
Title: Message Title C Lang commented on PUP-1386 Re: puppet agents complain about master not-being UTF-8 Would it make sense to have the default config.ru set the encoding to UTF-8 so mod_passenger matches standalone ? 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-1796) File resource fails for root(/) directory.
Title: Message Title Andrew Henroid updated an issue Puppet / PUP-1796 File resource fails for root(/) directory. Change By: Andrew Henroid Scope Change Category: Adopted Scope Change Reason: customer escalation Story Points: 1 Sprint: 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 (PUP-6512) Change hiera.yaml (v4) to lookup.conf
Title: Message Title Nicholas Fagerlund commented on PUP-6512 Re: Change hiera.yaml (v4) to lookup.conf But version 4 was for a yaml file called hiera.yaml with a particular format, right? And we're switching to a hocon file called lookup.conf with a slightly different format (to accommodate non-filesystem backends), right? I suppose we could just say we're skipping a bunch of versions and bump it to 5. But given the identity change, why not reset the count? 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-6391) Ubuntu 16.10 support in systemd provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6391 Ubuntu 16.10 support in systemd provider Change By: Kylo Ginsberg Release Notes Summary: This change adds systemd as the default service provider for ubuntu 16.10. 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-6391) Ubuntu 16.10 support in systemd provider
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-6391 Ubuntu 16.10 support in systemd provider Change By: Kylo Ginsberg Release Notes: New Feature 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-6391) Ubuntu 16.10 support in systemd provider
Title: Message Title Kylo Ginsberg commented on PUP-6391 Re: Ubuntu 16.10 support in systemd provider Note to ticket watchers: this has passed CI (a while ago), and per my earlier comment, doesn't need internal QA assessment, so skipping Ready for Test. 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-1796) File resource fails for root(/) directory.
Title: Message Title David Kramer updated an issue Puppet / PUP-1796 File resource fails for root(/) directory. Change By: David Kramer Fix Version/s: PUP 4.6.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-1796) File resource fails for root(/) directory.
Title: Message Title David Kramer assigned an issue to Andrew Henroid Puppet / PUP-1796 File resource fails for root(/) directory. Change By: David Kramer 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 (FACT-1454) When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1454 When upgrading to Ruby 2.3 for Puppet-agent, libfacter_tests segfaults Change By: Michael Smith Status: Ready for Merge 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-6240) Deprecate old semantic version implementation
Title: Message Title David Kramer updated an issue Puppet / PUP-6240 Deprecate old semantic version implementation Pushing to PUP 4.7.0 and taking out of the upcoming sprint while we wait for the blocking work to be resolved. Change By: David Kramer Sprint: Language 2016-06-01 , Language 2016-08-10 (3rd 1.6.0 Fix Version/s: PUP 4.6.0 Fix Version/s: PUP 4.7.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
Jira (PUP-6476) Add Hocon support to Puppet
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Karen Van der Veer Fix Version/s: PUP 4.y Fix Version/s: PUP 4.6.x 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6496 Add support for using hocon for main hiera config file Change By: Karen Van der Veer Fix Version/s: PUP 4.y Fix Version/s: PUP 4.6.x 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-6496) Add support for using hocon for main hiera config file
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6496 Add support for using hocon for main hiera config file Change By: Karen Van der Veer Fix Version/s: PUP 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 (PUP-6476) Add Hocon support to Puppet
Title: Message Title Karen Van der Veer updated an issue Puppet / PUP-6476 Add Hocon support to Puppet Change By: Karen Van der Veer Fix Version/s: PUP 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-1465) acceptance test: tests/facts/ubuntu.rb fails because dhcp server has adddress: 192.168.x.x
Title: Message Title Sean Griffin commented on FACT-1465 Re: acceptance test: tests/facts/ubuntu.rb fails because dhcp server has adddress: 192.168.x.x A fix for the ubuntu 10.04 specific case has been merged, see PR# 1387 for facter,https://github.com/puppetlabs/facter/pull/1378. General consensus there is that the regex for IP addresses in each of the test files should not limit the address to 10.x.x.x. Instead the pattern should be the one in sles.rb, https://github.com/puppetlabs/facter/blob/master/acceptance/tests/facts/sles.rb#L12 Files in facter/acceptance/tests/facts to be modified: ubuntu.rb, debian.rb, fedora.rb, macosx.rb, solaris.rb, and windows.rb 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-1465) acceptance test: tests/facts/ubuntu.rb fails because dhcp server has adddress: 192.168.x.x
Title: Message Title Sean Griffin assigned an issue to Sean Griffin Facter / FACT-1465 acceptance test: tests/facts/ubuntu.rb fails because dhcp server has adddress: 192.168.x.x Change By: Sean Griffin Assignee: Sean Griffin 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-5908) Implement a PCore MsgPack Serializer
Title: Message Title David Kramer updated an issue Puppet / PUP-5908 Implement a PCore MsgPack Serializer Pushing to PUP 4.7.0 and taking out of the upcoming sprint while we wait for the blocking work to be resolved. Change By: David Kramer Sprint: Language 2016-06-29 , Language 2016-08-10 (3rd 1.6.0 Fix Version/s: PUP 4.6.0 Fix Version/s: PUP 4.7.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
Jira (PUP-4742) Bring semantic_puppet library into Puppet
Title: Message Title David Kramer updated an issue Puppet / PUP-4742 Bring semantic_puppet library into Puppet Pushing to PUP 4.7.0 and taking out of the upcoming sprint while we wait for the blocking work to be resolved. Change By: David Kramer Sprint: Language 2016-06-01, Language 2016-06-15, Language 2016-06-29 , Language 2016-08-10 (3rd 1.6.0 Fix Version/s: PUP 4.6.0 Fix Version/s: PUP 4.7.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...@googlegr
Jira (FACT-1465) acceptance test: tests/facts/ubuntu.rb fails because dhcp server has adddress: 192.168.x.x
Title: Message Title Sean Griffin created an issue Facter / FACT-1465 acceptance test: tests/facts/ubuntu.rb fails because dhcp server has adddress: 192.168.x.x Issue Type: CI Blocker Assignee: Unassigned Created: 2016/07/19 9:58 AM Priority: Normal Reporter: Sean Griffin The Facter Tests step (step 5) in the master puppet-agent pipeline fails on ubuntu-1004-x86_64 because that platform reports a dhcp server address of 192.168.2.254 and the test requires a dhcp server address of the form 10.x.x.x. https://jenkins.puppetlabs.com/view/puppet-agent/view/master/view/puppet-agent/job/platform_puppet-agent_intn-van-sys_suite-daily-facter-master/155/SLAVE_LABEL=beaker,TEST_TARGET=ubuntu1004-64a/console 12:37:46 Test Case tests/facts/ubuntu.rb reported: # Add Comment
Jira (PUP-2316) Attributes attribute will not accept a single value for the User resource in AIX
Title: Message Title John Duarte commented on PUP-2316 Re: Attributes attribute will not accept a single value for the User resource in AIX Kylo Ginsberg, do we need release notes for this issue? 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-2316) Attributes attribute will not accept a single value for the User resource in AIX
Title: Message Title John Duarte commented on PUP-2316 Re: Attributes attribute will not accept a single value for the User resource in AIX Manually validated on AIX 6.1 using puppet at SHA 5e4da09. Install puppet from source tarballs Install Ruby Set up working directory mkdir pup6228 cd pup6228 Download rpm dependencies curl -O http://www.oss4aix.org/download/RPMS/ruby/ruby-2.0.0.353-1.aix5.1.ppc.rpm curl -O http://www.oss4aix.org/download/RPMS/gdbm/gdbm-1.11-1.aix5.1.ppc.rpm curl -O http://www.oss4aix.org/download/RPMS/libyaml/libyaml-0.1.6-1.aix5.1.ppc.rpm curl -O http://www.oss4aix.org/download/RPMS/openssl/openssl-1.0.1p-1.aix5.1.ppc.rpm curl -O http://www.oss4aix.org/download/RPMS/readline/readline-6.3-5.aix5.1.ppc.rpm curl -O http://www.oss4aix.org/download/RPMS/zlib/zlib-1.2.8-1.aix5
Jira (PUP-2316) Attributes attribute will not accept a single value for the User resource in AIX
Title: Message Title John Duarte updated an issue Puppet / PUP-2316 Attributes attribute will not accept a single value for the User resource in AIX Change By: John Duarte 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-6520) Determine whether there's any use case for a global lookup level
Title: Message Title Nicholas Fagerlund commented on PUP-6520 Re: Determine whether there's any use case for a global lookup level Ah, interesting. Yeah, I think I might agree? Since you don't have an ENC-per-environment, it's kind of incorrect to include it in the environment hierarchy. A default layer is also an interesting concept, and I have no idea what I think of that yet. 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-2868) Move how to setup and run PuppetDB unit tests
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2868 Move how to setup and run PuppetDB unit tests Change By: Ryan Senior Sprint: 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 (PDB-2885) structured fact matching/indexing for inventory endpoint
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2885 structured fact matching/indexing for inventory endpoint Change By: Ryan Senior Sprint: 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 (PDB-2886) projection for resources (parameters) and inventory(facts, trusted)
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2886 projection for resources (parameters) and inventory(facts, trusted) Change By: Ryan Senior Sprint: 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 (PDB-2869) puppet-client-tools 1.1.0 2016-07-20 Release
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-2869 puppet-client-tools 1.1.0 2016-07-20 Release Change By: Ryan Senior Sprint: 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 (PUP-5406) Address race conditions when stopping puppet
Title: Message Title Nick Walker commented on PUP-5406 Re: Address race conditions when stopping puppet calling a dup of PE-14459 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-6520) Determine whether there's any use case for a global lookup level
Title: Message Title Henrik Lindberg commented on PUP-6520 Re: Determine whether there's any use case for a global lookup level There has been a lengthy discussion about the role of data configuration and the ENC that relates to this topic. My take on that discussion was that it would be of value to specify: a global layer that overrides everything else - the content to come from a hierarchy that the ENC provided data is part of a lowest default layer that kicks in if no other layer have provided a value, again, the ENC may want to provide these This can also be achieved with an environment based hierarchy where ENC would be involved as a data provider. There is however no feature that allows configuration of a default level that has lower priority than module provided data. In the earlier discussion there was a concern that if the environment's "lookup.conf" defined where ENC data kicked in, then there would be a lack of central control over if the ENC is involved as intended or not. I am not saying that these additional layers are absolutely needed, and it is great to take this topic to a wider audience and drive it to conclusion. 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-5479) segfault with augeas type when changes attribute is too long
Title: Message Title David Lutterkort commented on PUP-5479 Re: segfault with augeas type when changes attribute is too long Just for the record: the upstream fix is in Augeas 1.5.0, released 2016-05-11 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-6523) Validate Resource Attribute data type
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6523 Validate Resource Attribute data type Issue Type: Improvement Assignee: Unassigned Created: 2016/07/19 5:45 AM Priority: Normal Reporter: Henrik Lindberg The Pcore Resource Type Generator tool generates data type information for some attributes, and in PUP-6522 (and PUP-6521) any data type information associated with a Parm will also be picked up and added to the Pcore description of a Param. In this ticket, the data type information is used during compilation to validate the values of resource attributes. This is somewhat complex as the final validation cannot be made until default values have also been evaluated (done late). Add Comment
Jira (PUP-6522) Make the pcore resource type generator pick up param data type from PUP-6521
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6522 Make the pcore resource type generator pick up param data type from PUP-6521 Issue Type: Bug Assignee: Unassigned Created: 2016/07/19 5:35 AM Priority: Normal Reporter: Henrik Lindberg In PUP-6521 the ability to define the Puppet Type System data type for a Parm (or Property) in a Resource Type. This information should be picked up by the generator tool to make it possible to make better validation at catalog compilation time. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-6521) Add the ability to describe Data Type for a Resource Param
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6521 Add the ability to describe Data Type for a Resource Param Issue Type: Bug Assignee: Unassigned Created: 2016/07/19 5:34 AM Priority: Normal Reporter: Henrik Lindberg It is of value to use the Puppet Type system to define the data type of a Param (or Property). This information can be used to validate given values both when compiling and when applying a catalog. Add Comment This message was sent by Atlassian JIRA (v6.4.13#64028-sha1:b7939e9)
Jira (PUP-5949) Update loaders to load pcore in place of ruby resource types when compiling
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5949 Update loaders to load pcore in place of ruby resource types when compiling Change By: Henrik Lindberg Acceptance Criteria: If a file is found under /.resource_types with the name of a resource type the following should happen:* A Ruby based Puppet::Type Class with the same name must not be loaded into the Ruby Runtime* A Pcore based implementation should instead be used* The catalog should have the exact same content as if the Ruby Puppet::Type implementation was used.* The requirement that Puppet::Type implementation must not be loaded is relaxed for the resource types built into Puppet (as some of them are loaded during the settings apply phase). It is allowed to also have a Pcore representation of those types for testing purposes. 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-5949) Update loaders to load pcore in place of ruby resource types when compiling
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5949 Update loaders to load pcore in place of ruby resource types when compiling Change By: Henrik Lindberg Scope Change Reason: next on env isolation work Story Points: 2 Sprint: Language 2016-07-27 Fix Version/s: PUP 4.6.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-5949) Update loaders to load pcore in place of ruby resource types when compiling
Title: Message Title Henrik Lindberg assigned an issue to Thomas Hallgren Puppet / PUP-5949 Update loaders to load pcore in place of ruby resource types when compiling Change By: Henrik Lindberg 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-6456) Detail tickets for environment isolation from exploration
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-6456 Detail tickets for environment isolation from exploration 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-6512) Change hiera.yaml (v4) to lookup.conf
Title: Message Title Henrik Lindberg commented on PUP-6512 Re: Change hiera.yaml (v4) to lookup.conf The version field is worth having going forward as it states the expected semantics of what the user have entered. Without it we make it difficult to make changes in the future. I think it should stay at 4 as it would be too confusing to "go back in time" and then later again possibly finding a version 4, now being a much later version. 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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Karel Brezina commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed ping 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-3042) If a catalog has a dependency cycle, it does not count as failed
Title: Message Title Karel Brezina commented on PUP-3042 Re: If a catalog has a dependency cycle, it does not count as failed I reopened this ticket and closed PE-5396 because the problem needs to be solved in Puppet. PE-5396 still contains some valuable comments. 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.