Jira (PUP-7361) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Ben Ford created an issue Puppet / PUP-7361 Apparently a Puppet Hiera error message points to a 404 Issue Type: Bug Assignee: Unassigned Created: 2017/03/15 10:55 PM Priority: Normal Reporter: Ben Ford The new Puppet version is pointing Hiera users to a 404 page. [21:58:28] This is an upgrade of PE 2016.5.1 -> 2017.1 [21:58:31] if it matters [21:58:53] 2017-03-16 04:01:12,660 - [Warning]: /etc/puppetlabs/enterprise/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 [21:58:55] (in /etc/puppetlabs/enterprise/hiera.yaml) [21:58:57] 2017-03-16 04:01:12,833 - [Warning]: The function 'hiera' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/4.9.4/reference/deprecated_language.html [21:58:59] (file & line not available) [21:59:02] And puppet 4.9.4 Add Comment
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Geoff Nichols Epic Status: To Do Done Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7360) Apparently a Puppet Hiera error message points to a 404
Title: Message Title Ben Ford created an issue Puppet / PUP-7360 Apparently a Puppet Hiera error message points to a 404 Issue Type: Bug Assignee: Unassigned Created: 2017/03/15 10:01 PM Priority: Normal Reporter: Ben Ford The new Puppet version is pointing Hiera users to a 404 page. [21:58:28] This is an upgrade of PE 2016.5.1 -> 2017.1 [21:58:31] if it matters [21:58:53] 2017-03-16 04:01:12,660 - [Warning]: /etc/puppetlabs/enterprise/hiera.yaml: Use of 'hiera.yaml' version 3 is deprecated. It should be converted to version 5 [21:58:55] (in /etc/puppetlabs/enterprise/hiera.yaml) [21:58:57] 2017-03-16 04:01:12,833 - [Warning]: The function 'hiera' is deprecated in favor of using 'lookup'. See https://docs.puppet.com/puppet/4.9.4/reference/deprecated_language.html [21:58:59] (file & line not available) [21:59:02] And puppet 4.9.4 Add Comment
Jira (PUP-7359) hiera5 doesn't interpolate in encrypted eyaml data
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7359 hiera5 doesn't interpolate in encrypted eyaml data Change By: Eric Thompson Summary: hiera5 can doesn 't interpolate hiera data into same in encrypted eyaml datasource data Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7359) hiera5 can't interpolate hiera data into same encrypted eyaml datasource
Title: Message Title
Eric Thompson commented on PUP-7359
Re: hiera5 can't interpolate hiera data into same encrypted eyaml datasource
this does work in a single {{ data_hash: yaml_data }} hierarchy
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7359) hiera5 can't interpolate hiera data into same encrypted eyaml datasource
Title: Message Title
Eric Thompson commented on PUP-7359
Re: hiera5 can't interpolate hiera data into same encrypted eyaml datasource
actually this is the same if i encrypt {{ % {lookup('enclair')}
}} into a value. enclair is not encrypted but is never interpolated
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-7359) hiera5 can't interpolate hiera data into same encrypted eyaml datasource
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7359 hiera5 can't interpolate hiera data into same encrypted eyaml datasource Change By: Eric Thompson Summary: hiera5 can't interpolate encrypted eyaml hiera data into same encrypted eyaml datasource Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7359) hiera5 can't interpolate encrypted eyaml data into same encrypted eyaml datasource
Title: Message Title Eric Thompson created an issue Puppet / PUP-7359 hiera5 can't interpolate encrypted eyaml data into same encrypted eyaml datasource Issue Type: Bug Affects Versions: PUP 4.9.4 Assignee: Thomas Hallgren Created: 2017/03/15 5:07 PM Priority: Normal Reporter: Eric Thompson [root@vi3cckc8ez3nwsu environments]# cat eyaml_backend2_1jvdmn6q/hieradata/common.yaml --- enclair: "i see you" test_hiera:
Jira (PUP-7136) Enable the tracing of lookup calls on a per-node basis
Title: Message Title Charlie Sharpsteen commented on PUP-7136 Re: Enable the tracing of lookup calls on a per-node basis If there is a noticeable performance hit, then we probably want to split explanations out to a separate parameter. The key feature is still the ability to enable explanations from the agent side by passing an additional flag to puppet agent -t and have the results show up on the server without twiddling any configuration bits on either side. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-747) Improve Solaris $::ipaddress accuracy
Title: Message Title Ryan Anderson commented on FACT-747 Re: Improve Solaris $::ipaddress accuracy Amen! Thanks Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1453) $ipaddress on openvz container returning 127.0.0.2
Title: Message Title Branan Riley commented on FACT-1453 Re: $ipaddress on openvz container returning 127.0.0.2 Can you provide the (redacted, if needed) output if `ip addr` and `ip route show`? I would not be surprised that the new networking resolver in Facter 3 has regressed on virtual network interfaces, since it's a complete rewrite and this stuff is complicated. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1528) Custom Ruby facts with additional resolutions instead replace core facts
Title: Message Title Branan Riley commented on FACT-1528 Re: Custom Ruby facts with additional resolutions instead replace core facts I think the general behavior of how custom implementation can override core facts is expected in facter 3, and is a result of the way Facter now works under the hood. Facter 3 resolvers are not tied to a given fact, like they are in Ruby facter - they collect many related facts, and populate them all at once. This is part of how we get such a huge performance improvement - we're not calling the same commands over and over for similar facts. Facter 2 and Ruby fact compatibility is implemented in this same way - all Ruby facts are essentially one Facter 3 "resolver". This means that they have no knowledge of core fact implementations, and, since they are run last, will happily overwrite them. An abridged pseudocode view of what Facter 3 is doing here: gather_all_filesystem_facts # Collect and set all the filesystem/disk facts with as few commands as possible gather_all_network_facts # Ditto for all the networking-related things gather_all_os_version_facts # Once more for all the OS-related things gather_all_ruby_custom_facts # your ruby OS fact overwrites a core fact value here! One of the things we've considered is trying to better expose this model in Facter's APIs, and make it clearer that custom facts are really running in a "virtual facter 2" within Facter 3's new model. All of that being said: It does appear that your confine isn't being respected, which I think is a bug Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-759) Can not get ec2 facter with non-root user on FreeBSD
Title: Message Title Branan Riley commented on FACT-759 Re: Can not get ec2 facter with non-root user on FreeBSD To be a bit clearer about what I think is going wrong here: Facter doesn't try to hit the EC2 metadata endpoint unless it thinks you're virtualized in a way that indicates EC2. If the virtual facts can't resolve, Facter won't bother hitting the EC2 endpoint. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3356) Use anti-join when eliminating inactive nodes from queries
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3356 Use anti-join when eliminating inactive nodes from queries Change By: Russell Mull Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3331) HA Replication of package inventory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3331 HA Replication of package inventory Change By: Russell Mull Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3283) Test coverage for conflicts during initial sync
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3283 Test coverage for conflicts during initial sync Change By: Russell Mull Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3310) [module PR] Fix duplicate resource errors for puppet service due to parse order
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3310 [module PR] Fix duplicate resource errors for puppet service due to parse order Change By: Russell Mull Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3306) Remove the vestigial clojure version of the PuppetDB CLI
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3306 Remove the vestigial clojure version of the PuppetDB CLI Change By: Russell Mull Sprint: Son of Hopper Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3325) Audit acceptance / integration tests for coverage gaps
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3325 Audit acceptance / integration tests for coverage gaps Change By: Russell Mull Sprint: Son of Hopper SE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3332) Implement querying support for package inventory
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-3332 Implement querying support for package inventory Change By: Russell Mull Sprint: Son of Hopper SE 2017-03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Maggie Dreyer commented on PUP-6715 Re: End-to-end POC for string externalization in Puppet The unfinished work which used to live in this epic has moved to PA-1024. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6643) Review and mark translatable strings
Title: Message Title Maggie Dreyer commented on PUP-6643 Re: Review and mark translatable strings This ticket has been superseded by several more granular ones (PUP-7042, PUP-7043, PUP-7109). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows 1) The specific issue is that Windows users cannot manage Ruby gems because our Ruby is placed first in the PATH on Windows. The most recent PR (earlier ones overreached) addresses this specific issue with a few lines of code. 2) The general issue is that package providers use 'which' to find the first command (for example, 'gem') specified in code by the provider. This 'first' model prevents managing 'multiple.' One suggested solution is for users to create a new provider that inherits from the base provider. Creating a new provider (for example: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/package/puppet_gem.rb) to specify commands for each instance of a provider seems excessive compared to being able to specify commands via a parameter. Here's a different/similar case (https://tickets.puppetlabs.com/browse/PUP-6895) where the 'first' model fails (albeit due to an unfortunate choice by a Perl developer to name a command 'pip') that could be resolved by being able to specify the full path of the command as a parameter. A command parameter could/would need to be used to establish a third level uniqueness key, as per https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/package.rb#L274 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1587) Need to add more --no-custom-facts tests
Title: Message Title Eric Delaney assigned an issue to Eric Delaney Facter / FACT-1587 Need to add more --no-custom-facts tests Change By: Eric Delaney Assignee: Eric Delaney Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1591) Add TestRail comments to connect test cases to the tests
Title: Message Title Eric Delaney created an issue Facter / FACT-1591 Add TestRail comments to connect test cases to the tests Issue Type: Task Affects Versions: FACT 3.4.2 Assignee: Eric Delaney Created: 2017/03/15 1:04 PM Priority: Normal Reporter: Eric Delaney Need to review the existing TestRail test cases for testing facter's command line options, and apply TestRail comments to connect the existing tests and TestRail cases. Add Comment
Jira (PDB-3332) Implement querying support for package inventory
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-3332 Implement querying support for package inventory Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7342) Create acceptance test for PUP-5058
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-7342 Create acceptance test for PUP-5058 Change By: Kurt Wall Assignee: Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3357) PuppetDB fails to update catalogs when rich data types are enabled
Title: Message Title
Charlie Sharpsteen created an issue
PuppetDB / PDB-3357
PuppetDB fails to update catalogs when rich data types are enabled
Issue Type:
Bug
Assignee:
Unassigned
Created:
2017/03/15 12:37 PM
Priority:
Normal
Reporter:
Charlie Sharpsteen
When a rich data type is added to a resource, the resulting catalog contains resources with ext_parameters keys. PuppetDB tries to work these new keys into an UPDATE operation on the catalog_resources table, which fails during statement preparation with a 'No hstore extension installed' error. No errors occur if the resource is initially stored with sensitive data.
The root cause for this behavior is the same as PDB-3322, which concerns the Sensitive data type.
Reproduction Case
Install PE 2017.1.0 on CentOS 7.
Add a file resource to the default node in /etc/puppetlabs/code/environments/production/manifests/site.pp that uses the binary_file function to manage content with binary data:
file{'/tmp/rich_data_test':
Jira (PUP-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Henrik Lindberg commented on PUP-3552 Re: Use application/json Content-Type/Accepts instead of PSON We can add on to the application/json, but that is also not standard. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7318) Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10
Title: Message Title Ethan Brown commented on PUP-7318 Re: Cherry-pick i18n + UTF-8 fixes from puppet#master to puppet#4.10 Reverted the 4283 commit in ed89d3b and pushed up to 4.10.x branch Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Henrik Lindberg commented on PUP-3552 Re: Use application/json Content-Type/Accepts instead of PSON If we instead move the "non json"-parts to the definition to the end point - how do we differ between different formats that are all in JSON (and the same for MsgPack) ? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title Josh Cooper commented on PUP-3552 Re: Use application/json Content-Type/Accepts instead of PSON AFAIK objects in the puppet ecosystem are always accessed via different REST endpoints, e.g. /puppet/v3/catalog vs /puppet/v3/report. So the caller already knows what type of object they are asking for. And this is pretty standard behavior, e.g. $ curl -s -i -H 'Accept: application/json' https://api.github.com/users/joshcooper | grep '^Content-Type' Content-Type: application/json; charset=utf-8 My concern with using application/vnd.puppet.pcore+json is that it's not standard and will be an issue for external integrations. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Ethan Brown commented on PUP-2937 Re: Windows: Unable to reference packages with UTF-8 Characters in their names Also - I went back through old agents and found that this was definitively fixed in Puppet 4.4.0 / agent 1.4.0. The fix was definitely not present in Puppet 4.3.2 / agent 1.3.6, which means that it was likely fixed in the set of tickets at https://tickets.puppetlabs.com/issues/?jql=project%20%3D%20Puppet%20and%20fixVersion%20%3D%20%22PUP%204.4.0%22 Most likely it was PUP-5728 that actually resolved this given manifests were not previously parsing properly as UTF-8 on Windows. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3552) Use application/json Content-Type/Accepts instead of PSON
Title: Message Title
Henrik Lindberg commented on PUP-3552
Re: Use application/json Content-Type/Accepts instead of PSON
The format on the wire is one of json or msgpack (etc) - that is basically what a reader would need to know to be able to read it. Naturally the reader must for most use cases know how the read data is organized - is this a "catalog" or a "report" and if so what is the version/representation of that. You may need to know that before reading the stream (you may be a reader that only understand an older version of say "catalog").
Following mime standard - there is no way to say "this is json + our thing" - it works the other way around - "this is our thing - it is in json". Hence my suggestion of:
application/vnd.puppet.pcore+{json|msgpack|...}
that would establish that this is a format that vendor puppet has defined and named, and then (after the +) what the encoding is (json, etc). Ultimately followed by additional mime arguments that defines things like UTF-8.
If we decide to not follow the rules of mime we can do what we want.
Sometimes - part of the format can be derived by context - i.e. "I am asking a particular endpoint for 'json'", the endpoint (URL) defines the rest (version, it is a catalog, etc). If we however want an actual mime type that defines this in a context free way, we would need the more elaborate description.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDB-3328) Implement terminus changes for package inventory
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-3328 Implement terminus changes for package inventory Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3204) Users and groups created mid-transaction are not found
Title: Message Title
John Duarte updated an issue
Puppet / PUP-3204
Users and groups created mid-transaction are not found
Change By:
John Duarte
I recently noticed the following: {code} Aug 23 18:09:35 extdns03 puppetdr987: [ID 702911 daemon.error] (//extdns03/common_foglight/foglight_agents_setup/Exec[/opt/foglight/script/setup.sh]) Failed to call refresh on Exec[/opt/foglight/script/setup.sh]: Invalid user: foglight {code} While I'm reasonably sure that the user did exist at that point. So after long and painful debugging I did the following: {code} extdns01# RUBYLIB=. irbirb(main):001:0> require 'puppet'=> trueirb(main):002:0> Puppet::Util.uid('boom')=> nil[ Now, in a different window, ran "adduser boom" ]irb(main):003:0> Puppet::Util.uid('boom')=> nilirb(main):004:0> {code} I guess puppet should flush the uid/gid cache on any user/group operation, or possibly even every time.
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols assigned an issue to Adam Bottchen Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Assignee: Adam Bottchen Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title John Duarte updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: John Duarte QA Risk Assessment: Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Acceptance Criteria: - Ability to opt-in to behavior where Puppet's vendored Ruby is not in the PATH. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Fix Version/s: PUP 6.0.0 Fix Version/s: PUP 5.y Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Sprint: Agent Accepted Grooming Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Ethan Brown Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title Ethan Brown updated an issue Puppet / PUP-2937 Windows: Unable to reference packages with UTF-8 Characters in their names Change By: Ethan Brown Sprint: Agent Grooming On 2017 - Deck 03-22 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-2937) Windows: Unable to reference packages with UTF-8 Characters in their names
Title: Message Title
Ethan Brown commented on PUP-2937
Re: Windows: Unable to reference packages with UTF-8 Characters in their names
I just verified this has been fixed - probably as a result of
PUP-3837
.
Note that the original manifest example was slightly incorrect, and should include Windows in the title of the package like:
package { 'Windows Azure Libraries for .NET – v2.3':
ensure => '2.3.0424.070',
source => "C:/WindowsAzureLibsForNet-x64.msi"
}
When I ran puppet resource package after installation, with codepage 437 as the active codepage, I got:
package { 'Windows Azure Libraries for .NET - v2.3':
ensure => '2.3.0424.070',
}
Re-running puppet apply:
Jira (FACT-1573) Verify, reconcile, and document Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and document Windows OS version facts Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1573) Verify, reconcile, and document Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and document Windows OS version facts Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1573) Verify, reconcile, and document Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and document Windows OS version facts Change By: Geoff Nichols Summary: Verify, reconcile, and correct document Windows OS version facts Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6040) "puppet facts" outputs indirector object instead of simple fact list
Title: Message Title Martin Alfke commented on PUP-6040 Re: "puppet facts" outputs indirector object instead of simple fact list +1 for dotted notation +1 for using similar options (puppet facts --flat) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7041) Add Japanese Windows to Puppet acceptance testing matrices
Title: Message Title Ethan Brown commented on PUP-7041 Re: Add Japanese Windows to Puppet acceptance testing matrices LTS is not "officially" Japanese compatible... yet. At the point that LTS becomes a 4.y agent, we might want to change things - but for now, master and stable are sufficient. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7041) Add Japanese Windows to Puppet acceptance testing matrices
Title: Message Title John O'Connor commented on PUP-7041 Re: Add Japanese Windows to Puppet acceptance testing matrices Ethan Brown I think LTS has entered the frame since this ticket came to life - do we want to include this, or just test on master and stable? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7358) acceptance: add test of 'puppet module list' while in code page 65001
Title: Message Title John Duarte updated an issue Puppet / PUP-7358 acceptance: add test of 'puppet module list' while in code page 65001 Change By: John Duarte QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7070) Remove stacktrace property of http error response object
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7070 Remove stacktrace property of http error response object Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7070) Remove stacktrace property of http error response object
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7070 Remove stacktrace property of http error response object Change By: Geoff Nichols Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7070) Remove stacktrace property of http error response object
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7070 Remove stacktrace property of http error response object Change By: Geoff Nichols Acceptance Criteria: - Puppet's http error response object no longer includes stacktrace property.- Puppet 5 API schema updated to reflect change. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7358) acceptance: add test of 'puppet module list' while in code page 65001
Title: Message Title John Duarte created an issue Puppet / PUP-7358 acceptance: add test of 'puppet module list' while in code page 65001 Issue Type: Sub-task Assignee: Unassigned Created: 2017/03/15 10:27 AM Priority: Normal Reporter: John Duarte Add acceptance test for PMT while in code page 65001 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Change By: Geoff Nichols Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Change By: Geoff Nichols Acceptance Criteria: Format of structured data output to console is same as the Puppet 4 implementation. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7268) SPIKE: Puppet::Util::Execution rewrite
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7268 SPIKE: Puppet::Util::Execution rewrite Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7268) SPIKE: Puppet::Util::Execution rewrite
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7268 SPIKE: Puppet::Util::Execution rewrite Change By: Geoff Nichols Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7268) SPIKE: Puppet::Util::Execution rewrite
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7268 SPIKE: Puppet::Util::Execution rewrite Change By: Geoff Nichols Acceptance Criteria: - Feature parity with current implementation.- Prototype and more complete scope defined for recommended implementation. - Reusability across components is a "nice to have". Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7257 Don't superfluously CGI encode facts facts_for_uploading Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7257 Don't superfluously CGI encode facts facts_for_uploading Change By: Geoff Nichols Story Points: 2 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-3043) Recursive File resources operating on large directory trees are inefficient
Title: Message Title Emerson Prado commented on PUP-3043 Re: Recursive File resources operating on large directory trees are inefficient If I understood the source file `lib/puppet/type/file.rb`, it seems to me that the cause is that file recursion and management are done separately. So, if we have a huge tree with thousands of files, the agent will first generate a list of all subdirs and files, then apply the resource parameters to each one of them. So, in practice, each subdir and file will be processed as a distinct resource - and generate a distinct log entry, which may be what eats your CPU after the last chown. DISCLAIMER: I know squat of Ruby, so I can be plain wrong in my assertions above. A more efficient approach, in my opinion, would be to use the OS recursion capabilities when querying and applying configurations (like `chown -R`). But this would require a thorough revamping of the Ruby module, and maybe new modules like `puppet/type/file/owner_recursive`, etc. Don't know how worthy would it be. An alternative: a feature request against stdlib for a type or function specialized in directory recursive processing. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7257 Don't superfluously CGI encode facts facts_for_uploading Change By: Geoff Nichols Acceptance Criteria: - Facts sent as JSON to Puppet 5 masters.- Facts sent as PSON to older masters.- Content type for POST is application/json Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7356) acceptance: add tests for empty/conflicting clientbucket behavior
Title: Message Title John Duarte updated an issue Puppet / PUP-7356 acceptance: add tests for empty/conflicting clientbucket behavior Change By: John Duarte QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Alex P commented on PUP-7351 Re: PUP 4.9.4 `deep merge` hiera interpolation still doesn't work also, if you still want to see debug logs, is there any email I can send them to? It has quite a bit of real data and don't want to attach it here. Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7357) acceptance: add tests ensuring JSON prefered over PSON
Title: Message Title John Duarte assigned an issue to qa Puppet / PUP-7357 acceptance: add tests ensuring JSON prefered over PSON Change By: John Duarte Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7357) acceptance: add tests ensuring JSON prefered over PSON
Title: Message Title John Duarte updated an issue Puppet / PUP-7357 acceptance: add tests ensuring JSON prefered over PSON Change By: John Duarte QA Risk Assessment: Needs Assessment Automate Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7357) acceptance: add tests ensuring JSON prefered over PSON
Title: Message Title John Duarte created an issue Puppet / PUP-7357 acceptance: add tests ensuring JSON prefered over PSON Issue Type: Sub-task Assignee: Unassigned Created: 2017/03/15 10:15 AM Priority: Normal Reporter: John Duarte Add acceptance tests to puppet to validate that JSON is preferred over PSON. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7255 SPIKE: Enable newer agents to talk to older masters Change By: Geoff Nichols Sprint: Agent Grooming 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7255 SPIKE: Enable newer agents to talk to older masters Change By: Geoff Nichols Acceptance Criteria: Decision made on implementation to be used in Puppet 5.0 and broadcast to puppet-dev. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7257 Don't superfluously CGI encode facts facts_for_uploading Change By: Josh Cooper Story Points: 2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title
Alex P commented on PUP-7351
Re: PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
another two errors we're getting is with alias / variable usage. Here is the configuration:
If I do it as it was advised by Eric Thompson in
PUP-7289
, i.e.
sudo::configs:
"%{dev_username}":
'content' : "%{dev_username} ALL=(ALL:ALL) APACHECTL, NGINX, !SU, !SHELLS, REBOOT, APACHECONF, POSTGRESQL, COMPOSER
'ensure' : 'present'
then there is the following error: Error: Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: No title provided and "Sudo::Conf[]" is not a valid resource reference on node ...
If I stick with my config, i.e. via `% {alias('dev_username')}
`, then there is another one: {{ Could not retrieve catalog from remote server: Error 500 on SERVER: Server Error: Evaluation Error: Error while evaluating a Function Call, Lookup of key 'dev_username' failed: 'alias' interpolation is only permitted if the _expression_ is equal to the entire string at /etc/puppetlabs/code/modules/sudo/manifests/configs.pp:20:14 on node ...}}
dev_username is a one-word string.
Add Comment
Jira (PUP-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Ethan Brown commented on PUP-7255 Re: SPIKE: Enable newer agents to talk to older masters OPTIONS is the way to go IMHO - it's used for pre-flight checks during CORS requests, and is a pretty standard HTTP concept. https://developer.mozilla.org/en-US/docs/Web/HTTP/Methods/OPTIONS Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7356) acceptance: add tests for empty/conflicting clientbucket behavior
Title: Message Title John Duarte created an issue Puppet / PUP-7356 acceptance: add tests for empty/conflicting clientbucket behavior Issue Type: Sub-task Assignee: John Duarte Created: 2017/03/15 10:08 AM Priority: Normal Reporter: John Duarte Add acceptance test(s) to validate clientbucket contents that are empty or contain identical content do not produce a filebucket error. Ref: PUP-1334 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Alex P updated an issue Puppet / PUP-7351 PUP 4.9.4 `deep merge` hiera interpolation still doesn't work Change By: Alex P Attachment: screenshot-2.png Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7255 SPIKE: Enable newer agents to talk to older masters Change By: Josh Cooper Story Points: 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-801) Facter does not see secondary IP's added with ip addr
Title: Message Title Branan Riley commented on FACT-801 Re: Facter does not see secondary IP's added with ip addr I'm going to check if this still applies to Facter 3 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Alex P commented on PUP-7351 Re: PUP 4.9.4 `deep merge` hiera interpolation still doesn't work ok, after switching to debug preparing logs for you, was able to trace at least one misconfiguration that was overseen when discussing last time. The site manifest was as follows: include lookup(... does help a bit (i.e. result is different but still an error). Believe it has to be updated here to reflect that as well: https://docs.puppet.com/puppet/4.9/hiera_use_function.html Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7351) PUP 4.9.4 `deep merge` hiera interpolation still doesn't work
Title: Message Title Alex P updated an issue Puppet / PUP-7351 PUP 4.9.4 `deep merge` hiera interpolation still doesn't work Change By: Alex P Attachment: screenshot-1.png Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-801) Facter does not see secondary IP's added with ip addr
Title: Message Title Branan Riley assigned an issue to Branan Riley Facter / FACT-801 Facter does not see secondary IP's added with ip addr Change By: Branan Riley Assignee: Eric Sorenson Branan Riley Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-801) Facter does not see secondary IP's added with ip addr
Title: Message Title Branan Riley updated an issue Facter / FACT-801 Facter does not see secondary IP's added with ip addr Change By: Branan Riley Labels: needs_repro Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-198) Rename uniqueid hostid
Title: Message Title Branan Riley commented on FACT-198 Re: Rename uniqueid hostid With Puppet Five and a probable Facter Four approaching, now is a good time for us to think about tackling this. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-636) GCE fact retrieval should ignore proxy setting
Title: Message Title Branan Riley commented on FACT-636 Re: GCE fact retrieval should ignore proxy setting This is also potentially still a problem in Facter 3, as I don't think we explicitly dealt with proxy settings in it. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Geoff Nichols Sprint: Client 2016-09-07 , Agent 5 Ready for Engineering Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7331) "Unable to set ownership" error with logdest on agents
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7331 "Unable to set ownership" error with logdest on agents Change By: Geoff Nichols Sprint: Client 2016-09-07 , Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7355) acceptance: hiera eyaml
Title: Message Title Eric Thompson created an issue Puppet / PUP-7355 acceptance: hiera eyaml Issue Type: Task Assignee: Eric Thompson Components: QA Created: 2017/03/15 9:46 AM Priority: Normal Reporter: Eric Thompson because of the regressions acceptance seems appropriate here. we'll need a test for hiera3 and hiera5 config Add Comment This message was sent by Atlassian JIRA
Jira (PUP-7210) not english Windows: Puppet agent on windows dont get server from config
Title: Message Title Anton Patsev commented on PUP-7210 Re: not english Windows: Puppet agent on windows dont get server from config I run from cmd.. Need should be run "Puppet agent on demand" Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7255) SPIKE: Enable newer agents to talk to older masters
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7255 SPIKE: Enable newer agents to talk to older masters Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7268) SPIKE: Puppet::Util::Execution rewrite
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7268 SPIKE: Puppet::Util::Execution rewrite Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7070) Remove stacktrace property of http error response object
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7070 Remove stacktrace property of http error response object Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7257) Don't superfluously CGI encode facts facts_for_uploading
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7257 Don't superfluously CGI encode facts facts_for_uploading Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1573) Verify, reconcile, and correct Windows OS version facts
Title: Message Title Geoff Nichols updated an issue Facter / FACT-1573 Verify, reconcile, and correct Windows OS version facts Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7256) Ensure console pretty printing maintains pre-JSON formatting
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7256 Ensure console pretty printing maintains pre-JSON formatting Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-1191) Puppet should not reset locale
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-1191 Puppet should not reset locale Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-6035) Puppet Throws Exception when Running Under Unicode Windows User
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6035 Puppet Throws Exception when Running Under Unicode Windows User Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7308) classes do not honor refresh events when running with tags
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7308 classes do not honor refresh events when running with tags Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7302) Puppet HTTP Node API: make fact_merge optional
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7302 Puppet HTTP Node API: make fact_merge optional Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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-7292) Allow to set password warning days for user type
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-7292 Allow to set password warning days for user type Change By: Geoff Nichols Sprint: Agent Grooming On-Deck Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- 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.
