Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Karel Brezina commented on PDB-1472 Re: [Performance] Improvements for paged results Thanks Wyatt Alt for taking your time. I'm glad that you found the strange behavior even on your machine. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1485) Align url-prefix in foss to align with pe-puppetdb
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1485 Align url-prefix in foss to align with pe-puppetdb Issue Type: Task Assignee: Unassigned Created: 2015/05/06 3:08 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber We need to figure out what we want to do with the main url-prefix, right now pe-puppetdb uses /pdb for our API, and foss uses / ... this breaks the dashboard in PE by using this, I figure we should do one (or more) of the following: a) Make the dashboard follow the URL-prefix properly b) Change the default url-prefix to align for both shipped packages c) Consider using web-routing for these decisions in config for say FOSS, in favour of the old url-prefix potentially? This way there is one place to configure each service. Add Comment
Jira (PDB-1486) Rename /pe & /sync endpoints to something more puppetdb specific
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1486 Rename /pe & /sync endpoints to something more puppetdb specific Issue Type: Task Assignee: Unassigned Created: 2015/05/06 3:13 AM Fix Versions: PDB 3.0.0 Priority: Normal Reporter: Kenneth Barber The /pe & /sync endpoint could probably do with some uniqueness across applications in case we wish to later host other applications in the same JVM. Add Comment
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title
Peter Souter updated an issue
Puppet / PUP-4045
Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Change By:
Peter Souter
Using a slightly modified version of the code from "Pro Puppet" I am getting the following error: {code} Jun 13 01:36:33 media puppet-agent[18196]: (/Stage[main]/Mysql::Config/File[mysql_data_dir]) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket {code} The file resource in mysql/manifests/config.pp is as follows: {code} file { "mysql_data_dir" :path => $mysql::params::data_directory,group => "mysql",owner => "mysql",recurse => true,require => File["my.cnf"],} {code} And for this particular $operatingsystem (Fedora) the value for $data_directory in mysql/manifests/params.pp is : {code} $data_directory = "/var/lib/mysql" {code} By default mysql on a Fedora system places its mysql.sock file in the data directory but it appears when a you try and change the permissions recursively, puppet doesn't know what to do with the socket file. I can place the socket file elsewhere as a work around but I believe that puppet needs to ignore socket files when changing permissions. {code} [root@media modules]# puppet --version2.6.8[root@media modules]# puppet master --version2.6.8 {code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe
Jira (PUP-4045) Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket
Title: Message Title Peter Souter commented on PUP-4045 Re: Failed to generate additional resources using 'eval_generate': Cannot manage files of type socket As someone who encountered this recently, and needed to use the workaround of adding the socket files to the `ignore` parameter, you can find out what files are sockets with `tree` easy enough: $ tree --inodes -F | grep = │ │ ├── [2458821] S_TCP= So I needed to add this to my code: ignore=> ['S_TCP'] Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4530) FreeBSD specific Service provider fix
Title: Message Title Matthew Seaman created an issue Puppet / PUP-4530 FreeBSD specific Service provider fix Issue Type: Bug Affects Versions: PUP 3.7.5, PUP 3.6.2 Assignee: Unassigned Attachments: puppet-3.7.5.patch Components: Platform Created: 2015/05/06 4:38 AM Environment: FreeBSD sys-puppet-1.adestra.com 10.1-RELEASE-p5 FreeBSD 10.1-RELEASE-p5 #0: Tue Jan 27 08:55:07 UTC 2015 r...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64 Priority: Normal Reporter: Matthew Seaman The Service provider for FreeBSD parses the output of 'service foo rcvar' to work out what the service name is. However for some services – only a very few – the output contains an optional 'descripti
Jira (FACT-956) Update puppet-agent#master to build facter#master, remove cfacter
Title: Message Title Rob Reynolds commented on FACT-956 Re: Update puppet-agent#master to build facter#master, remove cfacter Merged into master at a32d7ecd Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1315) Add sync information to metrics
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1315 Add sync information to metrics Change By: Ryan Senior Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1313) Clojure network/node failure tests for single datacenter HA topology
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1313 Clojure network/node failure tests for single datacenter HA topology Change By: Ryan Senior Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1312) When starting PDB, don’t service requests until after an initial sync completes
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1312 When starting PDB, don’t service requests until after an initial sync completes Change By: Ryan Senior Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1467) puppetdb module has ordering problem with read_database.ini
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1467 puppetdb module has ordering problem with read_database.ini Change By: Kenneth Barber Component/s: Module Affects Version/s: PDB module-4.2.1 Sprint: PuppetDB 2015-05-06 Story Points: 0 Scope Change Reason: Module PR Scope Change Category: Found Fix Version/s: PDB module-4.3.0 Add Comment
Jira (PDB-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1469 puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package Change By: Kenneth Barber Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilati
Title: Message Title Kenneth Barber commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation. And to add more to this, by disabling trusted you're just masking the cache miss. If the master gets a cache miss, it will try to query PuppetDB for facts instead which is not desirable, so even if we fix this, we're then left with a gaping problem that users won't see until they are hours deep into an investigation. So while our use of trusted creates a confusing error message, its really surfacing a deeper issue, in that cache misses create unpredictable outcomes and do not warn the user properly. Just to be clear in case my previous points on this are vague, we have no set of actions on this today ... nor is a real next set of steps set out. Its been suggested to us to change this behaviour and to not use 'trusted' which is certainly possible, but still - there is a bigger bug behind it and I don't think thats necessarily the full correct answer (although its a cheap way to get rid of the error I suppose . I'd be happy to have a chat to people about this if we have the time, it feels like we need a cross-team solution rather than 'just fix it on the pdb side' ... perhaps I haven't been clear on making my point - happy to clarify via a chat if required. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1484) Memory leak when 'replace facts' failing
Title: Message Title Kenneth Barber commented on PDB-1484 Re: Memory leak when 'replace facts' failing Simon Oxwell we can control the prepared-statement cache by adding a configuration option. I believe now its hard-coded to 1000 items, but since we have quite a few dynamic queries this can quickly get large. I wouldn't have expected 500 MB though, I've seen 50 MB before. Do you have a hprof dump that we can look at for this? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1472) [Performance] Improvements for paged results
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1472 [Performance] Improvements for paged results Change By: Kenneth Barber Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilati
Title: Message Title Charlie Sharpsteen commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation. I think the correct answer is to separate the "trusted" data from the fact data on the PDB side. The reason being is that these two datasets are separate attributes of the Node object, are never mixed by the compiler and always exist as distinct entities. During compilation, there are two top-scope datasets: $::trusted and $::facts, and $::facts['trusted'] is undefined. Now, this does also lead to a question for the Puppet side: if trusted data is coming from PDB or a cached Node object, instead of a live Node request, is it still "trusted"? Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-949) Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilati
Title: Message Title Kenneth Barber commented on PDB-949 Re: Retrieving facts that have had 'trusted' facts injected into them causes a 400 "Attempt to assign to a reserved variable name: 'trusted' on node" failure during Puppet catalog compilation. Charlie Sharpsteen I think perhaps you're missing the subtlety of this larger problem, or I'm not describing it very well. Ping me if you want when you're not busy, we can have a chat. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4528) Chaining arrows do not work as expected with "empty" resources
Title: Message Title Henrik Lindberg commented on PUP-4528 Re: Chaining arrows do not work as expected with "empty" resources This is a known issue - IIRC there should be a warning when this happens and using the future parser. On the one hand it does exactly what is expected - the statement becomes "depends on nothing", and "nothing depends on". Not sure if we want to change that. It could be made an error, or it could short circuit (just skip the empty part). The later could lead to other hard to detect problems. An error is probably preferable as there is really no real practical use of an empty set in the middle of a chain (nor at the beginning or end of a chain). Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-956) Update puppet-agent#master to build facter#master, remove cfacter
Title: Message Title Rob Reynolds commented on FACT-956 Re: Update puppet-agent#master to build facter#master, remove cfacter Puppet-Agent merged into master at 80ca92e Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4483) Add NotUndef type to the set of Puppet types
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4483 Add NotUndef type to the set of Puppet types Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4489) Add data_provider to module metadata
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4489 Add data_provider to module metadata Change By: Henrik Lindberg Fix Version/s: PUP 4.2.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-355) how to run rspec-puppet with data in modules
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-355 how to run rspec-puppet with data in modules Change By: Henrik Lindberg Sprint: Language 2015-06-10 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1487 Add producer_timestamp to store-report Change By: Russell Mull Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1487 Add producer_timestamp to store-report Change By: Russell Mull We're currently using start_time, but it turns out that comes from the agent. After adding this, use it in the stale-nodes query. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Russell Mull created an issue PuppetDB / PDB-1487 Add producer_timestamp to store-report Issue Type: New Feature Assignee: Unassigned Created: 2015/05/06 7:57 AM Priority: Normal Reporter: Russell Mull We're currently using start_time, but it turns out that comes from the agent. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Russell Mull updated an issue PuppetDB / PDB-1487 Add producer_timestamp to store-report Change By: Russell Mull Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1311) Run sync on an internal timer, with configuration
Title: Message Title Rob Browning assigned an issue to Unassigned PuppetDB / PDB-1311 Run sync on an internal timer, with configuration Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1311) Run sync on an internal timer, with configuration
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-1311 Run sync on an internal timer, with configuration Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1483) PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1483 PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker Change By: AJ Roetker Sprint: PuppetDB 2015-05-06 Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1465 PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker Change By: AJ Roetker Sprint: PuppetDB 2015-05-06 Story Points: 1 Fix Version/s: PDB 3.0.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type
Title: Message Title Erik Dasher commented on PUP-3812 Re: Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type I'm reopening this because I think the above error, thrown while backing up a file via file_bucket, indicates that file_bucket is still treating binary data as UTF-8. I'm unsure if this should come through Triage, or come directly to QA for re-test. I'm choosing QA for now. Ping Jeremy Barlow Kurt Wall. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1483) PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1483 PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker Change By: AJ Roetker Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type
Title: Message Title Erik Dasher assigned an issue to QA Puppet / PUP-3812 Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type Change By: Erik Dasher Status: Reopened Ready for Test Assignee: QA Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1483) PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1483 PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1300) Make acceptance tests compatible with Puppet 4.0
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1300 Make acceptance tests compatible with Puppet 4.0 Change By: Steve Barlow Sprint: PuppetDB 2015-04-08, PuppetDB 2015-04-22, PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1465 PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1311) Run sync on an internal timer, with configuration
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1311 Run sync on an internal timer, with configuration Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1417) Announce HyperSQL Deprecation in 3.0.0
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1417 Announce HyperSQL Deprecation in 3.0.0 Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1289) Use producer_timestamp in GC query
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1289 Use producer_timestamp in GC query Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1450) Make automatic expiration work with sync
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1450 Make automatic expiration work with sync Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1482) PR (1378): (maint) allow ordering on non-extracted fields - wkalt
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1482 PR (1378): (maint) allow ordering on non-extracted fields - wkalt Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1310) Make the 'deactivate node' command commute.
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1310 Make the 'deactivate node' command commute. Change By: Steve Barlow Sprint: PuppetDB 2015-04-22, PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1467) puppetdb module has ordering problem with read_database.ini
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1467 puppetdb module has ordering problem with read_database.ini Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1447) remove late-project/basic-project and supply the functionality with the database.
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1447 remove late-project/basic-project and supply the functionality with the database. Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type
Title: Message Title Erik Dasher updated an issue Puppet / PUP-3812 Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type Change By: Erik Dasher Sprint: Server 2015-02-04, Server 2015-02-18 , Server Emerald 2015-05-13 Scope Change Reason: Bug regression discovered while making unrelated tests. Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1274) PR (1291): (maint) Change version policy to account for upgrades - senior
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1274 PR (1291): (maint) Change version policy to account for upgrades - senior Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: PR was merged months ago but not pushed through Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1444) PR (1358): (maint) Move late-project? from queries to columns - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1444 PR (1358): (maint) Move late-project? from queries to columns - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: PR submitted last sprint. Bookkeeping error Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3812) Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type
Title: Message Title Erik Dasher updated an issue Puppet / PUP-3812 Modify file_bucket_file API to use "application/octet-stream" instead of "text/plain" for Content-Type Change By: Erik Dasher The Puppet file_bucket_file API -- https://docs.puppetlabs.com/guides/rest_api.html#file-bucket -- requires a PUT request for a file to include a Content-Type of "text/plain". Puppet agent and file_bucket_file requests through the puppet filebucket CLI face also do not include a charset along with the Content-Type. Per various industry specifications -- see https://tools.ietf.org/html/rfc6657 in particular -- the default charset that a receiver should assume for this case would be either US-ASCII or ISO-8859-1. Puppet agent and filebucket CLI face requests, however, currently format the request body as raw "binary data". This is incompatible with the US-ASCII and ISO-8859-1 formats.In order to make the client's intentions about the request body encoding more clear, it would be better for clients to include a Content-Type of "application/octet-stream".[~josh] suggested that we could create a new format called ":binary", map that to "application/octet-stream", and change file_bucket/file to use it. Here are some relevant locations in the code where this could be done:https://github.com/puppetlabs/puppet/blob/master/lib/puppet/network/formats.rb#L65https://github.com/puppetlabs/puppet/blob/master/lib/puppet/file_bucket/file.rb#L16-L27Depending upon how we would do this, it may need to be done on a major version boundary. If the master were upgraded to accept "application/octet-stream" while still treating "text/plain" as "binary" initially, backward compatibility would be preserved. At some point, though, it may make sense to just break compatibility for "text/plain" on file_bucket/file altogether as the current implementation is ambiguous and not in alignment with industry standards. h3.QA:Risk Assessment: HighProbability: HighSeverity: Medium-High Add Comment This message was sent by Atlass
Jira (PDB-1474) PR (1375): (maint) fix /v4/catalogs/ so version isn't repeated in the href - wkalt
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1474 PR (1375): (maint) fix /v4/catalogs/ so version isn't repeated in the href - wkalt Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: found bug Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1456) PR (1366): (maint) Speed up storage.clj ` in (?,?,?...)` queries - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1456 PR (1366): (maint) Speed up storage.clj ` in (?,?,?...)` queries - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: discovered performance issue Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1470) PR (1374): (maint) make facts response streaming - wkalt
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1470 PR (1374): (maint) make facts response streaming - wkalt Change By: Steve Barlow Sprint: PuppetDB 2015-05-06 , PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1457) PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1457 PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1460) PR (1369): (maint) Upgrade clj-time ring-core and compojure deps - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1460 PR (1369): (maint) Upgrade clj-time ring-core and compojure deps - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Reason: Blocked console DB ticket Scope Change Category: Found Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1461) PR (1370): (maint) Allow any valid tk config to be used by benchmark tool - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1461 PR (1370): (maint) Allow any valid tk config to be used by benchmark tool - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1483) PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1483 PR (1380): (maint) Remove redirect to PuppetDB dashboard - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1465) PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1465 PR (1372): (maint) Detangle query-eng database and http streaming - ajroetker Change By: Steve Barlow Scrum Team: PuppetDB Scope Change Category: Adopted Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title
Davide Ferrari created an issue
Puppet / PUP-4531
create_resources() should deep merge the default parameters
Issue Type:
Bug
Assignee:
Unassigned
Created:
2015/05/06 8:27 AM
Priority:
Normal
Reporter:
Davide Ferrari
If you instance a resource with create_resources() and that resource takes a hash (call it $options) as a parameter, you should be able to define a default value for the keys inside the $options parameter.
define my_resource($options = {}) {
notify("param1 is ${options['param1'}")
# undef, it should be 'from defaults'
notify("param2 is ${options['param2'}")
Jira (PUP-1598) unhelpfull error message when parent directory is missing
Title: Message Title
Charlie Sharpsteen updated an issue
Puppet / PUP-1598
unhelpfull error message when parent directory is missing
Change By:
Charlie Sharpsteen
when creating a file, if the parent directory is missing a misleading error message is displayed, for example in the next case {{ /etc/munin/ }} was missing and I tried to create {{ /etc/munin/munin-node.conf }} {noformat} # puppetd --testnotice: Ignoring cacheinfo: Caching catalog at /var/lib/puppet/state/localconfig.yamlnotice: Starting catalog runerr: //Node[engine2]/engine/packages/Set_file[/etc/munin/munin-node.conf]/File[/etc/munin/munin-node.conf]/ensure: change from absent to file failed: Could not set file on ensure: No such file or directory - /etc/munin/munin-node.conf.puppettmp at /etc/puppet/manifests/site.pp:7notice: //Node[engine2]/engine/packages/Package[munin-node]: Dependency file[/etc/munin/munin-node.conf] has 1 failureswarning: //Node[engine2]/engine/packages/Package[munin-node]: Skipping because of failed dependenciesnotice: Finished catalog run in 3.95 seconds {noformat}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1598) unhelpfull error message when parent directory is missing
Title: Message Title
Charlie Sharpsteen commented on PUP-1598
Re: unhelpfull error message when parent directory is missing
Here's an updated test case for Puppet 3.8.0:
# mkdir -p /etc/puppetlabs/puppet/environments/production/modules/test/files
# touch /etc/puppetlabs/puppet/environments/production/modules/test/files/foo
# puppet apply -e 'file{"/tmp/doesnotexist/foo": ensure => file, source => "puppet:///modules/test/foo"}'
Notice: Compiled catalog for pe-380-master.puppetdebug.vlan in environment production in 0.17 seconds
Error: Could not set 'file' on ensure: No such file or directory - /tmp/doesnotexist/foo20150505-12857-st3w34.lock in 1
Error: Could not set 'file' on ensure: No such file or directory - /tmp/doesnotexist/foo20150505-12857-st3w34.lock in 1
Wrapped exception:
No such file or directory - /tmp/doesnotexist/foo20150505-12857-st3w34.lock
Jira (PUP-1598) unhelpfull error message when parent directory is missing
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1598 unhelpfull error message when parent directory is missing Change By: Charlie Sharpsteen Affects Version/s: PUP 3.8.0 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title
Davide Ferrari updated an issue
Puppet / PUP-4531
create_resources() should deep merge the default parameters
Change By:
Davide Ferrari
If you instance a resource with create_resources() and that resource takes a hash (call it $options) as a parameter, you should be able to define a default value for the keys inside the $options parameter.{code}define my_resource($options = {}) { notify ( { "param1 is ${options['param1'}" ) : } # undef, it should be 'from defaults' notify ( { "param2 is ${options['param2'}" ) : } # 'param2 is overwritten'}$default_resource_params = { 'options' => { 'param1' => 'from defaults', 'param2' => 'from defaults' }}$my_resources = { 'foo' => { 'options' => {'param2' => 'overwritten' } }}create_resources( 'my_resource', $my_resouces, $default_resource_params){code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-1598) unhelpfull error message when parent directory is missing
Title: Message Title Charlie Sharpsteen updated an issue Puppet / PUP-1598 unhelpfull error message when parent directory is missing Change By: Charlie Sharpsteen Scrum Team: Client Platform Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title
Davide Ferrari updated an issue
Puppet / PUP-4531
create_resources() should deep merge the default parameters
Change By:
Davide Ferrari
If you instance a resource with create_resources() and that resource takes a hash (call it $options) as a parameter, you should be able to define a default value for the keys inside the $options parameter.{code}define my_resource($options = {}) { notify{"param1 is ${options['param1' } ] ": } # undef, it should be 'from defaults' notify{"param2 is ${options['param2' } ] ": } # 'param2 is overwritten'}$default_resource_params = { 'options' => { 'param1' => 'from defaults', 'param2' => 'from defaults' }}$my_resources = { 'foo' => { 'options' => {'param2' => 'overwritten' } }}create_resources( 'my_resource', $my_resouces, $default_resource_params){code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title
Davide Ferrari updated an issue
Puppet / PUP-4531
create_resources() should deep merge the default parameters
Change By:
Davide Ferrari
If you instance a resource with create_resources() and that resource takes a hash (call it $options) as a parameter, you should be able to define a default value for the keys inside the $options parameter.{code}define my_resource($options = {}) { notify{"param1 is ${options['param1'] } ": } # undef, it should be 'from defaults' notify{"param2 is ${options['param2'] } ": } # 'param2 is overwritten'}$default_resource_params = { 'options' => { 'param1' => 'from defaults', 'param2' => 'from defaults' }}$my_resources = { 'foo' => { 'options' => {'param2' => 'overwritten' } }}create_resources( 'my_resource', $my_resouces, $default_resource_params){code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title
Davide Ferrari updated an issue
Puppet / PUP-4531
create_resources() should deep merge the default parameters
Change By:
Davide Ferrari
If you instance a resource with create_resources() and that resource takes a hash (call it $options) as a parameter, you should be able to define a default value for the keys inside the $options parameter.{code}define my_resource($options = {}) { notify{"param1 is ${options['param1']}": } # undef, it should be 'from defaults' notify{"param2 is ${options['param2']}": } # 'param2 is overwritten'}$default_resource_params = { 'options' => { 'param1' => 'from defaults', 'param2' => 'from defaults' }}$my_resources = { 'foo' => { 'options' => {'param2' => 'overwritten' } }}create_resources( 'my_resource', $ my_resouces my_resources , $default_resource_params){code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title
Davide Ferrari updated an issue
Puppet / PUP-4531
create_resources() should deep merge the default parameters
Change By:
Davide Ferrari
If you instance a resource with create_resources() and that resource takes a hash (call it $options) as a parameter, you should be able to define a default value for the keys inside the $options parameter.{code}define my_resource($options = {}) { notify{"param1 is ${options['param1']}": } # undef empty , it should be 'from defaults' notify{"param2 is ${options['param2']}": } # 'param2 is overwritten'}$default_resource_params = { 'options' => { 'param1' => 'from defaults', 'param2' => 'from defaults' }}$my_resources = { 'foo' => { 'options' => {'param2' => 'overwritten' } }}create_resources( 'my_resource', $my_resources, $default_resource_params){code} Output: {code}Notice: Compiled catalog for darkshadow.local in environment production in 0.03 secondsNotice: param1 isNotice: /Stage[main]/Main/My_resource[foo]/Notify[param1 is ]/message: defined 'message' as 'param1 is 'Notice: param2 is overwrittenNotice: /Stage[main]/Main/My_resource[foo]/Notify[param2 is overwritten]/message: defined 'message' as 'param2 is overwritten'{code}
Add Comment
This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegr
Jira (PDB-1488) Separate out connection pooling to be shared between projects
Title: Message Title Kenneth Barber created an issue PuppetDB / PDB-1488 Separate out connection pooling to be shared between projects Issue Type: Task Assignee: Unassigned Created: 2015/05/06 8:40 AM Priority: Normal Reporter: Kenneth Barber We want to find a cross-team shared solution for connection pooling. This might involve pulling out and sharing what the teams already have. Looks like this can be used by at least: Forge, PDB, Classifier, RBAC and perhaps the middleware? (not sure if they use a DB yet, but I know they talked about it in places). Other distractions we can consider: Cut to HikaruCP, as bonecp is retired Add Comment
Jira (PDB-1488) Separate out connection pooling to be shared between projects
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1488 Separate out connection pooling to be shared between projects Change By: Steve Barlow Scrum Team: PuppetDB Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1480) Rename the `pe-puppetdb-extensions` namespace from `puppetlabs.puppetdb` to `puppetlabs.pe_puppetdb_extenstions`
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1480 Rename the `pe-puppetdb-extensions` namespace from `puppetlabs.puppetdb` to `puppetlabs.pe_puppetdb_extenstions` Change By: AJ Roetker Sprint: PuppetDB 2015-05-20 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4531) create_resources() should deep merge the default parameters
Title: Message Title Davide Ferrari updated an issue Puppet / PUP-4531 create_resources() should deep merge the default parameters Change By: Davide Ferrari Affects Version/s: PUP 3.7.5 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1485) Align url-prefix in foss to align with pe-puppetdb
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1485 Align url-prefix in foss to align with pe-puppetdb Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1486) Rename /pe & /sync endpoints to something more puppetdb specific
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1486 Rename /pe & /sync endpoints to something more puppetdb specific Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1269) "Extractable only" fields are not supported in the query_eng/engine.clj
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1269 "Extractable only" fields are not supported in the query_eng/engine.clj Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1487) Add producer_timestamp to store-report
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1487 Add producer_timestamp to store-report Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1315) Add sync information to metrics
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1315 Add sync information to metrics Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1313) Clojure network/node failure tests for single datacenter HA topology
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1313 Clojure network/node failure tests for single datacenter HA topology Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1312) When starting PDB, don’t service requests until after an initial sync completes
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1312 When starting PDB, don’t service requests until after an initial sync completes Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1314) Add a sync event log file
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1314 Add a sync event log file Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1479) Mark aggregate-event-counts & event-counts API docs for removal in the future
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1479 Mark aggregate-event-counts & event-counts API docs for removal in the future Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1292) puppetdb api docs should include concrete examples
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1292 puppetdb api docs should include concrete examples Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1443) `edges` schema lacks proper foreign key constrains on `source` and `target` fields
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1443 `edges` schema lacks proper foreign key constrains on `source` and `target` fields Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1445) Always remove pe-* in packer scripts; generate all new AMIs
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1445 Always remove pe-* in packer scripts; generate all new AMIs Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1462) vector-valued facts cause gc churn on update
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1462 vector-valued facts cause gc churn on update Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-7) investigate moving puppetdb acceptance testing to use vsphere
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-7 investigate moving puppetdb acceptance testing to use vsphere Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1468) Maven keeps caching the old puppetdb during during ezbake builds
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1468 Maven keeps caching the old puppetdb during during ezbake builds Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1262) Update beaker and PuppetDB (config) to support c4.large and t2.medium instances
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1262 Update beaker and PuppetDB (config) to support c4.large and t2.medium instances Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1119) Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1119 Upon 3.0 release, edit config_file_puppetdb.markdown in puppet-docs repo Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1294) Add indices to foreign key columns
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1294 Add indices to foreign key columns Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1469) puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1469 puppetdb-terminus-2.3.3-1.el6 cannot find rubygems-json package Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1473) firm up behavior around empty lists vs 404s for nonexistent data
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1473 firm up behavior around empty lists vs 404s for nonexistent data Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1091) factsets does not support include-total when paired with a query
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1091 factsets does not support include-total when paired with a query Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1358) Module: Testing module against Puppet 4
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1358 Module: Testing module against Puppet 4 Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1322) fix nrepl.markdown so the repl example works when pasted
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1322 fix nrepl.markdown so the repl example works when pasted Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1033) Ezbake: fix downstream, make sure they can build our packages in an ezbake world
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1033 Ezbake: fix downstream, make sure they can build our packages in an ezbake world Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1035) Our module won't work with PDB 3.0.0 once released, as it has a new module package name
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1035 Our module won't work with PDB 3.0.0 once released, as it has a new module package name Change By: Steve Barlow Sprint: PuppetDB 2015-01-28, PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1455) Accommodate AIO (paths, etc.)
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1455 Accommodate AIO (paths, etc.) Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1350) update README.markdown to mention new API endpoints
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1350 update README.markdown to mention new API endpoints Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1453) handle comparison queries with non-numerics
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1453 handle comparison queries with non-numerics Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1442) consider changing aggregate-event-counts and event-counts to PE-only
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1442 consider changing aggregate-event-counts and event-counts to PE-only Change By: Steve Barlow Sprint: PuppetDB 2015- 05 06 - 20 03 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1488) Separate out connection pooling to be shared between projects
Title: Message Title Steve Barlow updated an issue PuppetDB / PDB-1488 Separate out connection pooling to be shared between projects Change By: Steve Barlow Story Points: 5 Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
