Jira (PUP-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Charlie Sharpsteen commented on PUP-9040 Re: puppet lookup command returns warning with poor formatting I suppose the question would be whether there are any practical consequences to this. I can think of cases where having the message on one line makes parsing easier, but having the file and line number separated and indented stack-trace style is nicer for display. All in all, if it is just a superficial formatting issue with no clear "right way" to do it, then there are many other things that could be fixed instead. 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-2169) Not possible to manage SELinux file contexts via puppet in a sane way
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-2169 Not possible to manage SELinux file contexts via puppet in a sane way Change By: Adam Bottchen CS Severity: 2 - Annoyance CS Business Value: 1 - ? CS Frequency: 1 - 1-5% of Customers 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-9337) Puppet sets permissions for Puppet files every run
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-9337 Puppet sets permissions for Puppet files every run Change By: Adam Bottchen CS Priority: Needs Priority Reviewed 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 (BOLT-737) Bolt documentation dissonance with acronyms and audience assumptions
Title: Message Title Kate Lopresti assigned an issue to Melissa Amos Puppet Task Runner / BOLT-737 Bolt documentation dissonance with acronyms and audience assumptions Change By: Kate Lopresti Assignee: Kate Lopresti Melissa Amos 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-9336) Ensure provider suitability is always lazily evaluated
Title: Message Title
Enis Inan commented on PUP-9336
Re: Ensure provider suitability is always lazily evaluated
Couldn't we modify the boolean confines {true} and {false} to optionally take in a block and case the value on that? This would look something like:
confine :true,
OR
confine :true,
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
Jira (PUP-9113) Unable to manage services with what looks like HyperV installed on Windows
Title: Message Title Sean McDonald commented on PUP-9113 Re: Unable to manage services with what looks like HyperV installed on Windows This is fixed in puppet 5.5.7 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-9113) Unable to manage services with what looks like HyperV installed on Windows
Title: Message Title Sean McDonald updated an issue Puppet / PUP-9113 Unable to manage services with what looks like HyperV installed on Windows Change By: Sean McDonald Fix Version/s: PUP 5.5.7 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 (BOLT-969) bolt-server clears its tmpdir during cache purging
Title: Message Title Cas Donoghue assigned an issue to Cas Donoghue Puppet Task Runner / BOLT-969 bolt-server clears its tmpdir during cache purging Change By: Cas Donoghue Assignee: Cas Donoghue 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 (FACT-1895) Executable and Structured data facts in .txt format to allow Boolean conversion
Title: Message Title Branan Riley commented on FACT-1895 Re: Executable and Structured data facts in .txt format to allow Boolean conversion As far as changing how we parse key=value, I think we'd probably consider that a breaking change - the types of facts are sort of part of the "API" with puppet manifests, and changing those types can break compiles 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 (FACT-1895) Executable and Structured data facts in .txt format to allow Boolean conversion
Title: Message Title Branan Riley commented on FACT-1895 Re: Executable and Structured data facts in .txt format to allow Boolean conversion JSON and YAML formatting are already supported in executable facts (see FACT-1356 and FACT-1653). We have a ticket to update the documentation to reflect that. It ended up in the release notes, but fell through the cracks for updating the main documentation. FACT-1876 tracks us making explicit in the docs how executable facts work when outputting structured data. 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 (PDB-4204) (WIP) PuppetDB alpine image from source
Title: Message Title gepetto-bot created an issue PuppetDB / PDB-4204 (WIP) PuppetDB alpine image from source Issue Type: Bug Assignee: Unassigned Created: 2018/12/06 1:56 PM Priority: Normal Reporter: gepetto-bot 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
Jira (PDB-3747) PDB holds summary query transactions open during long syncs
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3747 PDB holds summary query transactions open during long syncs Change By: Adam Bottchen Labels: cstop10 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-9345) Update documentation to reflect that Resource defaults since 5.0 depends on evaluation-order
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9345 Update documentation to reflect that Resource defaults since 5.0 depends on evaluation-order Change By: Henrik Lindberg Summary: Update documentation to reflect that Resource defaults are no longer since 5.0 depends on evaluation-order independent 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-9345) Resource defaults are no longer evaluation-order independent
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9345 Resource defaults are no longer evaluation-order independent Change By: Henrik Lindberg Component/s: DOCS 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-9345) Resource defaults are no longer evaluation-order independent
Title: Message Title Henrik Lindberg assigned an issue to Jean Bond Puppet / PUP-9345 Resource defaults are no longer evaluation-order independent Change By: Henrik Lindberg Assignee: Jean Bond 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-9345) Resource defaults are no longer evaluation-order independent
Title: Message Title Henrik Lindberg commented on PUP-9345 Re: Resource defaults are no longer evaluation-order independent This was a deliberate breaking change in Puppet 5.0.0 that apparently did not make it into documentation as it should. I am not 100% sure if there were changes in late 4.x series that caused order to be different - we were fixing issues and ran into conflicting requirements. The change was deliberate in Puppet 5 because of the conflicting requirements (impossible to meet at the same time) and the conclusion was that it was more valuable to support the other use cases instead of the faux declarative "the default can be set at any time". This started in PUP-25, and was fixed in PUP-7484 where some bugs were found. I am taking this to be a ticket to fix the documentation. Puppet will eagerly bind default values in effect at the time a resource _expression_ is evaluated (i.e in "evaluation order"). We are not going to change it back to how this worked before Puppet 5. Ping Jean Bond - the documentation should change to say something like: "Resource Defaults are evaluation order dependant as they are assigned to a created resource when a resource _expression_ is evaluated (declared for inclusion in the catalog). The default values in effect for the type at that point in time are used." 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
Jira (PDB-3526) Add online index rebuild capability to PuppetDB
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3526 Add online index rebuild capability to PuppetDB Change By: Adam Bottchen Labels: cstop10 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-9345) Resource defaults are no longer evaluation-order independent
Title: Message Title
Steve Traylen commented on PUP-9345
Re: Resource defaults are no longer evaluation-order independent
It's probably obvious but should have said:
File{
mode => '0777',
}
file{'/tmp/junk.txt':
ensure => file,
content => "content\n",
}
with the default specified first works just fine.
Add Comment
Jira (PUP-9345) Resource defaults are no longer evaluation-order independent
Title: Message Title
Steve Traylen updated an issue
Puppet / PUP-9345
Resource defaults are no longer evaluation-order independent
Change By:
Steve Traylen
*Puppet Version: 6.0.4 *Puppet Server Version: n/a *OS Name/Version: CentOS 7.From the [docs|https://puppet.com/docs/puppet/5.5/lang_defaults.html#behavior]:Resource defaults are evaluation-order independent — that is, a default affects resource declarations written both above and below it.This is no longer the case since release 4.10.5.*Desired Behavior:*puppet apply the following manifest:{noformat}file{'/tmp/junk.txt': ensure => present, content => "junk\n",}File{ mode => '0777',}{noformat}This should result in a file with ownership mode '0777'.Running with puppet 4.9.4:{noformat}Notice: /Stage[main]/Main/File[/tmp/file.txt]/ensure: defined content as '{md5}477fbe8ae54fcb5effa415227ec05cb4'Notice: Applied catalog in 0.07 seconds-rwxrwxrwx. 1 straylen c3 13 Dec 6 20:36 /tmp/file.txt{noformat}*Actual Behavior:*Running with current HEAD 6.0.4+{noformat}rm /tmp/file.txt && bundle exec puppet apply ~/tmp/apply.pp && ls -l /tmp/file.txtNotice: Compiled catalog for aiadm83.cern.ch in environment production in 0.05 secondsNotice: /Stage[main]/Main/File[/tmp/file.txt]/ensure: defined content as '{md5}477fbe8ae54fcb5effa415227ec05cb4'Notice: Applied catalog in 0.32 seconds-rw-r--r--. 1 straylen c3 13 Dec 6 20:35 /tmp/file.txt{noformat}The file is not '0777' as the defaults were never applied.Running a git bisect the patch that introduced this behaviour is[https://github.com/puppetlabs/puppet/commit/38413cd78c61fe34d2ee343ef773a07b4786f65a]Note the same behaviour is observed in both a simple manifest like above or if global default parameters are attempted via the site.pp file.
Add Comment
Jira (PUP-9345) Resource defaults are no longer evaluation-order independent
Title: Message Title
Steve Traylen created an issue
Puppet / PUP-9345
Resource defaults are no longer evaluation-order independent
Issue Type:
Bug
Affects Versions:
PUP 6.0.4
Assignee:
Unassigned
Components:
Compiler
Created:
2018/12/06 11:43 AM
Priority:
Normal
Reporter:
Steve Traylen
*Puppet Version: 6.0.4 *Puppet Server Version: n/a *OS Name/Version: CentOS 7. From the docs: Resource defaults are evaluation-order independent — that is, a default affects resource declarations written both above and below it. This is no longer the case since release 4.10.5. Desired Behavior: puppet apply the following manifest:
file{'/tmp/junk.txt':
ensure => present,
content => "junk\n",
}
Jira (PUP-7744) Puppet CA's CRL is prone to duplicate entries
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-7744 Puppet CA's CRL is prone to duplicate entries Change By: Adam Bottchen Labels: ca cstop10 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 (PDB-3745) Various tables in the puppetdb database get autovacuumed too frequently
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3745 Various tables in the puppetdb database get autovacuumed too frequently Change By: Adam Bottchen Labels: cstop10 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-271) unicode space causes oddly formatted output / missing text
Title: Message Title William Yardley updated an issue Puppet Strings / PDOC-271 unicode space causes oddly formatted output / missing text Change By: William Yardley Attachment: puppet_example.tar.gz 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-271) unicode space causes oddly formatted output / missing text
Title: Message Title William Yardley created an issue Puppet Strings / PDOC-271 unicode space causes oddly formatted output / missing text Issue Type: Bug Assignee: Unassigned Components: CLI Created: 2018/12/06 11:05 AM Priority: Major Reporter: William Yardley Ewoud Kohl van Wijngaarden noticed that https://github.com/voxpupuli/puppet-rabbitmq/blob/24abdd6b9934167d10f7ebc30fbc07cd654e6f81/manifests/init.pp#L192 had an odd unicode character that renders as a space for me (even with cat -vet) (https://github.com/voxpupuli/puppet-rabbitmq/pull/744#issuecomment-444942295 ) This seemed to be causing other weird spacing / rendering as well od -c shows 0026020a d m i n f i l e \n # ** @ p 0026040a r a m l o o p b a c k _ u s 0026060e r s T h i s o p t i o n
Jira (PUP-7092) Documentation on Hiera 3.2 references the wrong documentation
Title: Message Title Jean Bond commented on PUP-7092 Re: Documentation on Hiera 3.2 references the wrong documentation No, it wasn't fixed yet. It is now, though. Thanks for the ping on it, Henrik Lindberg! 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 (BOLT-982) Create new plan executor application with /plan/run endpoint
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-982 Create new plan executor application with /plan/run endpoint Change By: Cas Donoghue Fix Version/s: BOLT Next 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 (BOLT-335) Boltlib functions should have configurable timeouts
Title: Message Title Adam Bottchen updated an issue Puppet Task Runner / BOLT-335 Boltlib functions should have configurable timeouts Change By: Adam Bottchen Labels: cstop10 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-1974) Theme: Sensitive Data in Catalogs
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-1974 Theme: Sensitive Data in Catalogs Change By: Adam Bottchen Labels: cstop10 support tse 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 (PDB-3300) Add command for deleting node data
Title: Message Title Adam Bottchen updated an issue PuppetDB / PDB-3300 Add command for deleting node data Change By: Adam Bottchen Labels: AWS1 backup-restore cstop10 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-3263) Architecture Parameter for Package Resource
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Adam Bottchen Labels: cstop10 customer linux package type_and_provider yum 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-8094) Lookup ignores environment from the classifier when using rule with trusted facts
Title: Message Title Adam Bottchen updated an issue Puppet / PUP-8094 Lookup ignores environment from the classifier when using rule with trusted facts Change By: Adam Bottchen Labels: cstop10 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Adam Bottchen commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows I have removed it from the CS Top 10. 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Thomas Kishel commented on PUP-6134 Re: Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Oh, yes. There are other issues with more activity without a workaround. 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-6134) Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows
Title: Message Title Geoff Nichols updated an issue Puppet / PUP-6134 Unable to install a Ruby gem to non-Puppet Ruby stack using the package resource type on Windows Change By: Geoff Nichols Fix Version/s: PUP 6.y Fix Version/s: PUP 7.0.0 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 (BOLT-1019) Ability to use Puppet Agent Certificate during catalog execution
Title: Message Title Nick Maludy commented on BOLT-1019 Re: Ability to use Puppet Agent Certificate during catalog execution I just noticed another one too (maybe related). The $environment variable is set to "bolt_catalog". So, when `theforeman/puppet` rendered the config template for /etc/puppetlabs/puppet/puppet.conf it set [agent] environment = bolt_catalog I think this is less of an issue, but it may be related? 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
Jira (BOLT-1019) Ability to use Puppet Agent Certificate during catalog execution
Title: Message Title Michael Smith commented on BOLT-1019 Re: Ability to use Puppet Agent Certificate during catalog execution Seems like we can provide an option to let it use the default Puppet config location, which should include ssl. 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-3263) Architecture Parameter for Package Resource
Title: Message Title Geoff Nichols assigned an issue to Adam Bottchen Puppet / PUP-3263 Architecture Parameter for Package Resource Change By: Geoff Nichols Assignee: Branan Riley Adam Bottchen 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 (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Melissa Amos commented on BOLT-940 Re: apply_prep doesn't work with pcp nodes and released puppet_agent Draft docs are up: http://docs-internal.puppet.com/docs/bolt/dev/bolt_new_features.html#run-apply-with-pe-orchestrator-without-installing-puppet-agent-module-1-5-0 http://docs-internal.puppet.com/docs/bolt/dev/bolt_configure_orchestrator.html#install-the-bolt-module-in-a-pe-environment 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 (BOLT-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Melissa Amos commented on BOLT-510 Re: I want to name nodes in inventory separately from their URL/hostname Draft docs are up: http://docs-internal.puppet.com/docs/bolt/dev/bolt_new_features.html#node-aliases-1-5-0 http://docs-internal.puppet.com/docs/bolt/dev/inventory_file.html#provide-an-alias-to-a-node http://docs-internal.puppet.com/docs/bolt/dev/inventory_file.html#objects 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 (BOLT-510) I want to name nodes in inventory separately from their URL/hostname
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-510 I want to name nodes in inventory separately from their URL/hostname Change By: Melissa Amos Labels: docs docs_reviewed 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 (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Melissa Amos Labels: docs docs_reviewed 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 (BOLT-940) apply_prep doesn't work with pcp nodes and released puppet_agent
Title: Message Title Melissa Amos updated an issue Puppet Task Runner / BOLT-940 apply_prep doesn't work with pcp nodes and released puppet_agent Change By: Melissa Amos Release Notes: Bug Fix Enhancement 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 (BOLT-1019) Ability to use Puppet Agent Certificate during catalog execution
Title: Message Title Nick Maludy commented on BOLT-1019 Re: Ability to use Puppet Agent Certificate during catalog execution The puppetlabs/puppetdb module is also affected by the different `confdir` because it uses `$settings::confdir` that is set, by Bolt, to something like: `/tmp/bolt20181206-24176-1bfvwco` https://github.com/puppetlabs/puppetlabs-puppetdb/blob/master/manifests/params.pp#L108 In order for this module to work correctly, i had to specify the following two variables in Hiera to disable the puppetdb_conn_validator resource and fix the confdir: puppetdb::master::config::puppet_confdir: '/etc/puppetlabs/puppet' puppetdb::master::config::strict_validation: false 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"
Jira (BOLT-1019) Ability to use Puppet Agent Certificate during catalog execution
Title: Message Title Nick Maludy created an issue Puppet Task Runner / BOLT-1019 Ability to use Puppet Agent Certificate during catalog execution Issue Type: Improvement Assignee: Unassigned Created: 2018/12/06 4:54 AM Priority: Normal Reporter: Nick Maludy As a end user i would like the ability to use the Puppet Agent's certificate during catalog execution. Usecase: I'm trying to write a Bolt Plan with an apply block that uses our existing Roles+Profiles to install and configure a new Puppet Server + PuppetDB. The modules we're using for this are: theforeman/puppet (for Puppet Agent + Puppet Server), puppetlabs/puppetdb. During the catalog execution the puppetdb_conn_validator fails to connect the PuppetDB instance because the certificate used by Bolt does not match the same CA utilized by PuppetDB. Error message that i'm seeing from that resource when it fails to apply: Unable to connect to puppetdb server (https://bolttest01.domain.tld:8081): The certificate retrieved from the master does not match the agent's private key. Did you forget to run as root?\nCertificate fingerprint: XX:XX:XX:XX \nTo fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certificate.\nOn the master:\n puppetserver ca clean --certname bolttest01.domain.tld\nOn the agent:\n 1. puppet ssl clean\n 2. puppet agent -t\n
Jira (PUP-9344) Add # alt flag to String format %p to force double quoted output
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9344 Add # alt flag to String format %p to force double quoted output Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-9344) Add # alt flag to String format %p to force double quoted output
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-9344
Add # alt flag to String format %p to force double quoted output
Change By:
Henrik Lindberg
When formatting strings with {{String.new}} the formatting rules select single or double quotes depending on the contents of the string. If it can be output as a single quoted string it will produce single quote delimiters, otherwise double quote.This is bad when the result must have double quotes and there is currently no way to force the string formatter to enforce double quotes.To support this, we can add support for "alternate form" using {{#}} to the {{%p}} format and let that mean "use double quotes" - this then applies to all string format that produce a quoted output.
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
Jira (PUP-9344) Add # alt flag to String format %p to force double quoted output
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9344 Add # alt flag to String format %p to force double quoted output Change By: Henrik Lindberg Summary: Add # alt flag to String format %p to force double quoted output 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-9344) Add # alt flag to String format to force double quoted output
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9344 Add # alt flag to String format to force double quoted output Issue Type: Improvement Assignee: Henrik Lindberg Components: DOCS, Language, Type System Created: 2018/12/06 2:52 AM Fix Versions: PUP 6.1.0 Priority: Normal Reporter: Henrik Lindberg When formatting strings with String.new the formatting rules select single or double quotes depending on the contents of the string. If it can be output as a single quoted string it will produce single quote delimiters, otherwise double quote. This is bad when the result must have double quotes and there is currently no way to force the string formatter to enforce double quotes. To support this, we can add support for "alternate form" using # and let that mean "use double quotes" - this then applies to all string format that produce a quoted output. Add Comment
Jira (PUP-7092) Documentation on Hiera 3.2 references the wrong documentation
Title: Message Title Henrik Lindberg assigned an issue to Jean Bond Puppet / PUP-7092 Documentation on Hiera 3.2 references the wrong documentation Change By: Henrik Lindberg Assignee: Jean Bond 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-7092) Documentation on Hiera 3.2 references the wrong documentation
Title: Message Title Henrik Lindberg commented on PUP-7092 Re: Documentation on Hiera 3.2 references the wrong documentation Ping Jean Bond Not sure what state this documentation ticket is in - it may be fixed already... 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-9077) Inconsistent undef value received by 4.x API Ruby functions after touched by 3.x Ruby function
Title: Message Title Henrik Lindberg commented on PUP-9077 Re: Inconsistent undef value received by 4.x API Ruby functions after touched by 3.x Ruby function This was fixed as part of PUP-6964 and is released in Puppet 6.0.0. Closing this as a duplicate of PUP-6964 since it fixes this issue as a side effect of loading 3.x functions as if they were 4.x (while still adhering to some of 3.x peculiarities, this particular problem is fixed). 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-9296) ^ and $ shouldn't match newlines in Pattern
Title: Message Title Henrik Lindberg commented on PUP-9296 Re: ^ and $ shouldn't match newlines in Pattern Jean Bond Where docs explain how to use regexp with =~ and !~ operators or with Pattern data type we should point out that if the string the user is matching against contains newlines, then they need to use \A and \z instead of ^ and $ as the later match beginning and end of a line. This is a common mistake users make and can cause their regexp to unintentionally match multiline text. Have not looked in docs where we talk about regular expressions. 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-1519) Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number
Title: Message Title Henrik Lindberg commented on PUP-1519 Re: Package resource should allow ensure=>">1.0" or ensure=>"<0.10" as well as 'latest', 'installed' and specific version number As noted earlier, we have Semver and SemverRange data types and since Puppet 6.0.0 rich-data can be sent in the catalog. This makes it possible to use those types of values to construct advanced matching for the ensure value. (The type/provider can then interpret that). While versions are specified in different ways in different packages, it should be possible to interpret a semver version range (within the limits of what a particular provider can handle naturally). 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-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Henrik Lindberg commented on PUP-9040 Re: puppet lookup command returns warning with poor formatting So, what happens here is that the "not found" is raised without a "reason" (there is no particular known reason why it is not finding a variable) - that is why there is no information after the semicolon. Then, the warn_once method kicks in, and it formats the message for output - when this is logged it is a string with a new line separating the message from the location information. This is for human output. What lookup does is to get logged messages and outputs them, It does not want to screw up formatting of the explain output with potentially lots of newlines and indentation - instead it outputs logged messages one by one as strings. This is what causes a n to be present in the output. I don't see how we can fix this without removing the newline formatting from warn_once, but that will make other use cases worse. The other option is to have lookup strip newlines from the output - but then that could take away valuable information from the output. I am considering just closing this as a "won't do", but want a second opinion - ping Charlie Sharpsteen, what do you think. 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
Jira (PUP-9040) puppet lookup command returns warning with poor formatting
Title: Message Title Henrik Lindberg commented on PUP-9040 Re: puppet lookup command returns warning with poor formatting Investigated this again. The new-line is coming from Puppet.warn_once, and right now I don't know why it is adding a new line before the location information. 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-9329) Array conversion to String using 'short-form' broken
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-9329
Array conversion to String using 'short-form' broken
Change By:
Henrik Lindberg
Release Notes Summary:
A regression in the string formatting rules has been fixed where a short form formatting rule given for an Array or Hash would not be recognized. For example `String([1,[2,3],4], '%#a")` would not format with indentation, but the long form would `String([1,[2,3],4], {Array => { format => '%#a"}})`. Now the short form works for Array and Hash as intended.
Release Notes:
Bug Fix
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
Jira (PUP-9329) Array conversion to String using 'short-form' broken
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9329 Array conversion to String using 'short-form' broken Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-9329) Array conversion to String using 'short-form' broken
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9329 Array conversion to String using 'short-form' broken Change By: Henrik Lindberg Fix Version/s: PUP 5.5.z Fix Version/s: PUP 6.1.0 Fix Version/s: PUP 6.0.5 Fix Version/s: PUP 5.5.9 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
Jira (PUP-9252) injection of PAL compiler in 4.x function does not work when not invoked by PAL
Title: Message Title Henrik Lindberg commented on PUP-9252 Re: injection of PAL compiler in 4.x function does not work when not invoked by PAL PUP-9254 contains a fix for this - there is a PR ready to be merged. 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-9252) injection of PAL compiler in 4.x function does not work when not invoked by PAL
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9252 injection of PAL compiler in 4.x function does not work when not invoked by PAL Change By: Henrik Lindberg Fix Version/s: PUP 6.1.0 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-5946) Puppet Resource Types
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-5946 Puppet Resource Types Change By: Henrik Lindberg Assignee: Henrik Lindberg 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-5946) Puppet Resource Types
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5946 Puppet Resource Types Change By: Henrik Lindberg Fix Version/s: PUP 5.y 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-9343) Hiera features in 6.y timeframe
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-9343 Hiera features in 6.y timeframe Issue Type: Epic Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2018/12/06 12:35 AM Priority: Normal Reporter: Henrik Lindberg This Epic is a collection of feature requests / issues for Hiera in the Puppet 6 timeframe. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9343) Hiera features in 6.y timeframe
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9343 Hiera features in 6.y timeframe Change By: Henrik Lindberg Assignee: Thomas Hallgren 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-9310) Timespan and Timestamp types cannot be specified from integer or float
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-9310 Timespan and Timestamp types cannot be specified from integer or float Change By: Henrik Lindberg Method Found: Needs Assessment Customer Feedback 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-9310) Timespan and Timestamp types cannot be specified from integer or float
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9310 Timespan and Timestamp types cannot be specified from integer or float Change By: Henrik Lindberg Assignee: Henrik Lindberg 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.
