Jira (PUP-6542) Group resource emits misleading change notification with auth_membership => false
Title: Message Title Ethan Brown updated an issue Puppet / PUP-6542 Group resource emits misleading change notification with auth_membership => false Change By: Ethan Brown Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Moses Mendoza assigned an issue to Tim Purkerson Puppet / PUP-6716 Error when purging local users on Windows Change By: Moses Mendoza Assignee: Moses Mendoza Tim Purkerson Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Moses Mendoza updated an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Moses Mendoza Affects Version/s: PUP 4.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Moses Mendoza moved an issue Puppet / PUP-6716 Error when purging local users on Windows Change By: Moses Mendoza Affects Version/s: PE 3.8.1 Component/s: Windows Component/s: Windows Key: PE PUP - 13126 6716 Project: Puppet Enterprise [Internal] Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving
Jira (PUP-6716) Error when purging local users on Windows
Title: Message Title Moses Mendoza commented on PUP-6716 Re: Error when purging local users on Windows Moved to PUP project Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1508) End-to-end POC for string externalization in Facter
Title: Message Title Larissa Lane updated an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Change By: Larissa Lane Labels: i18n Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Change By: Larissa Lane Labels: i18n Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1508) End-to-end POC for string externalization in Facter
Title: Message Title Larissa Lane created an issue Facter / FACT-1508 End-to-end POC for string externalization in Facter Issue Type: Task Assignee: Unassigned Created: 2016/09/19 4:57 PM Priority: Normal Reporter: Larissa Lane Wrap one simple string* in the facter repo with the _() gettext function Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese Add the facter repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa) When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the facter repo (Larissa) Add a setting to check the user's locale and display supported languages or default to English Test on an OS that has the environment set to Japanese Consider stripping the line numbers out of the POT file to reduce churn *Simple string means a string that isn't composed or concatenated Talk to Libby Molina about the CI jobs she is creating for Clojure and _javascript_ Out of scope is an opt-out option to turn off localized strings, but this should be considered for another ticket. Add Comment
Jira (PUP-6715) End-to-end POC for string externalization in Puppet
Title: Message Title Larissa Lane created an issue Puppet / PUP-6715 End-to-end POC for string externalization in Puppet Issue Type: Task Assignee: Unassigned Created: 2016/09/19 4:57 PM Priority: Normal Reporter: Larissa Lane Wrap one simple string* in the puppet repo with the _() gettext function Create a CI job that uses the gettext-setup gem tooling to generate a POT file, and a PO file for Japanese Add the puppet repo to the Transifex integration and test that the PO file is automatically pulled into Transifex when updates are made to it (Larissa) When the PO file reaches 100% translated and reviewed in Transifex, it is automatically updated in the puppet repo (Larissa) Add a setting to check the user's locale and display supported languages or default to English Test on an OS that has the environment set to Japanese Consider stripping the line numbers out of the POT file to reduce churn *Simple string means a string that isn't composed or concatenated Talk to Libby Molina about the CI jobs she is creating for Clojure and _javascript_ Out of scope is an opt-out option to turn off localized strings, but this should be considered for another ticket. Add Comment
Jira (PUP-6474) Incorporate gettext_setup gem into puppet
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6474 Incorporate gettext_setup gem into puppet Change By: Larissa Lane Team: Agent & Platform Goal here is to incorporate the gettext_setup gem into such that we can externalize a single string in puppet and produce a pot file (presumably from a rake task). Does not include externalizing the string or producing the pot file. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Larissa Lane Team: Agent & Platform Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-348) Facter should provide a convenient way to cache values
Title: Message Title Glenn Sarti assigned an issue to Maggie Dreyer Facter / FACT-348 Facter should provide a convenient way to cache values Change By: Glenn Sarti Assignee: Glenn Sarti Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6067) Pip3 provider does not include features from Pip
Title: Message Title Brandon High assigned an issue to Brandon High Puppet / PUP-6067 Pip3 provider does not include features from Pip Change By: Brandon High Assignee: Brandon High Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6067) Pip3 provider does not include features from Pip
Title: Message Title Brandon High assigned an issue to Unassigned Puppet / PUP-6067 Pip3 provider does not include features from Pip Change By: Brandon High Assignee: Brandon High Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6709) Escaped characters are handled differently with future parser enabled
Title: Message Title Henrik Lindberg commented on PUP-6709 Re: Escaped characters are handled differently with future parser enabled You can say that: In future parser, and 4.x single quoted and double quoted strings behave the same way in that backslashes must be escaped to remove their special meaning. In 3.x without future parser there were bugs in the implementation that made it impossible to construct certain single quoted strings. In this particular example, each occurrence of . and * should be replaced with a backslash followed by the captured character. Since the string is given to regsubst, and it also uses backslash as the escape mechanism we must use double the amount of backslashes - 4 in total to get two in the string, which means one as a replacement. For the captured part we need \1 in the string, which can be written as '\1' or '1' Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3050) Implementation
Title: Message Title Ryan Senior commented on PDB-3050 Re: Implementation Karel Brezina can we get some description here? I don't know what this ticket covers and it will be difficult to reconcile when we get ready to release PDB. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Tobias Wolter commented on PUP-6713 Re: Vim should highlight data types in a class definition Reporter here, spent a couple of minutes trying to fix it with setting a syntax region that recognizes the brackets after the data type, but that didn't seem to lead anywhere due to lack of vimfu on my side. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Paul Anderson updated an issue Puppet / PUP-6713 Vim should highlight data types in a class definition Change By: Paul Anderson Attachment: Screen Shot 2016-09-19 at 15.24.07.png Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title
Paul Anderson commented on PUP-6713
Re: Vim should highlight data types in a class definition
Additional info:
User provided a sample use case trying to validate paths. Here is a sample:
class vim_syntax
Unknown macro: { Pattern[/A[A-Za-z_-1-9 ./] $path_to_somewhere Pattern[/A[A-Za-z_-1-9 ./] $path_to_somewhere_else String $my_string }
For convenience, here is the regex in action: http://rubular.com/r/yPZ9EQsIBn
Suspect code is here: https://github.com/rodjek/vim-puppet/blob/d881b93dc4a8ed1374ad44439aeeb47808a6b91a/syntax/puppet.vim#L19-L28
Add Comment
This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6612) Scope effort for i18n string externalization
Title: Message Title Larissa Lane updated an issue Puppet / PUP-6612 Scope effort for i18n string externalization Change By: Larissa Lane Categorize strings in Puppet that require externalization for i18n, e.g. with aautomated tool that can be expanded later to check PRs and integrated with CIfor all Ruby projects. Categorize strings as basic static strings, simple formattedstrings, strings requiring pluralization and/or additional translation context, complexcases that may require manual intervention, and strings that should not betranslated. Investigate removing line numbers from the POT file to reduce churn. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Paul Anderson updated an issue Puppet / PUP-6713 Vim should highlight data types in a class definition Change By: Paul Anderson Environment: https://github.com/puppetlabs/puppet-syntax-vim also https://github.com/rodjek/vim-puppet on Vim 7 , code that includes .4 on Ubuntu/Debian Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3057) release 4.2.3 to PE davis only
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3057 release 4.2.3 to PE davis only Issue Type: Task Assignee: Unassigned Created: 2016/09/19 2:03 PM Priority: Normal Reporter: Wyatt Alt Davis needs the ezbake bump. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) --
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Paul Anderson commented on PUP-6713 Re: Vim should highlight data types in a class definition I started a private e-mail chain with the user to get some additional details that were not in the tweets. I will post updates as they become available. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6714) PCore generation omits information about capability types
Title: Message Title Nick Lewis created an issue Puppet / PUP-6714 PCore generation omits information about capability types Issue Type: Bug Assignee: Unassigned Created: 2016/09/19 1:42 PM Priority: Major Reporter: Nick Lewis Given a capability resource type definition: Puppet::Type.newtype :cap, :is_capability => true do newparam :name, :is_namevar => true newparam :value end
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Eric Sorenson assigned an issue to Lindsey Smith Puppet / PUP-6713 Vim should highlight data types in a class definition Change By: Eric Sorenson Assignee: Eric Sorenson Lindsey Smith Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Eric Sorenson updated an issue Puppet / PUP-6713 Vim should highlight data types in a class definition Change By: Eric Sorenson Team: Puppet Developer Support Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Eric Sorenson commented on PUP-6713 Re: Vim should highlight data types in a class definition Lindsey Smith the vim syntax highliter plugin is a popular development tool and it's languished with respect to new language features. Something for team to consider. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6713) Vim should highlight data types in a class definition
Title: Message Title Paul Anderson created an issue Puppet / PUP-6713 Vim should highlight data types in a class definition Issue Type: New Feature Affects Versions: PUP 4.6.2 Assignee: Eric Sorenson Components: Community Created: 2016/09/19 1:13 PM Environment: https://github.com/puppetlabs/puppet-syntax-vim also https://github.com/rodjek/vim-puppet on Vim 7, code that includes Priority: Normal Reporter: Paul Anderson Source: @towo on Twitter https://twitter.com/towo/status/777600724985315328 Does anybody have a puppet.vim that actually does highlighting of data types in a class definition? Pattern[...] breaks a lot of things.— Tobias Wolter (@towo) September 18, 2016 @puppetize You lot maybe? Even your officialish repo (https://t.co/lSVtsu6J77) is broken in that regard.— Tobias Wolter (@towo) September 18, 2016
Jira (PUP-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Erik Hansen commented on PUP-6711 Re: Puppet lookup doesn't know about custom facts I was testing on a PE 2016.2.0 Master with this repro case. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6703) Minor improvement to agent failover test (originally PUP-6383)
Title: Message Title Geoff Nichols assigned an issue to Maggie Dreyer Puppet / PUP-6703 Minor improvement to agent failover test (originally PUP-6383) Change By: Geoff Nichols Assignee: Branan Riley Maggie Dreyer Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2779) stockpile: satisfy ourselves that the durability approach is reliable enough, or adjust it
Title: Message Title Rob Browning assigned an issue to Rob Browning PuppetDB / PDB-2779 stockpile: satisfy ourselves that the durability approach is reliable enough, or adjust it Change By: Rob Browning Assignee: Rob Browning Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2779) stockpile: satisfy ourselves that the durability approach is reliable enough, or adjust it
Title: Message Title Rob Browning updated an issue PuppetDB / PDB-2779 stockpile: satisfy ourselves that the durability approach is reliable enough, or adjust it Change By: Rob Browning Summary: stockpile: satisfy ourselves that the durability approach is reliable enough , or adjust it Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6457) Mount resources could handle invalid options better
Title: Message Title Geoff Nichols assigned an issue to Kurt Wall Puppet / PUP-6457 Mount resources could handle invalid options better Change By: Geoff Nichols Assignee: qa Kurt Wall Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Henrik Lindberg commented on PUP-6712 Re: Arrays in resource chaining That would be fixable though (as opposed to making it possible to get a collector inside an array). It would still not allow filtering - i.e. you could reference individual resources or "all" of that type. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-718) Allow for disabling certain facts within Facter
Title: Message Title Glenn Sarti assigned an issue to Stan Duffy Facter / FACT-718 Allow for disabling certain facts within Facter Change By: Glenn Sarti Assignee: qa Stan Duffy Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3056) periodic acceptance tests broken on master and stable
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-3056 periodic acceptance tests broken on master and stable Issue Type: Bug Assignee: Unassigned Created: 2016/09/19 8:35 AM Priority: Normal Reporter: Wyatt Alt On master debian 8 appears to be using a broken ruby. Host 'debian8-64-1' exited with 1 running: gem install i18n -v 0.6.11 Last 10 lines of output were: ERROR: Loading command: install (LoadError)
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn commented on PUP-6712 Re: Arrays in resource chaining Nope It lets you declare the variable $foo = [ File, Service ] But when you try and use it in a chain $foo -> Notify<||> Error: Could not find resource 'File[]' for relationship on 'Notify[bar]' on node localhost.localdomain Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Henrik Lindberg commented on PUP-6712 Re: Arrays in resource chaining The reference to File would mean all resources of that type (but I am not sure if that works). Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Henrik Lindberg commented on PUP-6712 Re: Arrays in resource chaining True, [ File <|| > ] will not work. Have you tried: [ File ] And it needs to be in an array assigned to a variable. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn commented on PUP-6712 Re: Arrays in resource chaining Henrik Lindberg That might work for individual resource references (eg Foo['bar']) but for using collector syntax chaining this wouldn't work $foo = [ File<||> ] Error: Could not parse for environment production: Invalid use of _expression_. A Virtual Query does not produce a value at /root/foo.pp:1:10 on node localhost.localdomain So your pattern is nice, but it wouldn't help these particular use cases. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group,
Jira (PUP-6711) Puppet lookup doesn't know about custom facts
Title: Message Title Henrik Lindberg commented on PUP-6711 Re: Puppet lookup doesn't know about custom facts Erik Hansen Which version of puppet? We recently made the lookup use the facts for the local node on which you are running the command available. Earlier you would always have to specify the set of facts you wanted to use by referencing a file with those facts on the command line. Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6712
Arrays in resource chaining
Change By:
Henrik Lindberg
Team:
Puppet Developer Support
Sprint:
PDS Triage
There are a number of use cases where lots of different resource types need to require and notify the same things... eg{code}Foo <||> -> Resource_one<||> ~> Bar<||>Foo <||> -> Resource_two<||> ~> Bar<||>Foo <||> -> Resource_three<||> ~> Bar<||>Foo <||> -> Resource_four<||> ~> Bar<||>{code}A couple of real world examples of this are:https://github.com/crayfishx/puppet-firewalld/blob/3.1.4/manifests/init.pp#L163-L169https://github.com/voxpupuli/puppet-splunk/blob/4.0.0/manifests/init.pp#L189-L248The current chaining syntax is quite repetitive, it would make more sense if you could include arrays in resource chaining, so this:{code} Service['firewalld'] -> Firewalld_zone <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_rich_rule <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_service <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_port <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_direct_chain <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_direct_rule <||> ~> Exec['firewalld::reload'] Service['firewalld'] -> Firewalld_direct_passthrough <||> ~> Exec['firewalld::reload']{code}Could be written more cleanly as something like:{code} Service['firewalld'] -> [ Firewalld_zone <||>, Firewalld_rich_rule <||>, Firewalld_service <||>, Firewalld_port <||>, Firewalld_direct_chain <||>, Firewalld_direct_rule <||>, Firewalld_direct_passthrough <||> ] ~> Exec['firewalld::reload']{code}So a chain to an array of references will apply the relationship to all members of the array.
Add Comment
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Henrik Lindberg commented on PUP-6712 Re: Arrays in resource chaining The precedence of the collector _expression_ and the fact that it does not produce a value that can be used in the language (and hence not be placed as a data element in an Array) makes the suggested syntax and semantics impossible to achieve. I have not tried, but I think you can assign an array of references to a variable and use that variable in the chain. The array can contain references to resource types, and to individual resources - something like this: $x = [ ResourceA, ResourceB['this_b']] Service['some_service'] -> $x -> Exec['some_exec'] Would something like that work for you? Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
Jira (PDB-2730) Command Processing 2.0
Title: Message Title Karen Van der Veer updated an issue PuppetDB / PDB-2730 Command Processing 2.0 Change By: Karen Van der Veer Epic Colour: ghx-label- 1 4 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6712) Arrays in resource chaining
Title: Message Title Craig Dunn created an issue Puppet / PUP-6712 Arrays in resource chaining Issue Type: New Feature Assignee: Unassigned Components: Language Created: 2016/09/19 7:05 AM Priority: Normal Reporter: Craig Dunn There are a number of use cases where lots of different resource types need to require and notify the same things... eg Foo <||> -> Resource_one<||> ~> Bar<||> Foo <||> -> Resource_two<||> ~> Bar<||> Foo <||> -> Resource_three<||> ~> Bar<||>
Jira (PUP-2782) Yumrepo target attribute does not work
Title: Message Title Matthew Gyurgyik updated an issue Puppet / PUP-2782 Yumrepo target attribute does not work Change By: Matthew Gyurgyik Affects Version/s: PUP 4.6.2 Add Comment This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
