Jira (PUP-4359) puppetversion fact is missing
Title: Message Title Michael Smith commented on PUP-4359 Re: puppetversion fact is missing I'm not clear which facter version you're trying to demonstrate there. I'd assume the puppet-agent package you installed includes facter and cfacter. Native facter wouldn't include the puppetversion fact, it's only present in puppet (when using native facter). 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-4359) puppetversion fact is missing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4359 puppetversion fact is missing Change By: Kurt Wall Assignee: KurtWall 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional I believe the PR I was thinking of is going in the other direction... https://github.com/puppetlabs/puppet/pull/3321 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-942) Create acceptance tests for Facter external facts dir
Title: Message Title Eric Thompson commented on FACT-942 Re: Create acceptance tests for Facter external facts dir schema 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional Can you link me to the client authoritative environment PR you mentioned? I'd like to take a look. I understand the security implications; i absolutely feel that this is something that should be configurable, especially given that it would change the current behavior. The feature is that it should be possible to invoke puppet agent using the --environment and --noop flags even with a server specified environment. Any other component of this request is simply an implementation detail. Again, we don't need the ability to set enforcement of environments on a per node basis via the ENC; that's just one possible implementation of the original request. Perhaps it would make sense to explain this in terms of a workflow? I want to deploy new code to my production infrastructure. I am currently building a feature branch. Prior to deploying this code, I wish to invoke a --noop run to determine what would change with the new branch. Current workflow with enc specified: 1. Put the node into noop mode, or disable Puppet on the node. 2. Set the node to use user-specified environment in the PE console (note that not all consoles support this.) 3. Invoke puppet on the node, using --environment to specify the new environment. 4. Return the node to its original environment in the console. 5. Return the node to enforcing mode, or re-enable puppet. If I forget to perform step 1 before changing the environment in step 2, I may cause the wrong branch of code to be enforced on the node. This could potentially break the node. If I fail to enable user-specified environments in step 2, the master will reject my environment request. If I fail to return the node to it's original environment in step 4, puppet may be invoked with the wrong environment, potentially breaking the node. If I fail to re-enable puppet in step 5, the node's configuration will no longer be enforced, potentially breaking production. Other notes: The overhead of performing this process will discourage simulation of changes prior to release. There are few ways to mitigate these risks using automation. Disabling ENC specified environments globally is not an option in this scenario for the reasons mentioned in my previous post.
Jira (PUP-4465) Document PUP-4201 JSON logging via --logdest
Title: Message Title Nicholas Fagerlund created an issue Puppet / PUP-4465 Document PUP-4201 JSON logging via --logdest Issue Type: Bug Affects Versions: PUP 3.8.0 Assignee: Thomas Hallgren Components: DOCS Created: 2015/04/27 12:58 PM Fix Versions: PUP 3.8.0 Priority: Normal Reporter: Nicholas Fagerlund PUP-4201 added support for specifying --logdest /var/log/somefile.json and getting a (partial) JSON array of log message objects. This wasn't documented. Docs for --logdest are in several files in lib/puppet/application/NAME.rb. The most important ones are apply, agent, and master. All three of these, at least, need edits to reflect the new feature. This feature is quiet enough and odd enough that I believe updating the description of --logdest is the only documentation we need.
Jira (PDB-1447) remove late-project/basic-project and supply the functionality with the database.
Title: Message Title Wyatt Alt assigned an issue to Wyatt Alt PuppetDB / PDB-1447 remove late-project/basic-project and supply the functionality with the database. Change By: Wyatt Alt Assignee: WyattAlt 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-4359) puppetversion fact is missing
Title: Message Title Michael Smith commented on PUP-4359 Re: puppetversion fact is missing Right, that's fair. 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-4351) Default service type and package provider not set on Cumulus Linux
Title: Message Title Stan Duffy commented on PUP-4351 Re: Default service type and package provider not set on Cumulus Linux Josh Cooper FYI, We do have Cumulus Linux here in house. 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-942) Create acceptance tests for Facter external facts dir
Title: Message Title Michael Smith commented on FACT-942 Re: Create acceptance tests for Facter external facts dir Ignoring the acceptance dir should be possible. Trying with https://github.com/puppetlabs/facter/pull/931. 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional In PE 3.8.0 there is going to be a PE-only module called Puppet Catalog Preview that allows a catalog compilation to be made in two different environments and the resulting catalogs are diffed. This takes place on the master side. It does not run the catalog in no-op mode, but it is intended as help when refactoring or migrating between versions of puppet code. It sounds like it could potentially take some pain away by reducing the number of no-op runs that are required until having a satisfactory result (at least for some use cases). Sounds like the absolute best support would be if it was possible to directly invoke run this node now in noop-mode in environment x directly from the PE console UI (or multiple nodes, etc.). 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-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4435 Deprecate Puppet WEBrick and Rack servers Change By: Kurt Wall Assignee: KurtWall 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-4435) Deprecate Puppet WEBrick and Rack servers
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4435 Deprecate Puppet WEBrick and Rack servers Change By: Kurt Wall Assignee: QA KurtWall 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-4466) add acceptance: ensure functions can be written/execute in puppet language
Title: Message Title Eric Thompson created an issue Puppet / PUP-4466 add acceptance: ensure functions can be written/execute in puppet language Issue Type: Sub-task Assignee: Eric Sorenson Components: QA Created: 2015/04/27 2:01 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You received this message because you are subscribed to
Jira (PUP-4413) Add acceptance test that 3.x forbidden env names work in 4.x
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4413 Add acceptance test that 3.x forbidden env names work in 4.x Change By: Eric Thompson Assignee: KurtWall EricThompson 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional The Puppet Catalog Preview feature sounds very powerful, and I'm excited to see it. Any chance it will require changes similar to what I've requested here? It runs master side only, and uses facts from the node as stored in PuppetDB, and it uses the ENC for classification, but it can override the ENC's decision regarding environment. It never sends the catalog to the agent. It would be possible to ship the previewed catalog to the agent and apply it with a noop. bg. Noop mode of course has some real benefits over catalog diff. A big one is that it can be used to develop 'rollback' releases, which can be very difficult to implement otherwise. Yes, naturally, you want to assert that it has the desired effect on the system. I'm hoping for a more generic solution that can be used without the PE console; I have a lot of clients running OS Puppet, and I did a lot of PE deploys without the console prior to PE 3.7. For that, I think the solution is to write an ENC implementation Possibly one that delegates to another already existing ENC. Run this node now in noop-mode in environment x The PE Orchestration console in PE already gives us this ability, and the PE console provides a great reporting engine to see the results. The combination is very powerful and very flexible. The only missing piece is the ability to use agent specified environments even with ENC specified environments. And then we are back at square one. Sounds like a feature to add to PE Orchestration. Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d)
Jira (PUP-4464) 4.x parser bug with anonymous data structures
Title: Message Title
Eric Sorenson created an issue
Puppet / PUP-4464
4.x parser bug with anonymous data structures
Issue Type:
Bug
Affects Versions:
PUP 4.0.0
Assignee:
Unassigned
Components:
Language
Created:
2015/04/27 12:38 PM
Priority:
Normal
Reporter:
Eric Sorenson
A user reported via IRC, and Richard Clamp repro'ed, the following issue using anonymous data structures to iterate over. The short version is that using an array, then a hash, confuses the parser, but hash then array works. So this is OK:
class munin {
Jira (PUP-2080) Support functions written in pp
Title: Message Title Eric Thompson commented on PUP-2080 Re: Support functions written in pp should this old pre-docs commit be re-instated: pre-docs 88dff99c 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-4359) puppetversion fact is missing
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4359 puppetversion fact is missing Change By: Kurt Wall Assignee: KurtWall 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-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage puppetdb=# select count(*) from fact_values where id not in (select distinct fact_value_id from facts); count --- 47146 (1 row) Add Comment This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) -- You
Jira (PUP-4359) puppetversion fact is missing
Title: Message Title Eric Thompson commented on PUP-4359 Re: puppetversion fact is missing it doesn't matter because we're testing if puppet sets it, no? it's not there when i install facter3 by itself. it's there after puppet is installed. There aren't any builds to test puppet/stable by itself (without installing some build of facter3), so i'm not sure how else i'd test it... 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-4388) Remove START option in /etc/default/puppet on Debian
Title: Message Title William Hopper updated an issue Puppet / PUP-4388 Remove START option in /etc/default/puppet on Debian Change By: William Hopper Summary: Remove STARToptionin /etc/default/puppetonDebian 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-4388) Remove START option in /etc/default/puppet on Debian
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4388 Remove START option in /etc/default/puppet on Debian Change By: Kurt Wall Assignee: KurtWall 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-2080) Support functions written in pp
Title: Message Title Eric Thompson assigned an issue to QA Puppet / PUP-2080 Support functions written in pp Change By: Eric Thompson Assignee: EricThompson 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 (PUP-4437) Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390
Title: Message Title Nicholas Fagerlund updated an issue Puppet / PUP-4437 Update the puppet-agent Repo for 4.0.1 to Incorporate Fix for PUP-4390 Change By: Nicholas Fagerlund Fix Version/s: PUP3.8.0 Fix Version/s: PUP4.1.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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional Thanks for digging that up. Yes, I think that PR is unrelated. 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-4388) Remove /etc/default/puppet on Debian
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4388 Remove /etc/default/puppet on Debian Change By: Kurt Wall Assignee: QA KurtWall 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-2080) Support functions written in pp
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-2080 Support functions written in pp Change By: Eric Thompson Assignee: QA EricThompson 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional The Puppet Catalog Preview feature sounds very powerful, and I'm excited to see it. Any chance it will require changes similar to what I've requested here? Noop mode of course has some real benefits over catalog diff. A big one is that it can be used to develop 'rollback' releases, which can be very difficult to implement otherwise. I'm hoping for a more generic solution that can be used without the PE console; I have a lot of clients running OS Puppet, and I did a lot of PE deploys without the console prior to PE 3.7. Run this node now in noop-mode in environment x The PE Orchestration console in PE already gives us this ability, and the PE console provides a great reporting engine to see the results. The combination is very powerful and very flexible. The only missing piece is the ability to use agent specified environments even with ENC specified environments. 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-1124) PuppetDB high CPU usage
Title: Message Title Anton Fomenko commented on PDB-1124 Re: PuppetDB high CPU usage Wyatt Alt, I\m putting the following code in my module lib/facter/last_run.rb require 'facter' Facter.add(last_run) do has_weight 100 confine :kernel = [ 'Linux' , 'SunOS' , 'FreeBSD' , 'Darwin' ] setcode do Facter::Util::Resolution.exec(date '+%a %b %d %T:%N %Z %Y') end end And no result: [root@srv puppet]# cfacter --custom-dir modules/my/lib/facter/ | grep last
Jira (PUP-2080) Support functions written in pp
Title: Message Title Henrik Lindberg commented on PUP-2080 Re: Support functions written in pp Well, it is documented in puppet-specifications now, so not meaningful to add same (or another version) of the specification in pre-docs. 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional For that, I think the solution is to write an ENC implementation Possibly one that delegates to another already existing ENC. To the best of my understanding, the ENC has no knowledge of the client specified environment. Thus, there's no way to determine whether or not the client specified an environment, and to react accordingly. Whatever solution is provided, simplicity is key. There's already a lot of stuff in puppet that's difficult to understand. I don't feel that a best practices workflow should require writing a custom ENC or an ENC wrapper. 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-4461) manifest changes are ignored when using hiera_include
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Henrik Lindberg Assignee: HenrikLindberg 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-4461) manifest changes are ignored when using hiera_include
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Thomas Hallgren Assignee: ThomasHallgren 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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4462 Single backslash before $ blocks interpolation in heredoc with no escapes enabled Change By: Thomas Hallgren Assignee: ThomasHallgren 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-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Thomas Hallgren Assignee: ThomasHallgren 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 Kenneth Barber updated an issue PuppetDB / PDB-1453 handle comparison queries with non-numerics Change By: Kenneth Barber Sprint: PuppetDB2015-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-1274) PR (1291): (maint) Change version policy to account for upgrades - senior
Title: Message Title Ryan Senior updated an issue PuppetDB / PDB-1274 PR (1291): (maint) Change version policy to account for upgrades - senior Change By: Ryan Senior Sprint: PuppetDB2015-05-06 Story Points: 0 Fix Version/s: PDB3.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-4461) manifest changes are ignored when using hiera_include
Title: Message Title Henrik Lindberg commented on PUP-4461 Re: manifest changes are ignored when using hiera_include In the most pathological case if a sequence of catalogs are requested, each loading one system function there would be one copy of each such environment, up to around ~20 (the number of 4.x. functions that can be loaded from the system). While it would be beneficial to keep the loaded system code, it can not be instantiated and bound to a closure across environment instances. The fix to this problem is simply to change the class instance variable to a instance variable. 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-4461) manifest changes are ignored when using hiera_include
Title: Message Title Thomas Hallgren commented on PUP-4461 Re: manifest changes are ignored when using hiera_include Merged to stable at 087071d and onward to master at 6960815 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Henrik Lindberg Fix Version/s: PUP4.1.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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg commented on PUP-4463 Re: split with just Regexp (unparameterized type) splits on whitespace This problem although present in 3.x with future parser, is more apparent in 4.0.0 since the Regexp pattern can be used in additional places (like in the split function). The fix is therefore only targeting 4.1.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-1455) Accommodate AIO (paths, etc.)
Title: Message Title Kenneth Barber updated an issue PuppetDB / PDB-1455 Accommodate AIO (paths, etc.) Change By: Kenneth Barber Sprint: PuppetDB2015-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 gepetto-bot commented on PDB-1457 Re: PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior senior commented: Creating this PR to see the acceptance tests green. Once that's green we may want to either roll back the version bump (just fix the tests) in preparation for the move, or merge it in as-is and follow the release cycle. RC is expected this week. 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Henrik Lindberg Affects Version/s: PUP4.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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Henrik Lindberg Sprint: Language2015-04-29 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Henrik Lindberg Assignee: HenrikLindberg 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-4461) manifest changes are ignored when using hiera_include
Title: Message Title Thomas Hallgren commented on PUP-4461 Re: manifest changes are ignored when using hiera_include Merge to 3.x at fef28c6 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 Ryan Senior assigned an issue to Unassigned PuppetDB / PDB-1289 Use producer_timestamp in GC query Change By: Ryan Senior Assignee: RyanSenior 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 gepetto-bot created an issue PuppetDB / PDB-1457 PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior Issue Type: Task Assignee: Unassigned Created: 2015/04/27 5:44 AM Labels: github Priority: Normal Reporter: gepetto-bot (maint) Bump to clojure 1.7.0-beta2 Author: Ryan Senior senior.r...@gmail.com Company: Github ID: senior Pull Request 1367 Discussion Pull Request 1367 File Diff Pull Request Description Found some failures in the events_test that was relying on the order of entries in a map that has changed in 1.7.0. Created a version of clojure.core/select-values that will preserve the order of selected keys and switched to an ordered-map to fix the issue.
Jira (PUP-4461) manifest changes are ignored when using hiera_include
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4461 manifest changes are ignored when using hiera_include Change By: Thomas Hallgren Assignee: ThomasHallgren 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-3596) Ensure Language Specification specifies behavior of undef resource param
Title: Message Title Henrik Lindberg assigned an issue to QA Puppet / PUP-3596 Ensure Language Specification specifies behavior of undef resource param Change By: Henrik Lindberg Status: InProgress ReadyforTest Assignee: HenrikLindberg 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 (PUP-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Thomas Hallgren commented on PUP-4374 Re: Splatting attributes into an amended attribute block isn't supported Merged to 3.x at 150e845. Merged to stable at 755b234. Merged to master at ac1de00. 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 gepetto-bot commented on PDB-1457 Re: PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior pljenkinsro commented: Test PASSed. Refer to this link for build results (access rights to CI server needed): https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1090/ 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Thomas Hallgren commented on PUP-4463 Re: split with just Regexp (unparameterized type) splits on whitespace Merged to stable at 4c672b4. Merged to master at d69dec0. 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Thomas Hallgren Assignee: ThomasHallgren 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-4374) Splatting attributes into an amended attribute block isn't supported
Title: Message Title Thomas Hallgren assigned an issue to Unassigned Puppet / PUP-4374 Splatting attributes into an amended attribute block isn't supported Change By: Thomas Hallgren Assignee: ThomasHallgren 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Thomas Hallgren assigned an issue to Thomas Hallgren Puppet / PUP-4463 split with just Regexp (unparameterized type) splits on whitespace Change By: Thomas Hallgren Assignee: ThomasHallgren 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-3596) Ensure Language Specification specifies behavior of undef resource param
Title: Message Title Henrik Lindberg commented on PUP-3596 Re: Ensure Language Specification specifies behavior of undef resource param Specification updated (catalog_expressions.md) now has a table to illustrate what happens when parameter has no default _expression_, one that is undef, and one that is not undef in combination with no setting, a setting of undef, a setting of something else, and in combination with data binding having a value bound or not. Also added some rules of thumb from a user perspective as it is difficult at first to figure out what the different effect of the various combinations are. 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 Ryan Senior updated an issue PuppetDB / PDB-1457 PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior Change By: Ryan Senior Sprint: PuppetDB2015-05-06 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 gepetto-bot commented on PDB-1457 Re: PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior Pull request (maint) Bump to clojure 1.7.0-beta2 has been closed. 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional Determining whether or not a node is permitted to change it's own environment is trivial using a custom ENC and a node parameter; that's not the problem I'm trying to solve. What's needed is a way to determine whether or not the agent specified an environment, and based on that condition determine whether to return the ENC specified environment or not. 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Christopher Barbour commented on PUP-4459 Re: Authoritative ENC Environments should be optional I see, thanks for clarifying. I assume that this is the logic you've been referring to: https://github.com/puppetlabs/puppet/blob/15c4ffdc5415b1ee8c701a956ec0c5cefaf7af41/lib/puppet/indirector/node/exec.rb#L24 This solves the problem. The only remaining issue is to determine whether the agent specified environment is the default environment, or if it's been over-ridden on the command line. I think your original conclusion is correct; this logic can be indirector specific, and doesn't need to be a puppet.conf setting. So, this can be closed as wont-fix. 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-4380) Split non-core puppet functionality into modules
Title: Message Title Justin Stoller commented on PUP-4380 Re: Split non-core puppet functionality into modules Also, to provide info to the question I raised, I believe elsewhere Eric Sorenson set the initial scope of this (Puppet 4.2 timeframe) to include organizing the types and providers internally as modules so they are pulled down via filesync. Though they continue to be in tree and maintained by PL they otherwise look like modules. Then through the PUP 4 lifetime they would be moved to community namespace or wherever. I still have a feeling that the wherever for PE support through the 4.x lifecycle will mean some kind of collaboration with the supported modules team. But that decision doesn't need to be made now. Kylo Ginsberg, are the core/external types going to be documented somewhere, like an arm? 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional Technically, an ENC is a indirector terminus for node (either the node_terminus=exec; executes an external script), or node_terminus=console (PE). An indirector terminus can call another terminus by delegating. One could be derived from the exec terminus https://github.com/puppetlabs/puppet/blob/master/lib/puppet/indirector/node/exec.rb#L24 (is where the ENC in an exec overrides the env in the request) and simply via some external configuration file determine if the node in question should be allowed to specify its own environment. It could also execute a script to determine an overriding environment. To do the same with console, the new wrapping terminus need to delegate the request, and then modifiy the node object that is returned (simply node.environment = 'this_is_the_one_i_want) before returning the node. A terminus like this can be delivered in a module; there is no need for it to be in puppet. An alternative is to update the ENC external command API to also accept the request environment (the one given by the agent) as an argument to the ENC script. (That does not help with the console terminus though since it is not based on an external command). 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional I just explained how to do that. As you said, the --environment given on the agent apply command line (or the configured environment on the agent) is not passed on to the ENC (unless it is done via some other means like a fact). The value for the --environment given on the agent is part of the indirector request though. Thus a custom node terminus can pick that up and do what it wants. 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-4411) Allow create_resources() to declare parameterized classes
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-4411 Allow create_resources() to declare parameterized classes Change By: Owen Rodabaugh CS Priority: Trivial 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-4411) Allow create_resources() to declare parameterized classes
Title: Message Title Owen Rodabaugh updated an issue Puppet / PUP-4411 Allow create_resources() to declare parameterized classes Change By: Owen Rodabaugh CS Priority: NeedsPriority Trivial 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-965) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg commented on FACT-965 Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Moved this to FACT and marked for facter 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 (FACT-965) facter doesn't run under jruby
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-965 facter doesn't run under jruby Change By: Kylo Ginsberg Summary: Investigate:Puppetserverimplictlyrelieson facter buthasnomechanismto doesn't run nativefacter underjruby 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-965) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg updated an issue Facter / FACT-965 Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Change By: Kylo Ginsberg Fix Version/s: FACT3.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 (FACT-965) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Kylo Ginsberg moved an issue Facter / FACT-965 Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Change By: Kylo Ginsberg Component/s: AIO Affects Version/s: PUP4.0.0 Key: PUP FACT - 965 Project: Puppet Facter 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-4419) create acceptance to ensure client does not overwrite server-set variables
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4419
create acceptance to ensure client does not overwrite server-set variables
Change By:
Eric Thompson
fromtheparent(quoting[~henrik.lindberg]):{quote}AfterdiscussionwithEricSoerenson,wedecidedthatitwasbesttomakethisanopt-inandthatwearenotaddingafunction-thisforthesakeofconsistencybetween$facts,$trusted_facts,and$server_facts.Thismeans:*Atthesameplacewherewecurrentlyset$trusted_factsweshouldalsoset$server_factsifusershaveoptedin*Thevaluessetin$server_factsarethe@server_factssetinthenodebythecompilerindirection+thecurrentenvironmentname*Theuseroptsinbyusingthesetting:trusted_server_facts*Thesettingisfalsebydefault*Weissueawarningifanynodeparameterisoverwritten{quote}
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 `hash in (?,?,?...)` queries - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1456 PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - 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 (PDB-1444) PR (1358): (maint) Move late-project? from queries to columns - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1444 PR (1358): (maint) Move late-project? from queries to columns - ajroetker Change By: AJ Roetker Sprint: PuppetDB2015-06-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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1456 PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker Change By: AJ Roetker Sprint: PuppetDB2015-06-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 (PUP-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional I assume this is the logic you've been referring to: https://github.com/puppetlabs/puppet/blob/15c4ffdc5415b1ee8c701a956ec0c5cefaf7af41/lib/puppet/indirector/node/exec.rb#L24 yes, that is where the exec node indirection make the override. There is something similar in the console node indirector, but that source is not public. This solves the problem. The only remaining issue is to determine whether the agent specified environment is the default environment, or if it's been over-ridden on the command line. That is tricky (as in impossible), as when the request arrives at the master, it is not possible to determine if it was overridden from the command line or specified as a setting (that information is not part of the REST request). You would have to base it on a known default (like production), but then not being able to know if that was given on the command line or not). I think your original conclusion is correct; this logic can be indirector specific, and doesn't need to be a puppet.conf setting. So, this can be closed as wont-fix. ok... closing 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,
Jira (PUP-4444) Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter
Title: Message Title Jeremy Barlow commented on PUP- Re: Investigate: Puppetserver implictly relies on facter but has no mechanism to run native facter Peter Huene and Kylo Ginsberg, elaborating on the discussion we had about the HttpClient “hook” approach that I’d mentioned we followed in Puppet Server in order to register an alternative http_client with core Ruby Puppet when running under Puppet Server. I think this is what Christopher Price had been alluding to in a prior comment in this thread: The “hook” was added to the Puppet::Network::HttpPool module in core Ruby Puppet. See: https://github.com/puppetlabs/puppet/blob/4.0.0/lib/puppet/network/http_pool.rb#L14-L21 When running under MRI Ruby by default, an Puppet::Network::HTTP::Connection instance would be used for HTTP client calls. Puppet Server, during its initialization, would register an alternative http_client: https://github.com/puppetlabs/puppet-server/blob/master/src/ruby/puppet-server-lib/puppet/server/config.rb#L27 Like I mentioned, even if it were viable, I’m not sure if this is the best approach for the hook being done for CFacter support. I believe the approach that Peter Huene has started pursuing could allow for CFacter to be accessed from Ruby Facter when running under JRuby without a special assist from Puppet Server. This could be advantageous for other potential reuses of CFacter from Ruby in the future where Puppet Server wouldn't be in the stack. 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
Jira (PUP-4467) Netscape comment extension uses wrong encoding
Title: Message Title Jeremy Barlow created an issue Puppet / PUP-4467 Netscape comment extension uses wrong encoding Issue Type: Bug Affects Versions: PUP 4.0.0 Assignee: Unassigned Created: 2015/04/27 5:35 PM Priority: Normal Reporter: Jeremy Barlow The value for a Netscape Comment certificate extension is supposed to be an ASN.1 OctetString which wraps an IA5String. Originally, I believe this was documented here, but this link no longer appears to be active: http://wp.netscape.com/eng/security/cert-exts.html References to this needing to be an IA5String, however, appear in some other places: http://docs.oracle.com/cd/E19957-01/816-5533-10/ext.htm#top http://javadoc.iaik.tugraz.at/iaik_jce/current/iaik/x509/extensions/netscape/NetscapeComment.html http://www.convertwriteservices.com/assets/docs/API/certj_reference/javadoc/com/rsa/certj/cert/extensions/NetscapeComment.html Prior to Puppet 4, the Ruby Puppet CA would generate the Netscape Comment extension value as a raw OctetString, not wrapping a
Jira (PUP-4348) Add test(s) for the File resource purge attribute
Title: Message Title Eric Thompson assigned an issue to Unassigned Puppet / PUP-4348 Add test(s) for the File resource purge attribute Change By: Eric Thompson 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-1289) Use producer_timestamp in GC query
Title: Message Title Ryan Senior commented on PDB-1289 Re: Use producer_timestamp in GC query Talking with Russell Mull and AJ Roetker. AJ will handle 1 and 5. Russ is already in the area of code that is 2 and 3, so he'll take that. And 4 is no longer needed since we are entirely pull based. 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 AJ Roetker assigned an issue to AJ Roetker PuppetDB / PDB-1289 Use producer_timestamp in GC query Change By: AJ Roetker Assignee: AJRoetker 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-1124) PuppetDB high CPU usage
Title: Message Title Wyatt Alt commented on PDB-1124 Re: PuppetDB high CPU usage Anton Fomenko Sorry, I missed that you were using the weight there. The weight argument seems to be functioning fine for me on facter 2.4.3. Are you up to date? 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-4419) create acceptance to ensure client does not overwrite server-set variables
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-4419 create acceptance to ensure client does not overwrite server-set variables Change By: Eric Thompson Assignee: KurtWall EricThompson 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-4348) Add test(s) for the File resource purge attribute
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-4348
Add test(s) for the File resource purge attribute
Change By:
Eric Thompson
TheFileresource{{purge}}attributeisnottestedinspec or nor acceptance.Fixthis.
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 AJ Roetker updated an issue PuppetDB / PDB-1444 PR (1358): (maint) Move late-project? from queries to columns - ajroetker Change By: AJ Roetker Sprint: PuppetDB2015- 06 05 - 03 06 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 `hash in (?,?,?...)` queries - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1456 PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker Change By: AJ Roetker Sprint: PuppetDB2015- 06 05 - 03 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-1456) PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker
Title: Message Title AJ Roetker updated an issue PuppetDB / PDB-1456 PR (1366): (maint) Speed up storage.clj `hash in (?,?,?...)` queries - ajroetker Change By: AJ Roetker Sprint: PuppetDB2015-05- 20 06 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-4348) Add test(s) for the File resource purge attribute
Title: Message Title Eric Thompson commented on PUP-4348 Re: Add test(s) for the File resource purge attribute this is already done: spec/integration/type/file_spec.rb#L1440-L1487 it tests both file and directory purging 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg commented on PUP-4459 Re: Authoritative ENC Environments should be optional I should have added, you would need to add a fact or something that is passed on to the server to know that the request is different. (But if you go to the trouble of doing that, there is less need for a fancy indirector since it would then pick up that fact instead and base the environment decision on that). 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-4459) Authoritative ENC Environments should be optional
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-4459 Authoritative ENC Environments should be optional Change By: Henrik Lindberg Assignee: HenrikLindberg 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-4380) Split non-core puppet functionality into modules
Title: Message Title Kylo Ginsberg commented on PUP-4380 Re: Split non-core puppet functionality into modules For context on what we might pull out, there have been (at least) two fruitful threads on puppet-dev on this topic: from Jan 2014, lots of discussion: https://groups.google.com/forum/#!msg/puppet-dev/4y9ZvbbkKBs/rmbhUlDvu9AJ from Oct 2014, less discussion but a crisp proposal: https://groups.google.com/forum/#!msg/puppet-dev/ENl4YndsuDE/PKwhqwpckyYJ 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-1448) 'replace facts' failing due to foreign key constraint issue
Title: Message Title Simon Oxwell commented on PDB-1448 Re: 'replace facts' failing due to foreign key constraint issue Hi Wyatt, I've now got 5 servers affected. I've collected the blocking fact values ids from the postgres logs, and they all seem to be related to our structured collections: puppetdb=# select factset_id,fact_value_id,value_hash,name,path from facts f inner join fact_values fv on f.fact_value_id=fv.id inner join fact_paths fp on f.fact_path_id=fp.id where f.fact_value_id in (807,810,1788,2709,2731,5697,1524348,1546444,1547903,1549732,1552056) order by fact_value_id; factset_id | fact_value_id |value_hash|name| path +---+--++-- 4 | 807 | eedbf60502cdb6b60552f2044fe16fcf6483e077 | funnelback_collections_profiles_structured | funnelback_collections_profiles_structured#~59#~collection 4 | 807 | eedbf60502cdb6b60552f2044fe16fcf6483e077 | funnelback_collections_structured | funnelback_collections_structured#~59 4 | 810 | cd339c27e31eff5c2c390c4c4e688d8ff1f60763 | funnelback_collections_profiles_structured | funnelback_collections_profiles_structured#~586#~collection 4 | 810 | cd339c27e31eff5c2c390c4c4e688d8ff1f60763 | funnelback_collections_structured | funnelback_collections_structured#~586
Jira (PUP-4359) puppetversion fact is missing
Title: Message Title Kurt Wall assigned an issue to Unassigned Puppet / PUP-4359 puppetversion fact is missing Change By: Kurt Wall Assignee: KurtWall 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-4359) puppetversion fact is missing
Title: Message Title Kurt Wall assigned an issue to Kurt Wall Puppet / PUP-4359 puppetversion fact is missing Change By: Kurt Wall Assignee: KurtWall 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-4348) Add test(s) for the File resource purge attribute
Title: Message Title
Kurt Wall updated an issue
Puppet / PUP-4348
Add test(s) for the File resource purge attribute
Change By:
Kurt Wall
TheFileresource{{purge}}attributeis nottested untested inspec nor and acceptance.Fixthis.
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 Ryan Senior updated an issue PuppetDB / PDB-1457 PR (1367): (maint) Bump to clojure 1.7.0-beta2 - senior Change By: Ryan Senior Story Points: 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-2315) function call error message about mis-matched arguments is hard to understand
Title: Message Title Henrik Lindberg commented on PUP-2315 Re: function call error message about mis-matched arguments is hard to understand I just reviewed the updated example document, and the proposed simplifications makes a lot of sense as they focus on the first given value that makes call unacceptable. 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-4463) split with just Regexp (unparameterized type) splits on whitespace
Title: Message Title Henrik Lindberg commented on PUP-4463 Re: split with just Regexp (unparameterized type) splits on whitespace Note added to language specification that an unparameterized Regexp type behaves as if it had a pattern of // when used as a regular _expression_. 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-4462) Single backslash before $ blocks interpolation in heredoc with no escapes enabled
Title: Message Title Thomas Hallgren commented on PUP-4462 Re: Single backslash before $ blocks interpolation in heredoc with no escapes enabled Merge to stable at 0f52fc9 with subsequent maintenance commit at 730d01e. 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.
