Jira (PUP-6808) Global defaults do not override `undef` parameters
Title: Message Title Joshua Spence commented on PUP-6808 Re: Global defaults do not override `undef` parameters I can reproduce this on Puppet 4.7.0 as well 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-6808) Global defaults do not override `undef` parameters
Title: Message Title
Joshua Spence created an issue
Puppet / PUP-6808
Global defaults do not override `undef` parameters
Issue Type:
Bug
Assignee:
Unassigned
Components:
Language
Created:
2016/10/10 9:21 PM
Environment:
Puppet 3.8.6
Priority:
Normal
Reporter:
Joshua Spence
It seems that global defaults do not override parameters set to `undef`. This is a similar issue to
PUP-3587
, but applies to global defaults (e.g. `Exec { ... }
`) rather than default values defined on `define`s. This is best demonstrated by an example:
define foo($bar = undef) {
Jira (PUP-6764) Make CI job to add PO files to repo
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6764 Make CI job to add PO files to repo Change By: Geoff Nichols Labels: i18n 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-6763) Make CI job to update POT file
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6763 Make CI job to update POT file Change By: Geoff Nichols Labels: i18n 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-6762) SPIKE - How and when do we get PO files from Transifex?
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6762 SPIKE - How and when do we get PO files from Transifex? Change By: Geoff Nichols Labels: i18n 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-6761) SPIKE - Find a workflow for POT file generation
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6761 SPIKE - Find a workflow for POT file generation Change By: Geoff Nichols Labels: i18n 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-6807) referencing non-existant variable in custom function crashes puppetserver
Title: Message Title Justin Stoller moved an issue Puppet / PUP-6807 referencing non-existant variable in custom function crashes puppetserver Change By: Justin Stoller Affects Version/s: PE 2016.2.1 Component/s: Puppet Server Component/s: Puppet Server Key: PE PUP - 17527 6807 Project: Puppet Enterprise [Internal] 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
Jira (HI-538) Update beaker to 3.1.0 for MacOS Sierra testing
Title: Message Title Sean McDonald assigned an issue to Sean McDonald Hiera / HI-538 Update beaker to 3.1.0 for MacOS Sierra testing Change By: Sean McDonald Assignee: Sean McDonald 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 (HI-538) Update beaker to 3.1.0 for MacOS Sierra testing
Title: Message Title Sean McDonald created an issue Hiera / HI-538 Update beaker to 3.1.0 for MacOS Sierra testing Issue Type: Task Assignee: Sean McDonald Created: 2016/10/10 3:42 PM Priority: Normal Reporter: Sean McDonald Beaker 3.1.0 is required to run tests on MacOS sierra. With the intent to start testing packages we need to bump the beaker version in hiera Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-122) Strings doesn't handle puppet 3.x API syntax when newfunction is on a newline
Title: Message Title William Hopper updated an issue Puppet Strings / PDOC-122 Strings doesn't handle puppet 3.x API syntax when newfunction is on a newline Change By: William Hopper Sprint: PDS 2016-10-19 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-6806) Update beaker version to 3.1.0 to allow MacOS Sierra testing Support
Title: Message Title Sean McDonald created an issue Puppet / PUP-6806 Update beaker version to 3.1.0 to allow MacOS Sierra testing Support Issue Type: Task Assignee: Sean McDonald Created: 2016/10/10 3:24 PM Priority: Normal Reporter: Sean McDonald Bump beaker version inside the acceptance Gemfile to 3.1.0, which will allow us to test on the MacOS Sierra (10.12) Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (FACT-1516) Update facter tests to include check for Sierra Kernel version
Title: Message Title Sean McDonald updated an issue Facter / FACT-1516 Update facter tests to include check for Sierra Kernel version Change By: Sean McDonald Facter explicitly checks for Kernel version on specific versions of MacOS. Update the tests to allow a check to exist for MacOS Sierra (10.12) . This ticket should also cover work to bump the version of beaker to 3.1.0 to allow testing for MacOS Sierra 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-1516) Update facter tests to include check for Sierra Kernel version
Title: Message Title Sean McDonald created an issue Facter / FACT-1516 Update facter tests to include check for Sierra Kernel version Issue Type: Task Assignee: Sean McDonald Created: 2016/10/10 3:11 PM Priority: Normal Reporter: Sean McDonald Facter explicitly checks for Kernel version on specific versions of MacOS. Update the tests to allow a check to exist for MacOS Sierra (10.12) Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PDOC-122) Strings doesn't handle puppet 3.x API syntax when newfunction is on a newline
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-122
Strings doesn't handle puppet 3.x API syntax when newfunction is on a newline
Change By:
William Hopper
Acceptance Criteria:
The following function should be documented correctly by strings:{code}module Puppet::Parser::Functions newfunction(:testfunc, doc: <<-DOCthis function prints all the arguments it gets@param [Array] some arg_list Some args separated by spaces@return [undef] won't return anythingDOC) do |args|args.each do |arg| puts argend endend{code}
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-3093) do not log the first retry and do not use the term "L2"
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3093 do not log the first retry and do not use the term "L2" Issue Type: Improvement Assignee: Unassigned Created: 2016/10/10 2:34 PM Priority: Normal Reporter: Wyatt Alt I'm a bit concerned that production environments might see a lot of log spam related to retries due to transaction conflicts. Seems like we can probably get away with logging the retry after number 4 or something, given that they happen fast. Separately, I think the term "L2" is going to be unclear to uses because we don't document it and most people will associate it with the L2 cache. We should remove it from our log messages and maybe refer to it as "level 2" internally. Add Comment
Jira (PDOC-122) Strings doesn't handle puppet 3.x API syntax when newfunction is on a newline
Title: Message Title
William Hopper updated an issue
Puppet Strings / PDOC-122
Strings doesn't handle puppet 3.x API syntax when newfunction is on a newline
Change By:
William Hopper
Affects Version/s:
PDOC 0.99.0
Acceptance Criteria:
The following function should be documented correctly by strings:{code}module Puppet::Parser::Functions newfunction(:testfunc, doc: <<-DOCthis function prints all the arguments it gets@param [Array] some args separated by spaces@return [undef] won't return anythingDOC) do |args|args.each do |arg| puts argend endend{code}
Story Points:
2
Team:
Puppet Developer Support
Summary:
Strings doesn't properly handle multiple Custom Functions puppet 3.x API syntax when newfunction is on a newline
Fix Version/s:
PDOC 1.0.0
Add Comment
Jira (PDOC-122) Strings doesn't properly handle multiple Custom Functions
Title: Message Title William Hopper commented on PDOC-122 Re: Strings doesn't properly handle multiple Custom Functions Thanks for the report, Nick Miller. I was able to reproduce this and figure out what's going on. In all of our tests, we create 3.x functions like yours in the following way: Puppet::Parser::Functions::newfunction(:testfunc, doc: <<-DOC this function prints all the arguments it gets @param [Array] some args separated by spaces @return [undef] won't return anything DOC ) do |args| args.each do |arg| puts arg end end
Jira (PDOC-122) Strings doesn't properly handle multiple Custom Functions
Title: Message Title
Nick Miller updated an issue
Puppet Strings / PDOC-122
Strings doesn't properly handle multiple Custom Functions
Change By:
Nick Miller
When the input to strings has more than one function in ` {{ lib/puppet/parser/functions/* ` }} , the generated yard documentation only includes content from the first function it finds, alphabetically. It is also not possible to find the function documentation without going opening the file manually.Steps to reproduce:# Clone my [test repo ]( | https://github.com/jeefberkey/functest ) ] , which was generated with `puppet module generate` and using Puppet 3.8.7# {{bundle install}}# {{puppet strings generate}}# Open {{docs/index.html}} in a browser and look for the function documentation
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 (PDOC-122) Strings doesn't properly handle multiple Custom Functions
Title: Message Title
Nick Miller updated an issue
Puppet Strings / PDOC-122
Strings doesn't properly handle multiple Custom Functions
Change By:
Nick Miller
When the input to strings has more than one function in `lib/puppet/parser/functions/*`, the generated yard documentation only includes content from the first function it finds, alphabetically. It is also not possible to find the function documentation without going opening the file manually.Steps to reproduce:# Clone my [test repo](https://github.com/jeefberkey/functest), which was generated with `puppet module generate` and using Puppet 3.8.7# ` {{ bundle install ` }} # `puppet strings generate`# Open `docs/index.html` in a browser and look for the function documentation
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 (PDOC-122) Strings doesn't properly handle multiple Custom Functions
Title: Message Title
Nick Miller updated an issue
Puppet Strings / PDOC-122
Strings doesn't properly handle multiple Custom Functions
Change By:
Nick Miller
When the input to strings has more than one function in `lib/puppet/parser/functions/*`, the generated yard documentation only includes content from the first function it finds, alphabetically. It is also not possible to find the function documentation without going opening the file manually.Steps to reproduce:# Clone my [test repo](https://github.com/jeefberkey/functest), which was generated with `puppet module generate` and using Puppet 3.8.7# {{bundle install}}# ` {{ puppet strings generate ` }} # Open ` {{ docs/index.html ` }} in a browser and look for the function documentation
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-3058) Report not being stored in PuppetDB due to Unicode Error
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3058 Report not being stored in PuppetDB due to Unicode Error Change By: Wyatt Alt Labels: maintenance Story Points: 2 Team: Foundational Features Security: Internal Sprint: Hopper FF 2016-10-19 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,
Jira (PDB-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Labels: maintenance Team: Foundational Features 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-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Sprint: Hopper FF 2016-10-19 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-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt 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-6789) Prefer but don't require capabilities matching the node environment
Title: Message Title Alex Dreyer updated an issue Puppet / PUP-6789 Prefer but don't require capabilities matching the node environment Since PUP changes can take a while to get merged we should try to get a PR for this up soon. Change By: Alex Dreyer Sprint: FF 2016-10-19 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 (PDOC-122) Strings doesn't properly handle multiple Custom Functions
Title: Message Title Nick Miller created an issue Puppet Strings / PDOC-122 Strings doesn't properly handle multiple Custom Functions Issue Type: Bug Assignee: Unassigned Created: 2016/10/10 1:58 PM Priority: Normal Reporter: Nick Miller When the input to strings has more than one function in `lib/puppet/parser/functions/*`, the generated yard documentation only includes content from the first function it finds, alphabetically. It is also not possible to find the function documentation without going opening the file manually. Steps to reproduce: Clone my [test repo](https://github.com/jeefberkey/functest), which was generated with `puppet module generate` and using Puppet 3.8.7 `bundle install` `puppet strings generate` Open `docs/index.html` in a browser and look for the function documentation
Jira (PUP-6805) Services started during package resource application persist in agent's cgroup
Title: Message Title
Adam Bottchen created an issue
Puppet / PUP-6805
Services started during package resource application persist in agent's cgroup
Issue Type:
Improvement
Affects Versions:
PUP 4.5.3
Assignee:
Unassigned
Created:
2016/10/10 1:41 PM
Priority:
Normal
Reporter:
Adam Bottchen
When the Puppet agent service applies a catalog with a package resource that includes a post-install script, that script is executed in the Puppet agent's cgroup. Even if the Puppet agent is stopped, these processes continue to reside in that cgroup.
Those processes should be locked to a per-run cgroup instead, to prevent resource contention and leaky data.
Re-create steps:
Simple manifest to install the package and start the service:
package { '/tmp/gatekeeper-1.1.0-1.x86_64.rpm':
ensure => present,
Jira (PDOC-60) Strings skips docs for the log message functions
Title: Message Title William Hopper assigned an issue to Nicholas Fagerlund Puppet Strings / PDOC-60 Strings skips docs for the log message functions Change By: William Hopper Status: Resolved Closed 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 (PDOC-114) Go/no-go meeting (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-114 Re: Go/no-go meeting (PDOC 0.99.0) Lindsey Smith·11:43 AM: Gooo 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 (PDOC-113) Build and smoke test gem (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-113 Re: Build and smoke test gem (PDOC 0.99.0) FOSS puppet-agent latest: Verified on Centos 7 by running strings generate on the apache, concat and stdlib modules. Documentation was generated as expected in both HTML and JSON. PE 3.8: Verified on Centos 7 in the same way. 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-3064) PuppetDB chokes on enqueued reports going from 3.2.x to 4.2
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-3064 PuppetDB chokes on enqueued reports going from 3.2.x to 4.2 Change By: Wyatt Alt Assignee: Wyatt Alt 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 (PDOC-112) Tag the release (PDOC 0.99.0)
Title: Message Title William Hopper commented on PDOC-112 Re: Tag the release (PDOC 0.99.0) Tagged 0.99.0 at 7df4f9e87c91c5eb2711496eb6ae4eb2eb95e02e 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-3071) log a more helpful message when the old-style puppetdb.conf is used
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3071 log a more helpful message when the old-style puppetdb.conf is used Change By: Wyatt Alt Labels: maintenance Team: Foundational Features Sprint: SE FF 2016-10-19 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-3071) log a more helpful message when the old-style puppetdb.conf is used
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3071 log a more helpful message when the old-style puppetdb.conf is used Change By: Wyatt Alt 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 (PDB-3071) log a more helpful message when the old-style puppetdb.conf is used
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-3071 log a more helpful message when the old-style puppetdb.conf is used Change By: Wyatt Alt Assignee: Wyatt Alt 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-3071) log a more helpful message when the old-style puppetdb.conf is used
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-3071 log a more helpful message when the old-style puppetdb.conf is used Change By: Wyatt Alt Sprint: Hopper SE 2016-10-19 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-6511) Add support for lookup.conf (version 5)
Title: Message Title Thomas Hallgren commented on PUP-6511 Re: Add support for lookup.conf (version 5) I have some additional concerns regarding use of Hocon in general: The implementation is fairly large (~100 files or ruby code) and as such, likely expensive to maintain. It may have a negative impact on both CLI boot time and memory consumption. It will require additional efforts when doing internationalization if we want error messages that stems from parsing configuration files to be localized. It introduces yet another syntax that Puppet users must learn (should be weighted against user value). It is not a subset of YAML which is used current Hiera configurations (the text in the description is not valid Hocon). 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 (PDOC-120) Generated _index.html page is not accessible on github.io
Title: Message Title David Schmitt commented on PDOC-120 Re: Generated _index.html page is not accessible on github.io +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 (PDOC-120) Generated _index.html page is not accessible on github.io
Title: Message Title Henrik Lindberg commented on PDOC-120 Re: Generated _index.html page is not accessible on github.io I think it is better to use a different and more descriptive name than _index.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-6511) Add support for lookup.conf (version 5)
Title: Message Title
Henrik Lindberg commented on PUP-6511
Re: Add support for lookup.conf (version 5)
In a discussion with Thomas Hallgren we concluded that there are several issues with respect to Hocon and interpolation:
The hocon syntax squats on $ {name}
which means it will be very problematic if we ever want puppet style interpolation to work instead of the "hiera" syntax
Hocon resolves interpolations in data at the time the data is read - that is not how lookup/hiera works for data files - the hocon interpolation cannot be lazy
It is not possible to turn off hocon interpolation
Hocon interpolates keys bound in its context - they must be present when the file is read (or in the file)
Hocon interpolation cannot be extended with things like interpolation functions (or if done in the hocon implementation then it is no longer hocon).
Hocon interpolation transforms "to string" the Hocon way
(uncertain) keys with '::' in them (how that works in combination with interpolation) - both, anchored keys like '::foo', and for name-spacing.
We also concluded that use of "hocon for configuration files" have not yet come up with a complete solution for puppet settings - (including the use of interpolations there). It is thus premature to make any assumptions regarding how that will be made to work and if we do this one way for lookup in a lookup.conf it is quite likely not what we end up with.
Ideally we want to reduce the number of interpolation syntaxes to one (puppet). If we are to adopt hocon's interpolation in lookup.conf (instead of the current %{} way, that is "hiera") we will add yet another interpolation format with a new set of quirks and constraints. If we continue using the "hiera" (current) format we have the risk that users make errors and get smacked by the need to escape $ and possibly some braces.
To be safe, and not expose users to hocon interpolation, it seems best to use lookup.yaml until we have a solution to "settings". The hocon format brings close to no additional value compared to a lookup configuration in yaml.
Jira (PUP-6780) modify the lookup helper implementation to support v5 features
Title: Message Title Henrik Lindberg commented on PUP-6780 Re: modify the lookup helper implementation to support v5 features The ticket PUP-6511 is for the format of the lookup.conf - posting there about concerns regarding use of hocon. 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 (PDOC-120) Generated _index.html page is not accessible on github.io
Title: Message Title David Schmitt commented on PDOC-120 Re: Generated _index.html page is not accessible on github.io _index.html is not a very descriptive name. Fixing the jekyll issue as a sideeffect of improving the name doesn't sound wrong. 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 (PDOC-67) Issue with markdown rendering of code using ~~~
Title: Message Title Henrik Lindberg commented on PDOC-67 Re: Issue with markdown rendering of code using ~~~ A question here is if Strings allows the syntax to follow the ``` ? for example ``` puppet 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 (PDOC-120) Generated _index.html page is not accessible on github.io
Title: Message Title Henrik Lindberg commented on PDOC-120 Re: Generated _index.html page is not accessible on github.io Question is if we should automatically add .nojekyll or simply pick another name for the _index.html file that does not interfere with use of Jekyll. 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 (PDOC-120) Generated _index.html page is not accessible on github.io
Title: Message Title Henrik Lindberg commented on PDOC-120 Re: Generated _index.html page is not accessible on github.io David - this has to do with the use of Jekyll on github io. https://help.github.com/articles/files-that-start-with-an-underscore-are-missing/ it can be turned off by adding a .nojekyll file to the root. (There are other options - see the link). If you also want Jekyll processing to be available for some files, the file may not start with one of the special Jekyll characters (see the link, there are several ways to do that). 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-6780) modify the lookup helper implementation to support v5 features
Title: Message Title
Henrik Lindberg commented on PUP-6780
Re: modify the lookup helper implementation to support v5 features
In general, the features of a "data language" like hocon are at a lower level. The right choice IMO is to just read the hocon data in an opaque way for data just as other formats may contain other interpolation or reference features. The worst case then is getting two levels of interpolation and that there may be interference between the two syntaxes and more things to escape. (Something like the "verbatim" feature we discussed does not help with stopping hocon interpolation from taking place I assume since it is at a higher level).
For lookup.conf - which is the configuration format it is more a UX issue than a technical. How we do this is also related to a future rewrite of "puppet settings"
1.a We decided letting the format/encoding in the file decide which kind of interpolation to use by the framework when it gets a string value. Since we only support current "hiera" % style at the start that is what you get. If you decided to use hocon interpolation that is done at the lower level long before lookup's interpolation.
1.b Same here - we decided to make this configurable and that it is really determined by the data format/encoding
1.c Expressing PP style interpolation in Hocon seems like a challenge - can hocon interpolation be turned off ?
2. The %{} notation needs to be valid since that is the only interpolation we have. The ${} syntax in Hocon is at lower level.
3. Digging - is that really digging, rather than an alternative way of setting a value in a hash? We still need to do the digging in lookup at higher levels during a lookup since not all formats supports that. They must all behave the same way since at the user level the support cannot vary depending on data format. (Also note, an implementation of a data_dig style data provider function must implement digging with lookup semantics).
Ideally, users should only have to learn one interpolation syntax. Since we already have Puppet's it would be ideal if that could be used everywhere. The only place we can change is in lookup.conf, but then only if it does not clash with Hocon interpolation.
Add Comment
This message was sent by Atlassian JIRA
Jira (PDB-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Pieter Loubser moved an issue PuppetDB / PDB-3092 Improve performance of resource_events queries with 'corrective_change = true Change By: Pieter Loubser Key: PE PDB - 17908 3092 Project: Puppet Enterprise [Internal] PuppetDB 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-3092) Improve performance of resource_events queries with 'corrective_change = true
Title: Message Title Karel Brezina commented on PDB-3092 Re: Improve performance of resource_events queries with 'corrective_change = true A partial index like CREATE INDEX resource_events_status_for_corrective_change_idx ON resource_events (status) WHERE corrective_change; would increase performance of queries with corrective_change = true and wouldn't consume a lot of disk space 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
Jira (PUP-6780) modify the lookup helper implementation to support v5 features
Title: Message Title
Thomas Hallgren commented on PUP-6780
Re: modify the lookup helper implementation to support v5 features
Some concerns around Hocon support.
We currently allow interpolation in the hiera.yaml config file and we control this interpolation our selves. The format uses is % {xxx}. We forbid the use of the "hiera function" syntax (i.e. %{func("xxx")}). Hocon has it's own interpolation format which is similar (but not equal to) puppet. It uses ${xxx}
syntax. One problem with this is that the '% {xxx}
' syntax is used throughout by lookup. I.e. it's consistently used. This raises a couple of questions.
1. Hocon seems well designed. It should be no problem to use the ${} support that it provides for the config files. But if we do: 1a. What about a Hocon provider? Should it too use the ${} instead of the %{} syntax? 1b. What about the general support in lookup. Should it different and still use %{}? 1c. What about the differences between PP interpolation and Hocon interpolation (becomes especially interesting if we introduce a PP based provider). 2. If we want to retain support for %{} syntax in Hocon, what about the ${} syntax? Should it be interchangeable or have different meaning?
Hocon also understands keys with dot notation and treats this:
foo.bar : 42
equivalent to:
foo { bar : 42 }
Do we utilize that or should "digging" still be performed by lookup?
Add Comment
Jira (PUP-6780) modify the lookup helper implementation to support v5 features
Title: Message Title
Thomas Hallgren updated an issue
Puppet / PUP-6780
modify the lookup helper implementation to support v5 features
Change By:
Thomas Hallgren
Comment:
Some concerns around Hocon support.We currently allow interpolation in the {{hiera.yaml}} config file and we control this interpolation our selves. The format uses is %{xxx}. We forbid the use of the "hiera function" syntax (i.e. %{func("xxx")}). Hocon has it's own interpolation format which is similar (but not equal to) puppet. It uses ${xxx} syntax.
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-6780) modify the lookup helper implementation to support v5 features
Title: Message Title
Thomas Hallgren commented on PUP-6780
Re: modify the lookup helper implementation to support v5 features
Some concerns around Hocon support.
We currently allow interpolation in the hiera.yaml config file and we control this interpolation our selves. The format uses is % {xxx}. We forbid the use of the "hiera function" syntax (i.e. %{func("xxx")}). Hocon has it's own interpolation format which is similar (but not equal to) puppet. It uses ${xxx}
syntax.
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-5908) Implement a PCore MsgPack Serializer
Title: Message Title Thomas Hallgren commented on PUP-5908 Re: Implement a PCore MsgPack Serializer Kylo Ginsberg, ping... 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.
