Jira (PUP-3049) mailalias always performs a "change" when value has a comma
Title: Message Title LeLutin updated an issue Puppet / PUP-3049 mailalias always performs a "change" when value has a comma Change By: LeLutin Summary: mailalias chokes on commas always performs a "change" when value has a comma 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-3049) mailalias chokes on commas
Title: Message Title LeLutin updated an issue Puppet / PUP-3049 mailalias chokes on commas Change By: LeLutin Affects Version/s: PUP 4.3.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-3049) mailalias chokes on commas
Title: Message Title
LeLutin commented on PUP-3049
Re: mailalias chokes on commas
I guess this is not getting any attention because 2.7 is EOL now.
I've just tested this against puppet-agent 1.3.2 on debian jessie and I'm still seeing the same behaviour. the alias gets created but puppet "changes" it on each run:
root@jessie:~# /opt/puppetlabs/bin/puppet apply -e "mailalias { 'redmine': recipient => '|/usr/share/redmine/extra/mail_handler/sub-mailhandler.py -e redm...@redmine.example.com -- /usr/share/redmine/extra/mail_handler/rdm-mailhandler.rb --url https://redmine.example.com --key somerandomalphanumstring --no-check-certificate --unknown-user accept --no-permission-check --allow-override project,tracker,category,priority,status' }"
Notice: Compiled catalog for jessie.vagrantup.com in environment production in 0.06 seconds
Notice: /Stage[main]/Main/Mailalias[redmine]/recipient: recipient changed '|/usr/share/redmine/extra/mail_handler/sub-mailhandler.py -e redm...@redmine.example.com -- /usr/share/redmine/extra/mail_handler/rdm-mailhandler.rb --url https://redmine.example.com --key somerandomalphanumstring --no-check-certificate --unknown-user accept --no-permission-check --allow-override project,tracker,category,priority,status' to '|/usr/share/redmine/extra/mail_handler/sub-mailhandler.py -e redm...@redmine.example.com -- /usr/share/redmine/extra/mail_handler/rdm-mailhandler.rb --url https://redmine.example.com --key somerandomalphanumstring --no-check-certificate --unknown-user accept --no-permission-check --allow-override project,tracker,category,priority,status'
Notice: Applied catalog in 0.08 seconds
root@jessie:~# /opt/puppetlabs/bin/puppet apply -e "mailalias { 'redmine': recipient => '|/usr/share/redmine/extra/mail_handler/sub-mailhandler.py -e redm...@redmine.example.com -- /usr/share/redmine/extra/mail_handler/rdm-mailhandler.rb --url https://redmine.example.com --key somerandomalphanumstring --no-check-certificate --unknown-user accept --no-permission-check --allow-override project,tracker,category,priority,status' }"
Jira (PDOC-178) @api private not showing up in generated docs
Title: Message Title LeLutin commented on PDOC-178 Re: @api private not showing up in generated docs Henrik Lindberg I'm curious why this was done by design. If the module developers indicate that a class should be private, then it'd be nice if it showed up in the generated documentation.. but there might be some things that I haven't considered. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDOC-226) Support for Type Aliases
Title: Message Title LeLutin commented on PDOC-226 Re: Support for Type Aliases I'd like to back that request up. I just found out that the documentation pages generated by puppet strings shows the types for class and defined type params, but their definitions are nowhere to be found when you want to know what they stand for. They could be listed as pages in the same section as ruby custom types which are already supported, or if this confuses things too much, they could also have their own section named "Type aliases". The very least would be to see what the type is an alias of (e.g. show the definition in the html page). then, like Henrik suggested, it would be great if all uses of this type in class and defined type params would link to the corresponding page Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-9603) Documentation and/or spec for syntax checkers in heredocs out of date
Title: Message Title LeLutin created an issue Puppet / PUP-9603 Documentation and/or spec for syntax checkers in heredocs out of date Issue Type: Bug Assignee: Unassigned Created: 2019/04/04 1:01 PM Priority: Normal Reporter: LeLutin Puppet Version: 6.4 Puppet Server Version: OS Name/Version: The document visible on https://github.com/puppetlabs/puppet-specifications/blob/master/language/heredoc.md#additional-semantics specifies a syntax for syntax checking of the contents of a heredoc string. (e.g. `@(END:_javascript_)` ) However official documentation has no mention of this: https://puppet.com/docs/puppet/6.4/lang_data_string.html#syntax I was told on IRC that the herdoc syntax for string content syntax checker was an experimental thing. helindbe then asked me to open this ticket so that documentation can be made up to date. Add Comment
Jira (PDB-4422) initial migration at first start fails puppetdb hangs.
Title: Message Title LeLutin commented on PDB-4422 Re: initial migration at first start fails puppetdb hangs. Hi there! for what it's worth, we've just hit exactly the same problem with puppet 6.2.0 paired with postgresql 11.4 on debian buster (using debian packages for both). Downgrading to 11.3 lets puppetdb finish its schema upgrade, so the same change that happened in the 9.6.x branch must have also happened somewhere between 11.3 and 11.4 We're going to try importing the fix for puppetdb from one of the versions mentioned above to see if it fixes the issue for the 11.x branch of postgresql, too. The debian bug report is here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=932135 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.313863.1561448596000.16202.1563213600550%40Atlassian.JIRA. For more options, visit https://groups.google.com/d/optout.
