Jira (PUP-5873) Ensure generated file resources in static catalog are contained
Title: Message Title Josh Cooper assigned an issue to Josh Cooper Puppet / PUP-5873 Ensure generated file resources in static catalog are contained Change By: Josh Cooper Assignee: Josh Cooper Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5832
4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Change By:
Henrik Lindberg
We currently have no good way of handling sensitive data in a puppet manifest.In PUP-5831 we are adding a binary type. Ticket PUP-3600 is about making that Binary type work as content in an unmodified 3.x PSON/JSON encoded catalog for the File content attribute, but only there. That is not enough for Binary, and certainly no enough for Sensitive data.While other attributes could possibly also be handled as special cases,there is no general handling of binary until we have better serialization. (TBD Ref to ticket). While Binary works for some attributes, it makes it hard to support as the receiving end must know that it may get binary data, and what that binary data represents. Say that it should be a secret Integer - how does the receiver know this and not mistake for say a GIF?To support this, we add a new type; {{Sensitive\[T, chipher]}}, a subtype of {{Binary}} where {{T}} represents the unencrypted value type, and {{chiper}} a chipher reference as in OpenSSL::Chipher. A runtime object maintains both the encrypted and unencrypted value, or just the encrypted value. A {{Sensitive}} value may have to be able to present itself in a surrogate form i certain situations, such a surrogate value must be of the actual data type or usage may break.It is uncertain if the surrogate is of value or if this is a presentation issue as each presentation technology may be happy with just a sequence of asterisks for any data type, a very narrow type (like an Enum would also not be able to have a surrogate if the surrogate is one of the acceptable values. For those reasons a surrogate value should not be included in the design. The Boolean 'value_available' attribute is used to denote if the value attribute is available. This boolean is needed as the value {{T}} may accept {{Undef}}.Thus a sensitive object can be described by he struct type:{code:puppet}Struct[{ value => T, chipher => String, data => Hash[String, Binary], value_available => Boolean }]{code}When creating an instance of {{Sensitive}}, the data may come from a data source where the value is already encrypted. Data sources that supports this, should return an instance of Sensitive instead of the String representation. The data source will have some way of representing the Cipher as well as the encrypted value. When a {{Sensitive}} is created from unencrypted source enough information must be given to enable encryption. The sensitive data can hold multiple encrypted values, one for each recipient. The typical use cases is to allow the master to see the value for the purpose of deriving new values, and for a node, or nodes..The most common case would be to encrypt for a node - the clear data is only readable by the node, but other scenarios may apply (a certificate shared by a group etc.). Information available only to the master, then made available to a node etc. The method that creates a sensitive must therefore be able to handle these various options.In this proposal, the keyname is assumed to uniquely identify a name, and that a node's fqdn is such a suitable key.{code:puppet}Sensitive.new(String $cipher
Jira (PUP-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5832
4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Change By:
Henrik Lindberg
We currently have no good way of handling sensitive data in a puppet manifest.In PUP-5831 we are adding a binary type. Ticket PUP-3600 is about making that Binary type work as content in an unmodified 3.x PSON/JSON encoded catalog for the File content attribute, but only there. That is not enough for Binary, and certainly no enough for Sensitive data.While other attributes could possibly also be handled as special cases,there is no general handling of binary until we have better serialization. (TBD Ref to ticket). While Binary works for some attributes, it makes it hard to support as the receiving end must know that it may get binary data, and what that binary data represents. Say that it should be a secret Integer - how does the receiver know this and not mistake for say a GIF?To support this, we add a new type; {{Sensitive\[T, chipher]}}, a subtype of {{Binary}} where {{T}} represents the unencrypted value type, and {{chiper}} a chipher reference as in OpenSSL::Chipher. A runtime object maintains both the encrypted and unencrypted value, or just the encrypted value. A {{Sensitive}} value may have to be able to present itself in a surrogate form i certain situations, such a surrogate value must be of the actual data type or usage may break.It is uncertain if the surrogate is of value or if this is a presentation issue as each presentation technology may be happy with just a sequence of asterisks for any data type, a very narrow type (like an Enum would also not be able to have a surrogate if the surrogate is one of the acceptable values. For those reasons a surrogate value should not be included in the design. The Boolean 'value_available' attribute is used to denote if the value attribute is available. This boolean is needed as the value {{T}} may accept {{Undef}}.Thus a sensitive object can be described by he struct type:{code:puppet}Struct[{ value => T, chipher => String, data => Hash[String, Binary ] , surrogate =>T, value_available => Boolean }]{code}When creating an instance of {{Sensitive}}, the data may come from a data source where the value is already encrypted. Data sources that supports this, should return an instance of Sensitive instead of the String representation. The data source will have some way of representing the Cipher as well as the encrypted value. When a {{Sensitive}} is created from unencrypted source enough information must be given to enable encryption. The sensitive data can hold multiple encrypted values, one for each recipient. The typical use cases is to allow the master to see the value for the purpose of deriving new values, and for a node, or nodes.. The most common case would be to encrypt for a node - the clear data is only readable by the node, but other scenarios may apply (a certificate shared by a group etc.). Information available only to the master, then made available to a node etc. The method that creates a sensitive must therefore be able to handle these various options.In this proposal, the keyname is assumed to uniquely identify a name, and that a node's fqdn is such a suitable key.{code:puppet}Sensi
Jira (PUP-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5832
4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Change By:
Henrik Lindberg
We currently have no good way of handling sensitive data in a puppet manifest.In PUP-5831 we are adding a binary type and in . Ticket PUP-3600 we are is about making a that Binary type work as content in a an unmodified 3.x PSON/JSON encoded catalog for the File content attribute , but only there . That is not enough for Binary, and certainly no enough for Sensitive data. Other While other attributes could possibly also be handled as special cases, but there is no general handling of binary until we have better serialization . (TBD ref Ref to ticket). While Binary works for some attributes, it makes it hard to support as the receiving end must know that it may get binary data, and what that binary data represents. Say that it should be a secret Integer - how does the receiver know this and not mistake for say a GIF ?To support this, we add a new type; {{Sensitive\[T, chipher]}}, a subtype of {{Binary}} where {{T}} represents the unencrypted value type, and {{chiper}} a chipher reference as in OpenSSL::Chipher. A runtime object maintains both the encrypted and unencrypted value, or just the encrypted value. A {{ Sensitive }} value must may have to be able to present itself in a surrogate form i certain situations, such a surrogate value must be of the actual data type or usage may break.It is uncertain if the surrogate is of value or if this is a presentation issue as each presentation technology may be happy with just a sequence of asterisks for any data type, a very narrow type (like an Enum would also not be able to have a surrogate if the surrogate is one of the acceptable values. For those reasons a surrogate value is should not be included in the design . The Boolean ' clear_value value_available ' attribute is used to denote if the value attribute is available. This boolean is needed as the value {{T}} may accept {{Undef}}.Thus a sensitive object can be described by he struct type:{code:puppet}Struct[{ value => T, chipher => String, data => Binary, surrogate =>T, clear_value value_available => Boolean }]{code}When creating an instance of {{Sensitive}}, the data may come from a data source where the value is already encrypted. Data sources that supports this, should return an instance of Sensitive instead of the String representation. The data source will have some way of representing the Cipher as well as the encrypted value. When a {{Sensitive}} is created from unencrypted source enough information must be given to enable encryption.The most common case would be to encrypt for a node - the clear data is only readable by the node, but other scenarios may apply (a certificate shared by a group etc.). Information available only to the master, then made available to a node etc. The method that creates a sensitive must therefore be able to handle these various options.In this proposal, the keyname is assumed to uniquely identify a name, and that a node's fqdn is such a suitable key.{code:puppet}Sensitive.new(String $cipher, String $keyname, T $data){code}Handling data of {{Sensitive}} type in the 3.x catalog is
Jira (PUP-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Henrik Lindberg Comment: meh - you cannot change an Improvement into an Epic (at least not by just changing the type). Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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 (NPUP-18) Lexer does not properly handle double quoted strings with embedded double quotes in an interpolation
Title: Message Title
Henrik Lindberg commented on NPUP-18
Re: Lexer does not properly handle double quoted strings with embedded double quotes in an interpolation
String interpolation can nest to any level. e.g.
"string1 ${ "string2 $ { "string3..." }
end of string2"} end of string 1"
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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.
Jira (PUP-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5805 Parser never sets location on RHS of "resource without title" expressions Change By: Henrik Lindberg Release Notes Summary: Minor corner case not reported by any user. Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5851) FR - Puppet Lookup with Unicode Facts File
Title: Message Title Ethan Brown commented on PUP-5851 Re: FR - Puppet Lookup with Unicode Facts File Can puppet lookup not be used on a Windows agent node? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5879) Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8
Title: Message Title Ethan Brown created an issue Puppet / PUP-5879 Ensure Puppet uses FileSystem.read where applicable to read JSON, settings and other files as UTF-8 Issue Type: Bug Affects Versions: PUP 4.3.2 Assignee: Unassigned Created: 2016/02/10 6:46 PM Labels: windows utf-8 Priority: Normal Reporter: Ethan Brown There are a number of places in Puppet where the internal file abstraction Puppet::FileSystem is not used, but should be, to enforce files are read properly as UTF-8. This primarily affects Windows, where the local codepage frequently causes unnecessary conversions if UTF-8 is not explicitly specified. An initial spike is in the branch - https://github.com/Iristyle/puppet/commits/ticket/stable/PUP-5728-convert-remaining-File-read-calls-to-Puppet-FileSystem that built on the work in PUP-5728 Two other items of note: PE-13721 exposed a similar issue in the puppet_enterprise module in a Japanese Windows - this module should be spot checked and additional ti
Jira (PUP-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5805 Parser never sets location on RHS of "resource without title" expressions Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5873) Ensure generated file resources in static catalog are contained
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5873 Ensure generated file resources in static catalog are contained Change By: Sean Griffin QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5697) Inline file permissions
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5697 Inline file permissions Change By: Sean Griffin QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5815) Add a puppet agent command line option to fail the run if the catalog's environment doesn't match
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5815 Add a puppet agent command line option to fail the run if the catalog's environment doesn't match Change By: Sean Griffin QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5803) Handle recurse=true agent-side behaviors when metadata is inlined
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5803 Handle recurse=true agent-side behaviors when metadata is inlined Change By: Sean Griffin QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5118) Handle duplicate resources when inlining file metadata
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5118 Handle duplicate resources when inlining file metadata Change By: Sean Griffin QA Risk Assessment: High QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5805 Parser never sets location on RHS of "resource without title" expressions Change By: Eric Thompson QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5836) Splat operator should turn Iterator into an array
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5836 Splat operator should turn Iterator into an array Change By: Eric Thompson QA Highest Test Level: Unit Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5876) Enable static catalogs by default
Title: Message Title John Duarte updated an issue Puppet / PUP-5876 Enable static catalogs by default Change By: John Duarte QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5813) Fix memory-leaks caused by global variables holding on to environments
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5813 Fix memory-leaks caused by global variables holding on to environments Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Low QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5819) Lexer should raise a better error when loading manifest files containing a UTF-8 BOM (Byte Order Mark)
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5819 Lexer should raise a better error when loading manifest files containing a UTF-8 BOM (Byte Order Mark) Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Probability Reason: using incorrect unicode format QA Risk Assessment: Medium QA Risk Probability: Low QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to th
Jira (PUP-5876) Enable static catalogs by default
Title: Message Title John Duarte updated an issue Puppet / PUP-5876 Enable static catalogs by default Change By: John Duarte QA Risk Assessment: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5835) Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception
Title: Message Title
Eric Thompson updated an issue
Puppet / PUP-5835
Symbol in scope; puppet apply -e 'notify { $environment: }' raises an exception
Change By:
Eric Thompson
QA Risk Assessment Reason:
escaped and found by user
QA Highest Test Level:
Unit
QA Risk Assessment:
High
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-1780) Issue warning when undefined variables are accessed
Title: Message Title Eric Thompson updated an issue Puppet / PUP-1780 Issue warning when undefined variables are accessed Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Probability Reason: probable when writing modules/code QA Risk Assessment: Medium QA Risk Severity Reason: inconvenient for debugging QA Risk Probability: Medium QA Risk Severity: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5861) Puppet Array & Hash types should present themselves as just Array/Hash when they are default
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5861 Puppet Array & Hash types should present themselves as just Array/Hash when they are default Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5875) Iterators are presenting themselves as Ruby type names
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5875 Iterators are presenting themselves as Ruby type names Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Probability Reason: rare QA Risk Assessment: Medium QA Risk Severity Reason: if checking iterator type in logic QA Risk Probability: Low QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-4748) Allow resources to be purged even whey they have dependency relationships
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4748 Allow resources to be purged even whey they have dependency relationships Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Probability Reason: pre-existing, long-standing issue QA Risk Assessment: Medium QA Risk Severity Reason: non-removal of resources QA Risk Probability: Low QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5875) Iterators are presenting themselves as Ruby type names
Title: Message Title Henrik Lindberg commented on PUP-5875 Re: Iterators are presenting themselves as Ruby type names Merged to master: dde0e3c Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5805) Parser never sets location on RHS of "resource without title" expressions
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5805 Parser never sets location on RHS of "resource without title" expressions Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Severity Reason: confusing, possible error in code QA Risk Probability: Low QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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
Jira (PUP-5824) Interpolation of an empty variable %{} or %{::} should yield an empty string
Title: Message Title
Sean Griffin updated an issue
Puppet / PUP-5824
Interpolation of an empty variable %{} or %{::} should yield an empty string
Change By:
Sean Griffin
QA Risk Assessment:
Medium
QA Risk Probability:
Medium
QA Risk Severity:
Low
QA Status:
Reviewed
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send 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-5861) Puppet Array & Hash types should present themselves as just Array/Hash when they are default
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5861 Puppet Array & Hash types should present themselves as just Array/Hash when they are default Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium QA Risk Probability: Low QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-4818) PUP-121 (relative namespacing) was never actually resolved in 3.x future parser
Title: Message Title Eric Thompson updated an issue Puppet / PUP-4818 PUP-121 (relative namespacing) was never actually resolved in 3.x future parser Change By: Eric Thompson QA Risk Assessment Reason: existing. serious QA Highest Test Level: Acceptance QA Risk Assessment: Medium QA Risk Probability: Medium QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bug
Jira (PUP-5836) Splat operator should turn Iterator into an array
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5836 Splat operator should turn Iterator into an array Change By: Sean Griffin QA Risk Assessment: Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5776) Master Theme: As a Puppet Jira User I want to know how to work with Themes and Epics in the Puppet Project
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5776 Master Theme: As a Puppet Jira User I want to know how to work with Themes and Epics in the Puppet Project Change By: Henrik Lindberg As a user of Jira focusing on the PUP project, I want to know about existing Epics, and how they should be applied. When we make released I want to know what needs to be done to ensure we have the relevant Epics defined.I expect the PUP folks to update this story with links to the available Themes. And that this description is updated with an overall description of how Themes and Epics work.DESCRIPTION OF THEMES AND EPICS-A Theme represents an activity that stretched over many releases; e.g. "Performance". We use an Epic to describe such themes. They are always named with a prefix of "Theme:". An example is PUP-5775 "Theme: Performance" Epic.For each release series, there is an Epic that contains the tickets that directly implements something in that theme. Other tickets may also support that Epic. As an example PUP-5773 "4.x Performance" is an Epic that supports "Theme: Performance".(This construct is used since Jira does not support the notion of Theme).RELESE SERIES EPICS-Release series epics are named Nx e.g. "4.x Performance". Such themes are created lazily when there is going to be work on that theme for a release series. RELEASE EPICS-If there is a need to create an Epic that is closed with a specific release, it should be given a concrete version name e.g. "4.4 Performance", and this ticket should support "4.x Performace". which in turn supports "Theme: Performance".The decision to use a release specific epic is based on how many tickets there are in total for the release, and for the release series. If there are too many tickets it becomes hard to find and navigate. Hence the option to use version specific epic. Details: RULES - * Always use the Epic name as the start of the Summay or risk not finding the ticket when linking with "supports" * Assign thematic themes to all scrum teams that the theme is relevant for* Never place a multi team Epic in a sprint (if you must keep track of work on the Epic itself - defining it etc. use separate tasks). A Jira project administrator will otherwise be pushed one level down in dante's inferno for every such breaking of this rule). Add Comment
Jira (PDB-2422) Use bucketed summary for historical catalog sync
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2422 Use bucketed summary for historical catalog sync Issue Type: Improvement Assignee: Unassigned Created: 2016/02/10 4:14 PM Priority: Normal Reporter: Russell Mull Once we can do full historical catalogs, we need to turn on the bucketed summary query for catalog sync. Index for the summary query Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5761) when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5761 when puppet module-level data provider function defines an unqualified key, puppet lookup returns nothing Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2423) Limit initial sync to latest catalogs and reports
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2423 Limit initial sync to latest catalogs and reports Issue Type: Improvement Assignee: Unassigned Created: 2016/02/10 4:14 PM Priority: Normal Reporter: Russell Mull This should help replica provisioning time while providing enough consistency for the things we care about Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5733) The Puppet Parser should ensure files are read with UTF-8
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5733 The Puppet Parser should ensure files are read with UTF-8 Change By: Sean Griffin QA Risk Assessment Reason: duplicate QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5732) Puppet::Filesystem.read should handle encoding
Title: Message Title Sean Griffin updated an issue Puppet / PUP-5732 Puppet::Filesystem.read should handle encoding Change By: Sean Griffin QA Risk Assessment Reason: duplicate QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5114) Retrieve content using content_uri
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5114 Retrieve content using content_uri Change By: Eric Thompson QA Risk Assessment Reason: direct puppet QA Highest Test Level: Acceptance QA Risk Probability Reason: default QA Risk Assessment: High QA Risk Probability: High QA Risk Severity: High Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5837) reverse_each and step functions should return undef when given a block to avoid confusion
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5837 reverse_each and step functions should return undef when given a block to avoid confusion Change By: Eric Thompson QA Risk Assessment: Medium QA Risk Probability: Medium QA Risk Severity: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5767) Add the specification from PUP-1985 to language specification repo
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5767 Add the specification from PUP-1985 to language specification repo Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5878) acceptance: agent can reconnect after master failure
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5878 acceptance: agent can reconnect after master failure Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5771) Add introduction to Iterable and Iterator to Pre-docs for PUP-5648
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5771 Add introduction to Iterable and Iterator to Pre-docs for PUP-5648 Change By: Eric Thompson QA Status: Reviewed QA Risk Assessment: Low Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5114) Retrieve content using content_uri
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5114
Retrieve content using content_uri
Change By:
Josh Cooper
Modify the catalog building process to inline {{content_uri}} for files. It should be of the form:{noformat}content_uri => 'puppet:///modules/ntp/files/ntp.conf'{noformat}Note the path is rooted in the per-environment directory, e.g. {{/etc/puppetlabs/code/environments/production}}. By default, {{content_uri}} should not specify a host and port in the URI, e.g. {{puppet:///modules/...}}. However, if {{source => 'puppet://:'}}, then those values should be preserved in the {{content_uri}}.Modify the catalog application process to retrieve content for {{file}} resources using the {{content_uri}} parameter instead of {{source}}. If the {{content_uri}} parameter is absent (for example because source refers to a local file or custom mount point), then the agent should fallback to using {{source}} and retrieve latest file content like it does now.The agent should send the REST request of the form:{noformat}https://server:port/puppet/v3/static_file_content/?code_id={noformat}where {{}} is that path of the file to download, e.g. {{ modules / etc ntp / files/ ntpd.conf}}, and {{code_id}} is contained in obtained from the catalog. Also note the endpoint is called {{static_file_content}}, a recent development, and it's in the {{v3}} namespace.The agent may send {{environment=production}} as a query param due to the indirector, but it is not necessary since that information will be contained in {{code_id}}.The agent should stream the response back, reading chunks of the response body like we do for {{file_content}}: https://github.com/puppetlabs/puppet/blob/master/lib/puppet/type/file/content.rb#L216-L221. In other words, we don't want to read the entire file into a memory.The agent should use DNS SRV records like it does for {{file_content}} requests. This is accomplished by following the {{file_content}} example above.Also add rspec tests under spec/integration simulating the server responding with valid content, and with HTTP 404. The latter case should cause the resource to fail, and should be output in the log.Also update API documentation showing expected request/response. Since this will only be a puppetserver REST endpoint, it probably makes sense to add it there. See https://github.com/puppetlabs/puppet/pull/4586/files#r50486882 /cc [~kevin.corcoran] Questions:* If The compiler should only line {{ content_uri}} if {{ code_id}} is non- nil , but there's a /empty. If {{content_uri}} is present , should the request fail? Or send a nil but {{code_id}} and expect latest content? I is not, then that ' m thinking s a bug and we should probably fail the former run .
Jira (PDB-2421) High Availability Phase 3
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2421 High Availability Phase 3 Issue Type: Epic Assignee: Unassigned Created: 2016/02/10 4:09 PM Priority: Normal Reporter: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5734) Value of the key dependencies in the metadata.json of modules isn't checked
Title: Message Title Alexander Johnson assigned an issue to Anderson Mills Puppet / PUP-5734 Value of the key dependencies in the metadata.json of modules isn't checked Change By: Alexander Johnson Assignee: Anderson Mills Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5114) Retrieve content using content_uri
Title: Message Title Michael Smith commented on PUP-5114 Re: Retrieve content using content_uri The question should be resolved by PUP-5876; content_uri will only be set if there's a code_id. As far as implementation, I believe it will amount to diff --git a/lib/puppet/type/file/content.rb b/lib/puppet/type/file/content.rb index 8ccac99..06985fe 100644 --- a/lib/puppet/type/file/content.rb +++ b/lib/puppet/type/file/content.rb @@ -212,8 +212,12 @@ module Puppet end def get_from_puppet_source(source_or_content, &block) - source = source_or_content.metadata.source - request = Puppet::Indirector::Request.new(:file_content, :find, source, nil, :environment => resource.catalog.environment_instan
Jira (PUP-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5832 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types. Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5734) Value of the key dependencies in the metadata.json of modules isn't checked
Title: Message Title Alexander Johnson updated an issue Puppet / PUP-5734 Value of the key dependencies in the metadata.json of modules isn't checked Change By: Alexander Johnson Story Points: 2 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2420) Sync core retains the local query result seq head
Title: Message Title Russell Mull created an issue PuppetDB / PDB-2420 Sync core retains the local query result seq head Issue Type: Bug Assignee: Unassigned Created: 2016/02/10 3:59 PM Priority: Normal Reporter: Russell Mull Will have to change the api of query-fn to fix this; probably make it pass a thunk to the callback. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5876) Enable static catalogs by default
Title: Message Title Michael Smith assigned an issue to Michael Smith Puppet / PUP-5876 Enable static catalogs by default Change By: Michael Smith Assignee: Michael Smith Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2412) HA Product/Tech lead work
Title: Message Title Russell Mull assigned an issue to Russell Mull PuppetDB / PDB-2412 HA Product/Tech lead work Change By: Russell Mull Assignee: Russell Mull Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5851) FR - Puppet Lookup with Unicode Facts File
Title: Message Title
Ryan Gard commented on PUP-5851
Re: FR - Puppet Lookup with Unicode Facts File
-
FR
-
Functional Review
Verified as fixed with build 6522aa18d8338b9ffdc613ea7e750a633d4ec6d5.
Environment
Agent: CentOS 7 x64 (LINUX_SUT)
Test Case Reproduction Steps
Install Puppet Agent on LINUX_SUT.
Install and configure Puppet Server.
Create a hiera configuration "/etc/puppetlabs/code/hiera.yaml" with the content:
---
:backends:
- "yaml"
:logger: "console"
:hierarchy:
- "%{myfact}"
Jira (PUP-5832) 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types.
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5832 4.x Sensitive Type - Handle Sensitive data in manifests, logs, catalog, reports and resource types. Change By: Henrik Lindberg Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5545) Use rubocop in module generator
Title: Message Title Anderson Mills updated an issue Puppet / PUP-5545 Use rubocop in module generator Change By: Anderson Mills Story Points: 1 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5867) Static catalog acceptance: Why cached catalog is applied, Story PUP-5706
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5867 Static catalog acceptance: Why cached catalog is applied, Story PUP-5706 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5866) Static catalog acceptance: Per environment enable of static catalog, Story PUP-5705
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5866 Static catalog acceptance: Per environment enable of static catalog, Story PUP-5705 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5863) Static catalog acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5863 Static catalog acceptance: Old agents function as before, no static catalog, Story PUP-5532, PUP-5536 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5864) Static catalog acceptance: Agent file access only to /environments/*/modules/*/files/*, Story PUP-5534
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5864 Static catalog acceptance: Agent file access only to /environments/*/modules/*/files/*, Story PUP-5534 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5860) Static catalog acceptance: Catalog application stability against out-of-band updates, Story PUP-5526
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5860 Static catalog acceptance: Catalog application stability against out-of-band updates, Story PUP-5526 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5862) Static catalog acceptance: Request file content only when drift detected, Story PUP-5531
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5862 Static catalog acceptance: Request file content only when drift detected, Story PUP-5531 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5872) Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5872 Static catalog acceptance: Correlate all agent run reports to a catalog, Story PUP-5533 Change By: Steve Barlow Sprint: Client Triage 2016-03-09 (Burn CF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5700) Verify network compatibility
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5700 Verify network compatibility Change By: Steve Barlow Sprint: Client 2016- 02 03 - 24 09 (Burn FF CF ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5341) Tag fields in reports accidentally changed to Puppet::Util::TagSet objects
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5341 Tag fields in reports accidentally changed to Puppet::Util::TagSet objects Change By: Steve Barlow Sprint: Client 2016- 02 03 - 24 09 (Burn FF CF ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Steve Barlow updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Steve Barlow Sprint: Client 2016- 02 03 - 24 09 (Burn FF CF ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5688) puppet module tool needs to respect metadata version constraint
Title: Message Title Kylo Ginsberg commented on PUP-5688 Re: puppet module tool needs to respect metadata version constraint Ping Anderson Mills. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5689) puppet module tool to support passing in a version
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5689 puppet module tool to support passing in a version Change By: Kylo Ginsberg Scrum Team: Code Management Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5689) puppet module tool to support passing in a version
Title: Message Title Kylo Ginsberg commented on PUP-5689 Re: puppet module tool to support passing in a version Ping Anderson Mills Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5689) puppet module tool to support passing in a version
Title: Message Title Kylo Ginsberg assigned an issue to Anderson Mills Puppet / PUP-5689 puppet module tool to support passing in a version Change By: Kylo Ginsberg Assignee: Anderson Mills Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5688) puppet module tool needs to respect metadata version constraint
Title: Message Title Kylo Ginsberg assigned an issue to Anderson Mills Puppet / PUP-5688 puppet module tool needs to respect metadata version constraint Change By: Kylo Ginsberg Assignee: Anderson Mills Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5688) puppet module tool needs to respect metadata version constraint
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5688 puppet module tool needs to respect metadata version constraint Change By: Kylo Ginsberg Scrum Team: Code Management Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5288 acceptance: puppet ruby in windows should use the correct ssldir Change By: Steve Barlow Sprint: Client 2016- 02 03 - 24 09 (Burn FF CF ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5291) puppet device fails during SSH session closure
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5291 puppet device fails during SSH session closure Change By: Kylo Ginsberg Release Notes Summary: Fix "stream closed" problem with SSH transport to Cisco devices closing the session with the IO handles still open. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5291) puppet device fails during SSH session closure
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5291 puppet device fails during SSH session closure Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5291) puppet device fails during SSH session closure
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5291 puppet device fails during SSH session closure Change By: Steve Barlow Sprint: Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5682) yumrepo doesn't handle enabled => false correctly
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5682 yumrepo doesn't handle enabled => false correctly Change By: Steve Barlow Sprint: Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5121) Add profiling for file inlining
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5121 Add profiling for file inlining Change By: Steve Barlow Sprint: Client 2016- 02 03 - 24 09 (Burn FF CF ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5682) yumrepo doesn't handle enabled => false correctly
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-5682 yumrepo doesn't handle enabled => false correctly Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5291) puppet device fails during SSH session closure
Title: Message Title Kylo Ginsberg assigned an issue to qa Puppet / PUP-5291 puppet device fails during SSH session closure Change By: Kylo Ginsberg Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5878) acceptance: agent can reconnect after master failure
Title: Message Title Eric Thompson created an issue Puppet / PUP-5878 acceptance: agent can reconnect after master failure Issue Type: Task Assignee: qa-team Components: QA Created: 2016/02/10 3:12 PM Priority: Normal Reporter: Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs
Jira (PUP-5701) Compare files using checksum_value
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5701 Compare files using checksum_value Change By: Steve Barlow Sprint: Client 2016-02-10 , Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5703) Handle cached catalog and pluginsync inconsistencies
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5703 Handle cached catalog and pluginsync inconsistencies Change By: Steve Barlow Sprint: Client 2016-02-10 , Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-3077) When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment
Title: Message Title Steve Barlow updated an issue Puppet / PUP-3077 When puppet agent fails to retrieve catalog from master, cached catalog is used without regard for the puppet.conf-declared environment Change By: Steve Barlow Sprint: Client 2016-01-27, Client 2016-02-10 , Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5698) Inline directory metadata
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5698 Inline directory metadata Change By: Steve Barlow Sprint: Client 2016-02-10 , Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5617) agent stalls when connection with master is dropped
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Kylo Ginsberg Release Notes Summary: Previously the agent would stall indefinitely if the network connection to the master were to break unexpectedly for some reason. This change allows the socket with the master to get closed and the agent to terminate cleanly.an error, rather than waiting forever. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5122) Acceptance tests for direct puppet running from cache
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5122 Acceptance tests for direct puppet running from cache Change By: Steve Barlow Sprint: Client 2016-02-10 , Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5699) Inline symlink metadata
Title: Message Title Steve Barlow updated an issue Puppet / PUP-5699 Inline symlink metadata Change By: Steve Barlow Sprint: Client 2016-02-10 , Client 2016-02-24 (Burn FF) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5617) agent stalls when connection with master is dropped
Title: Message Title Kylo Ginsberg updated an issue Puppet / PUP-5617 agent stalls when connection with master is dropped Change By: Kylo Ginsberg Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2368) Version the CLI subcommands separately
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2368 Version the CLI subcommands separately Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2224) Create PDB CLI full stack tests
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2224 Create PDB CLI full stack tests Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2218) Spike extracting the metadata.json file from exports
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2218 Spike extracting the metadata.json file from exports Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2339) POST queries to PuppetDB
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2339 POST queries to PuppetDB Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2228) Create "examples repo" and tie that into PDB CLI manpage creation
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2228 Create "examples repo" and tie that into PDB CLI manpage creation Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2385) Stream pretty-print responses in CLI
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2385 Stream pretty-print responses in CLI Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2225) Create status subcommand
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2225 Create status subcommand Change By: Andrew Roetker Fix Version/s: PDB CLI 0.1.0 Fix Version/s: PDB CLI 0.2.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Steve Barlow updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Steve Barlow Sprint: Language Triage Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2419) (maint) Update to leatherman 0.3.7
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2419 (maint) Update to leatherman 0.3.7 Change By: Andrew Roetker Scope Change Category: Adopted Scope Change Reason: Leatherman update, easy fix Fix Version/s: PDB CLI 0.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2419) (maint) Update to leatherman 0.3.7
Title: Message Title gepetto-bot updated an issue PuppetDB / PDB-2419 (maint) Update to leatherman 0.3.7 Change By: gepetto-bot Sprint: PuppetDB 2016-02-24 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-2419) (maint) Update to leatherman 0.3.7
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-2419 (maint) Update to leatherman 0.3.7 Issue Type: Bug Assignee: Unassigned Created: 2016/02/10 2:55 PM Priority: Normal Reporter: gepetto-bot This commit removes pod2man from our tree as it was added to leatherman 0.3.7 to be shared. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
