Jira (PUP-1113) Ability to display messages during agent run without creating resource changes
Title: Message Title Amir Barkal commented on PUP-1113 Re: Ability to display messages during agent run without creating resource changes Sounds like exactly what I need, I'll give it a try - thank you! Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-29) Notification hooks
Title: Message Title Klavs Klavsen commented on PDB-29 Re: Notification hooks One use-case IMHO - would be to collect data from runs. We currently trigger this collection from puppetdb, by way of our clients running puppet agent - curl'ing to a REST service (once agent run has send in report), which then pulls the latest report numbers (and hence lets puppetdb do the report parsing) - so we can save successes, failure etc. numbers - and do alerting and graphing of the state of our servers. It actually allowed us to produce great graphs - highlighting servers that have "continous changes".. alert on massive failure (10+ servers within certain timeframe) in icinga/nagios etc. 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-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5983 Environment Data Provider has different interpolation behavior than Hiera Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5983 Environment Data Provider has different interpolation behavior than Hiera Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Probability Reason: interpolation in hiera environment data QA Risk Assessment: Medium QA Risk Probability: Low QA Risk Severity: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google
Jira (PUP-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Eric Thompson commented on PUP-5983 Re: Environment Data Provider has different interpolation behavior than Hiera in global hiera data: [root@bq6tfw4y197h31b other_module]# for f in foobar_array; do echo $f; puppet lookup $f --node puppet.example.com; done foobar_array --- - - 1 - 2 - 3 [root@bq6tfw4y197h31b other_module]# for f in foobar_array; do echo $f; puppet lookup $f --node puppet.example.com --explain; done foobar_array Data Binding "hiera" Found key: "foobar_array" value: [
Jira (PUP-5983) Environment Data Provider has different interpolation behavior than Hiera
Title: Message Title Eric Thompson commented on PUP-5983 Re: Environment Data Provider has different interpolation behavior than Hiera in the environment on rhel7 at stable puppet-agent SHA: 7c523b75580210a79e2870ff262e6182d9060c05 [root@bq6tfw4y197h31b env1]# puppet lookup foobar_array --node $(hostname -f) --- - - 1 - 2 - 3 [root@bq6tfw4y197h31b env1]# puppet lookup foobar_array --node $(hostname -f) --explain Merge strategy first Data Binding "hiera" No such key: "foobar_array" Data Provider "Hiera Data Provider, version 4"
Jira (PUP-1113) Ability to display messages during agent run without creating resource changes
Title: Message Title Felix Frank commented on PUP-1113 Re: Ability to display messages during agent run without creating resource changes I suggest this be rejected instead. This module serves the stated purpose: https://forge.puppetlabs.com/ipcrm/echo Personally I don't feel that including this type in the core is warranted. 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 (PDOC-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Since there's pretty much unanimous agreement that strings is a tool better delivered via gem rather than a puppet module, the 0.4.0 will be the first and final release to feature both a gem and a module. The module will need to be updated to explain that it is deprecated and all further updates will come via the gem. That means we need to make a few changes for the module release to communicate that it's being deprecated:# Update the README to explain that the module is deprecated# Add a guide for gem installation in the README # Go through the Puppet Labs gem checklist # Go through the Puppet Labs library checklist 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 (PDOC-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Since there's pretty much unanimous agreement that strings is a tool better delivered via gem rather than a puppet module, the 0.4.0 will be the first and final release to feature both a gem and a module. The module will need to be updated to explain that it is deprecated and all further updates will come via the gem. That means we need to make a few changes for the module release to communicate that it's being deprecated: Before the module release: # Update the REAMDE README to explain that the module version is deprecated and where to find the gem # Add a brief deprecation messageBefore the guide for gem release: installation in the README # Go through the Puppet Labs gem release checklist# Update Go through the README to detail the gem installation process (instead of referencing the module) Puppet Labs library checklist 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 (PDOC-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Issue Type: Bug Task 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 (PDOC-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney created an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Issue Type: Bug Assignee: Unassigned Created: 2016/03/11 3:15 PM Priority: Normal Reporter: Hailee Kenney Since there's pretty much unanimous agreement that strings is a tool better delivered via gem rather than a puppet module, the 0.4.0 will be the first and final release to feature both a gem and a module. The module will need to be updated to explain that it is deprecated and all further updates will come via the gem. That means we need to make a few changes for the module release to communicate that it's being deprecated: Before the module release: Update the REAMDE to explain that the module version is deprecated and where to find the gem Add a brief deprecation message Before the gem release: Go through the Puppet Labs gem release checklist Update the README to detail the gem installation process (instead of referencing the module)
Jira (PDOC-74) Deprecate strings module in favor of gem
Title: Message Title Hailee Kenney updated an issue Puppet Strings / PDOC-74 Deprecate strings module in favor of gem Change By: Hailee Kenney Fix Version/s: PDOC 0.4.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8
Title: Message Title Michael Stahnke commented on PDB-2354 Re: PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8 The upgrade issue is being resolved in the puppetdb module. Andrew Roetker is working on the fix. Is there anything else needed here from RE? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2354) PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8
Title: Message Title Rajasree Talla assigned an issue to Rob Braden PuppetDB / PDB-2354 PuppetDB 4.0.0 needs automated testing for upgrades from 2.3.8 Change By: Rajasree Talla Assignee: Rob Braden 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-5986) Bad error for unresolved type in 4.x function API
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5986 Bad error for unresolved type in 4.x function API Change By: Eric Thompson QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5986) Bad error for unresolved type in 4.x function API
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5986 Bad error for unresolved type in 4.x function API Change By: Eric Thompson QA Highest Test Level: Unit QA Risk Assessment: Medium Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5986) Bad error for unresolved type in 4.x function API
Title: Message Title
Eric Thompson commented on PUP-5986
Re: Bad error for unresolved type in 4.x function API
validated on ubuntu1404 at stable puppet-agent SHA: 7c523b75580210a79e2870ff262e6182d9060c05
root@kc0dmwrcpudiep8:/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/functions# puppet apply -e 'then(all_you_need_is_love) |$x| { notice $x }'
Error: Evaluation Error: Error while evaluating a Function Call, 'then' parameter 'arg' expects a Resource value, got String at line 1:1 on node kc0dmwrcpudiep8.delivery.puppetlabs.net
the extra/blank line in the output is from the notice()
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
Jira (PUP-5986) Bad error for unresolved type in 4.x function API
Title: Message Title Eric Thompson assigned an issue to Eric Thompson Puppet / PUP-5986 Bad error for unresolved type in 4.x function API Change By: Eric Thompson Assignee: qa Eric Thompson Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send 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-5968) Deprecate Symbol#<=> monkey patch
Title: Message Title Hailee Kenney assigned an issue to Unassigned Puppet / PUP-5968 Deprecate Symbol#<=> monkey patch Change By: Hailee Kenney Assignee: Hailee Kenney 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-5936) a given undef should set undef and not require a default expression of = undef
Title: Message Title Eric Thompson updated an issue Puppet / PUP-5936 a given undef should set undef and not require a default _expression_ of = undef Change By: Eric Thompson QA Highest Test Level: Acceptance QA Risk Assessment: Low Medium QA Status: Reviewed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Craig Gomes commented on PUP-5288 Re: acceptance: puppet ruby in windows should use the correct ssldir Steve Barlow I chatted with Ryan Gard it does indeed belong with Windows. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2521) (docs) Fix typo in yaml frontmatter (pdb_support_guide)
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2521 (docs) Fix typo in yaml frontmatter (pdb_support_guide) Change By: Andrew Roetker Scope Change Category: Found Scope Change Reason: docs PR for pdb Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2522) (docs) Fix typo in yaml frontmatter (summary-stats)
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2522 (docs) Fix typo in yaml frontmatter (summary-stats) Change By: Andrew Roetker Scope Change Category: Found Scope Change Reason: docs PR for pdb Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Craig Gomes updated an issue Puppet / PUP-5288 acceptance: puppet ruby in windows should use the correct ssldir Change By: Craig Gomes Scrum Team: Client Platform Windows Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2523) (maint) Remove some more potential ordering issues from tests
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2523 (maint) Remove some more potential ordering issues from tests Change By: Andrew Roetker Scope Change Category: Found Scope Change Reason: Transient test failures fix Fix Version/s: PDB 3.2.x Fix Version/s: PDB 4.0.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2525) (maint) Handle terminus to termini package upgrades
Title: Message Title Andrew Roetker updated an issue PuppetDB / PDB-2525 (maint) Handle terminus to termini package upgrades Change By: Andrew Roetker Scope Change Category: Found Scope Change Reason: Packaging packaging packaging for PDB4 release Fix Version/s: PDB module-5.1.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-2958) Rapid-fire puppet runs cause race condition with SSL data
Title: Message Title
Jesus Garcia commented on PUP-2958
Re: Rapid-fire puppet runs cause race condition with SSL data
I have one customer that has reproduced this issue, or pretty close to it, at will and in front of me via Webex.
Details: After buildout of Windows SQL Server VM (and now others non-SQL), the nose fingerprint seems to get lost after the first agent run:
{{C:\Program Files\Puppet Labs\Puppet\bin>puppet agent --fingerprint
C:\Program Files\Puppet Labs\Puppet\bin>}}
Full Description Issue: After provisioning a Windows 2012r2 server, puppet agent gets installed. Custom fact is generated, and `puppet agent –t –waitforcert 120` is issued from the node. Puppet master signs certificated (via vRO WF) and node is classified via the custom fact. Puppet run begins and all configuration is successfully applied. Any subsequent puppet runs result in the following message from the node: ruby 2.1.8p440 (2015-12-16 revision 53160) [x64-mingw32]
C:\Program Files\Puppet Labs\Puppet\bin>puppet agent -t Error: Could not request certificate: The certificate retrieved from the masterdoes not match the agent's private key. Certificate fingerprint: To fix this, remove the certificate from both the master and the agent and then start a puppet run, which will automatically regenerate a certficate. On the master: puppet cert clean On the agent: 1a. On most platforms: find C:/ProgramData/PuppetLabs/puppet/etc/ssl -name .pem -delete 1b. On Windows: del "C:/ProgramData/PuppetLabs/puppet/etc/ssl/.pem" /f 2. puppet agent -t
Exiting; failed to retrieve certificate and waitforcert is disabled
Node is in Puppet console:
Output from `puppet cert list –all` on master: + "" (SHA256) 91:4C:9F:82:D4:57:A1:64:C2:95:D1:9B:A3:C0:07:7F:F5:AA:F4:AA:D5:CA:24:94:BE:6F:B2:12:85:C5:7E:9D
Removing the node from master, deleting certs on the node and re-adding does fix the problem.
This is happening intermittently, but seems to be more consistent with MS SQL servers. These do have significantly longer puppet run times. (oftern greater than 30 minutes). Not sure if that is anything…
Here is the node’s puppet.conf file:
PS C:\ProgramData\PuppetLabs\puppet\etc> cat .\puppet.conf [main] server= pluginsync=true autoflush=true environment=production runinterval = 6h
Attached is the Application log from the affected node. Let me know what other info you may need to help troubleshoot this issue.
Add Comment
Jira (PUP-5825) systemd service provider always enables service in chroot
Title: Message Title Matthew Gyurgyik commented on PUP-5825 Re: systemd service provider always enables service in chroot Pull Request: https://github.com/puppetlabs/puppet/pull/4770 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-5029) PUP 4.3.0
Title: Message Title Steve Barlow commented on PUP-5029 Re: PUP 4.3.0 Kenn Hussey OH SIGH! I read 4.4.0. Maybe i just have 4.4.0 on the brain right now and did a mental search and replace...You are of course right. I closed it. 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-5029) PUP 4.3.0
Title: Message Title Kenn Hussey commented on PUP-5029 Re: PUP 4.3.0 Steve Barlow ah, but PUP 4.4.0 is for puppet-agent 1.4.0; this ticket is much older... 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-5029) PUP 4.3.0
Title: Message Title Steve Barlow commented on PUP-5029 Re: PUP 4.3.0 Kenn Hussey Yeah, I think so. I was sort of waiting for the agent 1.4.0 to get a final tag, but that was it as far as I know. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5288) acceptance: puppet ruby in windows should use the correct ssldir
Title: Message Title Steve Barlow commented on PUP-5288 Re: acceptance: puppet ruby in windows should use the correct ssldir Craig Gomes Kylo Ginsberg This ticket needs a final home. Right now assigned to the client team (but not a sprint), but see eric's comment above that he thinks it might be windows. Where, oh where should I put this? 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-5825) systemd service provider always enables service in chroot
Title: Message Title William Hopper updated an issue Puppet / PUP-5825 systemd service provider always enables service in chroot Change By: William Hopper Story Points: 2 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-5992) Systemd service provider do not support custom status command
Title: Message Title William Hopper assigned an issue to qa Puppet / PUP-5992 Systemd service provider do not support custom status command Change By: William Hopper Status: Ready for CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5992) Systemd service provider do not support custom status command
Title: Message Title William Hopper updated an issue Puppet / PUP-5992 Systemd service provider do not support custom status command Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: This was merged during the community PR triage. Bringing into sprint so we can track it through CI. Sprint: Client Triage 2016-03-23 (Bug Fixes) 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-5967) File type links documentation incorrectly references :ignore value
Title: Message Title William Hopper updated an issue Puppet / PUP-5967 File type links documentation incorrectly references :ignore value Change By: William Hopper Scope Change Category: Adopted Scope Change Reason: Bringing up work from the backlog. Sprint: Client 2016- 04 03 - 10 23 ( C++ Bug Fixes ) Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2527) support latest_report? as a query field on event-counts/aggregate-event-counts
Title: Message Title
Wyatt Alt updated an issue
PuppetDB / PDB-2527
support latest_report? as a query field on event-counts/aggregate-event-counts
Change By:
Wyatt Alt
We document these endpoints as being queryable with the same fields as events, but latest_report? is not included. I'm not sure yet why it doesn't work, but [~verne] has an interest in this fix. To be concrete, this should work{code}[wyatt@desktop puppetdb](master) $ curl -X GET http://localhost:8080/pdb/query/v4/event-counts -d 'distinct_start_time=2015-01-01' -d 'distinct_end_time=2016-10-10' -d 'distinct_resources=true' -d 'summarize_by=resource' -d 'query=["=", "latest_report?", true]'Error 500 HTTP ERROR: 500Problem accessing /pdb/query/v4/event-counts. Reason:org.postgresql.util.PSQLException: ERROR: column certnames.latest_report does not exist Hint: Perhaps you meant to reference the column "certnames.latest_report_id". Position: 2905
Jira (PUP-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto commented on PUP-6045 Re: postrun_command should run after reports and summaries Yeah I have a workaround as well, I use a systemd unit to run puppet, and I use ExecPostStart. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2527) support latest_report? as a query field on event-counts/aggregate-event-counts
Title: Message Title Wyatt Alt updated an issue PuppetDB / PDB-2527 support latest_report? as a query field on event-counts/aggregate-event-counts Change By: Wyatt Alt We document these endpoints as being queryable with the same fields as events, but latest_report? is not included. I'm not sure yet why it doesn't work, but [~verne] has an interest in this fix. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-2527) support latest_report? as a query field on event-counts/aggregate-event-counts
Title: Message Title Wyatt Alt created an issue PuppetDB / PDB-2527 support latest_report? as a query field on event-counts/aggregate-event-counts Issue Type: Bug Assignee: Unassigned Created: 2016/03/11 10:31 AM Priority: Normal Reporter: Wyatt Alt 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
Jira (PUP-6045) postrun_command should run after reports and summaries
Title: Message Title R.I.Pienaar commented on PUP-6045 Re: postrun_command should run after reports and summaries Another command would work yes, I do like these hooks, but not sure if its the most elegant approach, today I dont have this problem anymore since I use apply and just have a shell script that runs apply - I do things I need just in the script after running apply. this works for me 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto commented on PUP-6045 Re: postrun_command should run after reports and summaries TBH I started to wrote a report processor to do that but those are only possible on puppet apply and puppet server. So, portreport_command or client_reports config variable? 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-6045) postrun_command should run after reports and summaries
Title: Message Title Kylo Ginsberg commented on PUP-6045 Re: postrun_command should run after reports and summaries So maybe the suggestion is for a new postreport_command?? Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1345) Solaris automount entries in mountpoint result in huge fact lists
Title: Message Title Branan Riley assigned an issue to Branan Riley Facter / FACT-1345 Solaris automount entries in mountpoint result in huge fact lists Change By: Branan Riley Assignee: Branan Riley 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-6045) postrun_command should run after reports and summaries
Title: Message Title R.I.Pienaar commented on PUP-6045 Re: postrun_command should run after reports and summaries Yeah, I wanted to do things locally as well with the last_run_summary, report etc after a run and could not. I believe Julien Pivotto wants to put some post-run status in his motd based on whats reports. I wanted to do some post processing to pass events onto a middleware event processor. Both not possible since this data is written as you say for scenario 1 - a scenario I never needed personally 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-6046) improve getting nested keys from hash
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6046 improve getting nested keys from hash Change By: Henrik Lindberg Story Points: 1 Sprint: Language Triage Scrum Team: Language Fix Version/s: PUP 4.5.0 Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6046) improve getting nested keys from hash
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6046
improve getting nested keys from hash
Change By:
Henrik Lindberg
In a blog post, [~ripienaar] writes:{quote}This \[structured facts] makes everything better. It’s also structured data but this is still a bit awkward in Puppet:{code:puppet}$x = $facts["foo"]["bar"]["baz"]{code}There seems to be no elegant way to handle a missing ‘foo’ or ‘bar’ key, things just fail badly in ways you can’t catch or recover from. On the CLI you can do facter foo.bar.baz so we’re already careful to not have “.” in a key. {quote}We can actually use multiple keys in an access operator (you can directly slice an array with two arguments (from, to). We could use this for hash as well to mean a progression of key lookups producing undef if one key produces undef.The example would then be written:{quote:puppet}$x = $facts[foo, bar, baz]{quote}it would also allow getting a value from an array in by using a numeric key. Slicing can also be supported if the key is an array. Example, 'baz' is an array and we want the last 2 elements.{quote:puppet}$x = $facts[foo, bar, baz, [-2, 2] ] {quote}
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
Jira (PUP-6046) improve getting nested keys from hash
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-6046
improve getting nested keys from hash
Change By:
Henrik Lindberg
In a blog post, [~ripienaar] writes:{quote}This \[structured facts] makes everything better. It’s also structured data but this is still a bit awkward in Puppet:{code:puppet}$x = $facts["foo"]["bar"]["baz"]{code}There seems to be no elegant way to handle a missing ‘foo’ or ‘bar’ key, things just fail badly in ways you can’t catch or recover from. On the CLI you can do facter foo.bar.baz so we’re already careful to not have “.” in a key. {quote}We can actually use multiple keys in an access operator (you can directly slice an array with two arguments (from, to). We could use this for hash as well to mean a progression of key lookups producing undef if one key produces undef. The example would then be written:{quote:puppet}$x = $facts[foo, bar, baz]{quote}it would also allow getting a value from an array in by using a numeric key. Slicing can also be supported if the key is an array. Example, 'baz' is an array and we want the last 2 elements.{quote:puppet}$x = $facts[foo, bar, baz, [-2, 2]{quote}
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
Jira (PUP-6046) improve getting nested keys from hash
Title: Message Title Henrik Lindberg created an issue Puppet / PUP-6046 improve getting nested keys from hash Issue Type: Bug Assignee: Unassigned Created: 2016/03/11 8:25 AM Priority: Normal Reporter: Henrik Lindberg In a blog post, R.I.Pienaar writes: This [structured facts] makes everything better. It’s also structured data but this is still a bit awkward in Puppet: $x = $facts["foo"]["bar"]["baz"] There seems to be no elegant way to handle a missing ‘foo’ or ‘bar’ key, things just fail badly in ways you can’t catch or recover from. On the CLI you can do facter foo.bar.baz so we’re already careful to not have “.” in a key. We can actually use multiple keys in an access operator (you can directly slice an array with two arguments (from, to). We could use this for hash as well to mean a progression of key lookups producing undef if one key produces undef.
Jira (PUP-6045) postrun_command should run after reports and summaries
Title: Message Title Kylo Ginsberg commented on PUP-6045 Re: postrun_command should run after reports and summaries Interesting. I wonder if there are actually two (or more) different use cases here: 1) postrun_command as a final measure of success/failure (should be before reporting, current behavior) 2) postrun_command for additional local reporting or followup, needs to parse report (suggested here) I think (1) motivated the current placement, so it seems like that would be a shame to give up. I don't fully get the case for (2) tbh, but would love to hear more. I'm not crazy about having two postrun command thingamabob's for the two use cases, but if those are really two distinct, high-value use cases maybe we want that? Needs more thought (at least for me). /cc R.I. Pienaar since you submitted the original redmine ticket. 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-5768) Fix problematic usage of ENV for Windows
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-5768 Fix problematic usage of ENV for Windows Change By: Kenn Hussey Flagged: Impediment 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-6024) Restrict which files are inlined within the per-environment directory
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6024 Restrict which files are inlined within the per-environment directory Change By: Kenn Hussey Flagged: Impediment 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-6031) static catalogs do not copy source host and port to content_uri
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6031 static catalogs do not copy source host and port to content_uri Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1282) networking.ip should fall back to default route 'src' if networking.primary has no IP address
Title: Message Title Kenn Hussey updated an issue Facter / FACT-1282 networking.ip should fall back to default route 'src' if networking.primary has no IP address Change By: Kenn Hussey Flagged: Impediment 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-6033) Recursive file resource in static catalog creates empty directory when source has trailing "/"
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6033 Recursive file resource in static catalog creates empty directory when source has trailing "/" Change By: Kenn Hussey Flagged: Impediment 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-6036) static catalogs cannot inline metadata for files requiring percent encoding
Title: Message Title Kenn Hussey updated an issue Puppet / PUP-6036 static catalogs cannot inline metadata for files requiring percent encoding Change By: Kenn Hussey Flagged: Impediment Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (NPUP-29) Parser does not parse resource override expressions for collectors correctly
Title: Message Title Steve Barlow updated an issue Native Puppet / NPUP-29 Parser does not parse resource override expressions for collectors correctly Change By: Steve Barlow Release Notes: Not Needed Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6043) puppet apply -e states "syntax error at end of file" when there is no file
Title: Message Title Henrik Lindberg commented on PUP-6043 Re: puppet apply -e states "syntax error at end of file" when there is no file That one has been up before - IIRC we just changed that to "end of input", maybe that can come from different places. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1365) Remove "Deprecated: use `puppet facts` instead" from facter --help output
Title: Message Title Nathanael Cole created an issue Facter / FACT-1365 Remove "Deprecated: use `puppet facts` instead" from facter --help output Issue Type: Improvement Affects Versions: FACT 3.1.4 Assignee: Unassigned Created: 2016/03/11 7:36 AM Priority: Normal Reporter: Nathanael Cole Current State: The help dump (facter --help) for the current version of Facter shows a deprecation warning next to the -p flag description. Requested Change: I have confirmed in the facter channel that this is misleading, and that deprecation is no longer valid. With customers contacting us regarding it, we hope that deprecation warning can be removed in coming versions until such a time as a functional replacement is offered again. Add Comment
Jira (PUP-6029) use function local type aliases instead of string in all 4.x functions
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6029 use function local type aliases instead of string in all 4.x functions Change By: Henrik Lindberg Release Notes Summary: This is an internal refactoring that makes sure that Puppet Strings has a fair chance at rending complex parameter types. A handful of functions are affected by this. (Only affects lookup function) 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-6045) postrun_command should run after reports and summaries
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-6045 postrun_command should run after reports and summaries ping Kylo Ginsberg Change By: Henrik Lindberg Scrum Team: Client Platform 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-5966) Update language specification with 'new instance operation'
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-5966 Update language specification with 'new instance operation' Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-6029) use function local type aliases instead of string in all 4.x functions
Title: Message Title Henrik Lindberg assigned an issue to Henrik Lindberg Puppet / PUP-6029 use function local type aliases instead of string in all 4.x functions Change By: Henrik Lindberg Assignee: Henrik Lindberg Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5903) 4.x function api should contain way to add type aliases
Title: Message Title
Henrik Lindberg updated an issue
Puppet / PUP-5903
4.x function api should contain way to add type aliases
Change By:
Henrik Lindberg
For complex function parameters it is difficult to write the type signatures in a 4.x function API.As an example look at the 4.x function {{lookup()}}. In that function string variables and interpolation is used to define the the types of parameters in string form.It would be very useful if a function could add type aliases to the type system and then use those in the dispatcher.Tools like Puppet String would then be able to find them (it cannot understand the string interpolations. Users would when the get an error also be helped by the name of the type (along with an expanded details mis match).it should be easy to come up with a type alias API, but a more difficult question is how to name these type aliases. A function in a module would naturally place the types in the module's name space. But what about an environment? Or in puppet? (which uses the global namespace).Somehow, it seems appropriate if the aliases, if being specific to a single function (and hence defined there) would use a name related to the function. If the types are more general, the should naturally not be introduced in a function.This leads to a couple of design decisions:* What is the namespace of type aliases in puppet itself ?* 4.x function API for type aliases for parameters* In a Puppet Function, should we allow it to introduce type aliases as well as defining the function? (Now that is not allowed).* Where do we place general type aliases in Puppet ?Example{code:ruby}#... in a 4.x function type_aliases local_types { type 'MyModule::PullSled::OhDeer ' = > 'Enum[...]'}dispatch :some_method { param 'MyModule::PullSled::OhDeer' :a_deer}#... etc{code}}
Add Comment
This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
Jira (PUP-5940) Update Language Specification (4.x function API type alias)
Title: Message Title Henrik Lindberg updated an issue Puppet / PUP-5940 Update Language Specification (4.x function API type alias) Change By: Henrik Lindberg Summary: Update Language Specification (4.x function API type alias ) 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-6045 postrun_command should run after reports and summaries Change By: Julien Pivotto Component/s: Catalog Application 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto updated an issue Puppet / PUP-6045 postrun_command should run after reports and summaries Change By: Julien Pivotto Component/s: Client 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-6045) postrun_command should run after reports and summaries
Title: Message Title Julien Pivotto created an issue Puppet / PUP-6045 postrun_command should run after reports and summaries Issue Type: Bug Assignee: Unassigned Created: 2016/03/11 2:56 AM Priority: Normal Reporter: Julien Pivotto From: https://projects.puppetlabs.com/issues/8195 by R.I.Pienaar At present the postrun_command is being run before the reports are sent and therefore also before they are stored locally in lastrunfile and lastrunreport. It would be great to change that behaviour so that postrun commands have acces to the reports file. Add Comment This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc)
