Jira (BOLT-1357) Reduce install size of bolt
Title: Message Title Glenn Sarti commented on BOLT-1357 Re: Reduce install size of bolt Cross reference : https://github.com/puppetlabs/bolt/issues/1177 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310851.1559272757000.76035.1566962940154%40Atlassian.JIRA.
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title Glenn Sarti commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows Yasmin Rajabi I feel it's still important. Having a different shell between local and remote commands is annoying (at best) and confusing. Also adding "powershell.exe -noprofile -NoLogo -ExecutionPolicy Bypass -Command" as a workaround is far from a great UX. Also using -Command has known peculiarities with regards to exit codes, double quoting, multiline commands etc. etc. Using the PowerShell Process sharing gem (which powers the IIS, DSC, DSC_Lite and PowerShell Puppet module) is a much much better idea. Note that while it "shares" the same process, each execution is in it's own sandbox (PowerShell Runspace to be exact) So I think this addresses Alex Dreyer's concern about "state" being left around. As for Alex's comment about "Would that be implemented for winrm too?" I don't understand the question. WinRM is a transport not a shell. What state in WinRM are you worried about? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314131.1561529132000.76013.1566961560266%40Atlassian.JIRA.
Jira (PUP-9989) Bug with attributes "purge_ssh_keys" in resource type "user"
Title: Message Title
Maheswaran Shanmugam created an issue
Puppet / PUP-9989
Bug with attributes "purge_ssh_keys" in resource type "user"
Issue Type:
Improvement
Assignee:
Unassigned
Created:
2019/08/27 8:00 PM
Environment:
Test is conducted on PE 2018.1.8 & PE 2018.1.0
Priority:
Normal
Reporter:
Maheswaran Shanmugam
Issue: By default, attribute ```purge_ssh_keys => true``` in resource type ```user``` should look for keys in the .ssh/authorized_keys file in the user’s home directory and Purge any keys that aren’t managed as ssh_authorized_key resources. However, then one copy of that key (manually added many keys) is removed. Run puppet again, another copy is removed. Recreation Steps: 1) puppet code ssh_authorized_key { 'henry': ensure => present, user => 'henry', type => 'ssh-rsa', key => 'a1akCIARg5rKE2zxEfztF9Cgh2u2WnWzUvDRCsHQ+E2SmsEEBuxJ8RpPafjG/GxO2247JWGvKzO4zpAtFO7G4WowFU0qmyGCfNyJzPLJd7OSBJC58ooY6G6Lp94P1w9z+7/gM8MkJ6d4W6M9uJL9JCL2aKRmuHAbl0URLwsXq846I7zfix5qXowduRzZTWNBQm3K+iGsASpexG2i/eWuaZGmPxeGxq+t6OtiasRjg9oWInak0+63Uzjj0pDZ1uBlS9EbxaBk+suZQ10qYxoh3dPnuqqEEr83S7GMEKBDZjzkTstIplMXZkhYBJB93rAngbM+JvNb', } user { 'henry': ensure => present, home => '/home/henry', managehome => true, purge_ssh_keys => true, } 2) Add multiple lines in ```/home/henry/.ssh/authorized_keys``` ```
HEADER: This file was autogenerated at 2019-08-27 19:50:56 -0700
HEADER: by puppet. While it can still be managed manually, it
HEADER: is definitely not recommended. ssh-rsa
Jira (PUP-9983) Prepare release announcement (Puppet Platform 6.8.1)
Title: Message Title Bill Tang commented on PUP-9983 Re: Prepare release announcement (Puppet Platform 6.8.1) The next release in the Platform 6 series, Platform 6.8.1 is now available! The release primarily contains bug fixes. You can see the full list of changes in the release notes https://puppet.com/docs/puppet/latest/release_notes_puppet.html 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322470.1566950355000.75909.1566954180099%40Atlassian.JIRA.
Jira (PUP-9987) Update Confluence and JIRA based on release (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9987 Update Confluence and JIRA based on release (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 5:00 PM Due Date: 2019/08/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 1) Update the release pages for Puppet Platform and puppet-agent in Confluence based on the release. Replace “Target Date” with “Release Date”, change language to past tense, and move the pages to the appropriate parent pages under “Current Releases”. 2) Update the “Versions & Dependencies pages for Puppet Platform and puppet-agent based on the release. Format the release versions in bold and move them to the appropriate tables under “Current Releases”. 3) Close any outstanding Milestone and Risk tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the Milestone tickets as needed to ensure they match the actual milestone dates. 4) Close the Release tickets for the Puppet Platform and puppet-agent releases. Be sure to update due dates for the tickets as needed to ensure they match the actual release date. 5) Close all tickets that have been resolved as part of the release. When using a bulk modify operation to transition the tickets to ‘Closed’ status in JIRA, be sure to select the appropriate resolution and disable notifications to avoid spamming watchers. 6) Make all tickets that were marked as Internal for the release public. When using bulk modify operation to change the value of the ‘level’ field for tickets to ‘None’ in JIRA, be sure to disable notifications to avoid spamming watchers. 7) Mark all versions that were shipped as part of the release as “released”. When doing so, be sure to update the
Jira (PUP-9988) Communicate scope and timeline of next release (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9988 Communicate scope and timeline of next release (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 5:00 PM Due Date: 2019/08/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 1) Create versions and filters for the release in in JIRA. Ensure that the filters are shared with the ‘All Employees’ group. 2) Create or update the Kanban board for the release series. Ensure that the underlying filter for the board includes issues from the release filter and add a quick filter to highlight just those issues. 3) Create Release tickets (in the Project Central project) for the Puppet Platform and puppet-agent releases, with sub-tasks for each milestone (e.g., “String Freeze”, “Stop Ship Line”, “Ready to Ship”, and “General Availability (GA)”. 4) Create release pages for the Puppet Platform and puppet-agent releases in Confluence, under the appropriate “Upcoming Releases” parent page. Make sure the pages reference the release filters, tickets, and Kanban board as needed. 5) Update the “Versions & Dependencies” pages for Puppet Platform and puppet-agent with dependency versions for releases. Format the release versions in italics and link them to their corresponding release pages. 6) Add events for the release milestone dates to Group-Platform Google calendar. Ensure the description for each event includes a link to the release page. 7) Send an email to stakeholders (e.g., puppet-...@googlegroups.com and discuss-platf...@puppet.com) outlining the scope and timeline for the release.
Jira (PUP-9986) Send release announcement (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9986 Send release announcement (Puppet Platform 6.8.1) Issue Type: Task Assignee: Sara Meisburger Created: 2019/08/27 5:00 PM Due Date: 2019/08/28 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) Once docs have finished building (check that all links resolve appropriately) from your puppet-product-updates account - Send the previously drafted announcement from the "prepare release announcement" ticket via BCC to puppet-us...@googlegroups.com, puppet-...@googlegroups.com, puppet-annou...@googlegroups.com, and internal-puppet-product-upda...@puppet.com. You must be a member of these groups in order to send. If this release has security implications, also send to puppet-security-annou...@googlegroups.com. Make a PSA on IRC and/or Slack, something along the lines of "PSA: Puppet Platform 6.8.1 is now available".
Jira (PUP-9981) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9981 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 4:59 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 1) Send an email reminder ahead of time about the upcoming Stop Ship milestone date. 2) Review tickets on the release Kanban board to ensure all code changes have landed. Flag any related issues that are not yet Ready for CI. 3) Ensure all tickets have release notes, if needed. Add comments to issues without release notes, asking the author of the PR to add them or indicate that they aren’t needed. 4) Follow up with the Engineering lead for each component (e.g., in Slack) to confirm current state and obtain a forecast for when all code will be in a build. 5) Send email indicating that the Stop Ship milestone has been achieved. Add Comment
Jira (PUP-9984) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9984 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 4:59 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 1) Ensure all prerequisite release tasks are complete. 2) Review the release Kanban board to ensure all tickets are resolved. 3) Ping release leads in #proj-puppet-releases Slack channel for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9983) Prepare release announcement (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9983 Prepare release announcement (Puppet Platform 6.8.1) Issue Type: Task Assignee: Bill Tang Created: 2019/08/27 4:59 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Jean Bond for review and any important hyperlinks. If there are any links, it would be most helpful for the sender if they were already hyperlinked to the display text, so only a copy+paste to Gmail is necessary. Add Comment
Jira (PUP-9985) Publish documentation and updates and release notes (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9985 Publish documentation and updates and release notes (Puppet Platform 6.8.1) Issue Type: Task Assignee: Jean Bond Created: 2019/08/27 4:59 PM Due Date: 2019/08/28 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) Merge release notes and documentation updates as needed, build and publish the docs, and verify that the updated docs are live before the announcement goes out. Add Comment
Jira (PUP-9982) Prepare documentation updates and release notes (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9982 Prepare documentation updates and release notes (Puppet Platform 6.8.1) Issue Type: Task Assignee: Jean Bond Created: 2019/08/27 4:59 PM Due Date: 2019/08/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) Please post a link to the docs PR in the 'Publish Docs' ticket. For X and Y releases, ensure that the WEB team has prepared Drupal for the release. Add Comment
Jira (PUP-9980) Prepare JIRA and Confluence for release (Puppet Platform 6.8.1)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9980 Prepare JIRA and Confluence for release (Puppet Platform 6.8.1) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/08/27 4:58 PM Due Date: 2019/08/27 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-08-28) 1) Ensure “Versions & Dependencies” pages for Puppet Platform and puppet-agent are up to date in Confluence. Reach out to teams as needed to confirm that the fix versions listed are those that we intend to ship with the release. 2) Ensure release leads for Puppet Platform and puppet-agent are correct and update the invitiation for the release retrospective to include them. Reach out to teams as needed to confirm lead assignments. 3) For each component project of Puppet Platform and puppet-agent, ensure there is a next version if needed. Often this will be the next Z in an X.Y.Z series. However, if we are jumping to a new X or Y release that skips an existing Z version in JIRA, make sure those tickets are reassigned to the correct fix version, and the unneeded version is deleted. For example, if we have tickets with a fix version of 4.3.3, but we’re going from 4.3.2 to 4.4.0, then we need to reassign the tickets assigned to 4.3.3 and delete the 4.3.2 version from JIRA. 4) Create public filters for inclusion in the release notes and/or announcement. These allow easy tracking as new bugs come in for a particular version and allow everyone to see the list of changes in a release. Include links to the filters as a comment on this issue before resolving it. 5) Update the “master” filters for Puppet Platform 6.8.1 and puppet-agent 6.8.1 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-9979) Puppet Platform 6.8.1 Release - 2019-08-28
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9979 Puppet Platform 6.8.1 Release - 2019-08-28 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/08/27 4:58 PM Due Date: 2019/08/28 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.8.1 Release - 2019-08-28 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9975) Regression: Unable to install g++ package using dpkg provider
Title: Message Title Jean Bond updated an issue Puppet / PUP-9975 Regression: Unable to install g++ package using dpkg provider Change By: Jean Bond Release Notes: Bug Fix Not Needed 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322201.1566676101000.75644.1566946080448%40Atlassian.JIRA.
Jira (PUP-9974) Regression: allow_virtual => true matches too much for dpkg provider
Title: Message Title Jean Bond updated an issue Puppet / PUP-9974 Regression: allow_virtual => true matches too much for dpkg provider Change By: Jean Bond Labels: resolved-issue-added 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322106.1566573534000.75647.1566946080472%40Atlassian.JIRA.
Jira (PUP-9973) Can't create users using useradd provider when specifying uid since 6.8.0
Title: Message Title Jean Bond updated an issue Puppet / PUP-9973 Can't create users using useradd provider when specifying uid since 6.8.0 Change By: Jean Bond Labels: resolved-issue-added 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322037.1566509702000.75412.1566943260444%40Atlassian.JIRA.
Jira (PUP-9975) Regression: Unable to install g++ package using dpkg provider
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9975 Regression: Unable to install g++ package using dpkg provider Change By: Josh Cooper Release Notes Summary: This regression was fixed in PUP-9974, which reverted the change made in 6.8.0 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322201.1566676101000.75208.1566939300314%40Atlassian.JIRA.
Jira (PUP-9975) Regression: Unable to install g++ package using dpkg provider
Title: Message Title Josh Cooper commented on PUP-9975 Re: Regression: Unable to install g++ package using dpkg provider We reverted the change in PUP-9824, and the revert is PUP-9974, which will be released in 6.8.1. As a result, this ticket will be "fixed" as well. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322201.1566676101000.75202.1566939240430%40Atlassian.JIRA.
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title Alex Dreyer commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows Would that be implemented for winrm too? I'm concerned about state being left around in some cases but not others. We also originally had concerns about us not being able to manage that state reliably, 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314131.1561529132000.75037.1566935940292%40Atlassian.JIRA.
Jira (PUP-9480) puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts
Title: Message Title Kris Bosland assigned an issue to Unassigned Puppet / PUP-9480 puppet unable to put ipv4+ipv6 dual stack hosts into /etc/hosts Change By: Kris Bosland Assignee: Kris Bosland 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295251.154953565.74973.1566934080191%40Atlassian.JIRA.
Jira (PDB-4491) Add/update CODEOWNERS in a few repos
Title: Message Title Rob Browning created an issue PuppetDB / PDB-4491 Add/update CODEOWNERS in a few repos Issue Type: Improvement Assignee: Unassigned Created: 2019/08/27 12:09 PM Priority: Normal Reporter: Rob Browning Specifically: puppetdb-cli stockpile structured-logging and perhaps for now just include a "* @puppetlabs/puppetdb" line. Also, make sure the addition of that line to pdb 5.2.x was merged up correctly. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1117) Powershell task helper library
Title: Message Title Yasmin Rajabi commented on BOLT-1117 Re: Powershell task helper library William Hurt is this something you're still interested in taking on? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295235.1549498793000.74926.1566932412756%40Atlassian.JIRA.
Jira (BOLT-1117) Powershell task helper library
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1117 Powershell task helper library Change By: Yasmin Rajabi Labels: closed-github-move eyu windows 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.295235.1549498793000.74932.1566932413191%40Atlassian.JIRA.
Jira (BOLT-1130) Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1130 Bolt PowerShell wrapper should allow for the use of Convert-ToJson (or similar) when using --params Change By: Yasmin Rajabi Labels: closed-github-move eyu known-issue-added windows 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.296554.1550589154000.74917.1566932340682%40Atlassian.JIRA.
Jira (BOLT-1170) Unable to run apply() on Windows host - The current deserialized object size is xxx. The allowed maximum object size is 10485760
Title: Message Title Ethan Brown commented on BOLT-1170 Re: Unable to run apply() on Windows host - The current deserialized object size is xxx. The allowed maximum object size is 10485760 Another way to work around the file content problem would be to enable SMB file transfers and make sure that Bolt internally uses that mechanism to send large blocks of content. WinRM transport is not really well equipped to send large amounts of binary 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299441.1552092246000.74895.1566932221087%40Atlassian.JIRA.
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title William Hurt commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows Yasmin Rajabi I think Michael Lombardi is zeroing in on a ruby gem based solution that you might like. His solution would allow multiple powershell commands in the same run utilizing the same PowerShell process that is kept running between commands so that the process only needs to go through startup once per Bolt startup. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314131.1561529132000.74891.1566932221023%40Atlassian.JIRA.
Jira (BOLT-1170) Unable to run apply() on Windows host - The current deserialized object size is xxx. The allowed maximum object size is 10485760
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1170 Unable to run apply() on Windows host - The current deserialized object size is xxx. The allowed maximum object size is 10485760 Change By: Yasmin Rajabi Labels: closed-github-move eyu ghm 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299441.1552092246000.74880.1566932160346%40Atlassian.JIRA.
Jira (BOLT-1176) Tasks run on Windows via PCP do not resolve all executable paths correctly
Title: Message Title Yasmin Rajabi commented on BOLT-1176 Re: Tasks run on Windows via PCP do not resolve all executable paths correctly Branan Riley a similar one to put on your radar. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.299757.1552418215000.74876.1566932100187%40Atlassian.JIRA.
Jira (BOLT-1296) Support ed25519 on windows
Title: Message Title Yasmin Rajabi commented on BOLT-1296 Re: Support ed25519 on windows Cas Donoghue this is something Ethan Brown has offered to help point in the right direction if you wanted to move this work. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307882.155734252.74868.1566931800375%40Atlassian.JIRA.
Jira (BOLT-1323) Support WinRM with Kerberos (from Windows node)
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1323 Support WinRM with Kerberos (from Windows node) Change By: Yasmin Rajabi Labels: closed-github-move eyu ghm 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309458.1558371969000.74860.1566931740381%40Atlassian.JIRA.
Jira (BOLT-1323) Support WinRM with Kerberos (from Windows node)
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1323 Support WinRM with Kerberos (from Windows node) Change By: Yasmin Rajabi Labels: closed-github-move eyu 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.309458.1558371969000.74856.1566931680226%40Atlassian.JIRA.
Jira (BOLT-1357) Reduce install size of bolt
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1357 Reduce install size of bolt Change By: Yasmin Rajabi Labels: closed-github-move eyu 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.310851.1559272757000.74852.1566931620246%40Atlassian.JIRA.
Jira (BOLT-1429) Inconsistent behavior in Boltspec::Run.run_command on Windows
Title: Message Title Yasmin Rajabi commented on BOLT-1429 Re: Inconsistent behavior in Boltspec::Run.run_command on Windows Thomas Honey William Hurt Glenn Sarti hey is this something you find important and want to take on? 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.314131.1561529132000.74844.1566931560673%40Atlassian.JIRA.
Jira (BOLT-1467) bolt_shim::command should execute via powershell on Windows
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1467 bolt_shim::command should execute via powershell on Windows Change By: Yasmin Rajabi Labels: closed-github-move eyu windows 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315975.1562793707000.74828.1566931380358%40Atlassian.JIRA.
Jira (BOLT-1467) bolt_shim::command should execute via powershell on Windows
Title: Message Title Yasmin Rajabi commented on BOLT-1467 Re: bolt_shim::command should execute via powershell on Windows Branan Riley do you think this is going to be the same issue with native pe plans? cc Ethan Brown 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315975.1562793707000.74825.1566931320171%40Atlassian.JIRA.
Jira (BOLT-1488) Use Schannel on Windows
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1488 Use Schannel on Windows Change By: Yasmin Rajabi Labels: closed-github-move eyu 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318236.1564160327000.74819.1566931260343%40Atlassian.JIRA.
Jira (BOLT-1488) Use Schannel on Windows
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-1488 Use Schannel on Windows Change By: Yasmin Rajabi Labels: closed-github-move eyu 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.318236.1564160327000.74810.1566931200354%40Atlassian.JIRA.
Jira (FACT-1960) The first prototype should be able to retrieve at least one fact from one os and display it similar to the way c++ facter displays it.
Title: Message Title Bogdan Irimie updated an issue Facter / FACT-1960 The first prototype should be able to retrieve at least one fact from one os and display it similar to the way c++ facter displays it. Change By: Bogdan Irimie Epic Status: To Do Done 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.317058.1563432174000.74619.1566928260138%40Atlassian.JIRA.
Jira (FACT-2001) Prototype 4 should include OS detection and output format similar to the C++ facter
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2001 Prototype 4 should include OS detection and output format similar to the C++ facter Issue Type: Epic Assignee: Unassigned Created: 2019/08/27 10:48 AM Priority: Normal Reporter: Bogdan Irimie 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 view this discussion on the web visit
Jira (FACT-2000) Add support for legacy facts
Title: Message Title Bogdan Irimie created an issue Facter / FACT-2000 Add support for legacy facts Issue Type: Task Assignee: Unassigned Created: 2019/08/27 10:44 AM Priority: Normal Reporter: Bogdan Irimie 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 view this discussion on the web visit
Jira (FACT-2000) Add support for legacy facts
Title: Message Title Bogdan Irimie assigned an issue to Bogdan Irimie Facter / FACT-2000 Add support for legacy facts Change By: Bogdan Irimie Assignee: Bogdan Irimie 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322383.1566927847000.74593.1566927900382%40Atlassian.JIRA.
Jira (PUP-9974) Regression: allow_virtual => true matches too much for dpkg provider
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9974 Regression: allow_virtual => true matches too much for dpkg provider Change By: Mihai Buzgau Fix Version/s: PUP 6.8.1 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322106.1566573534000.74557.1566927540499%40Atlassian.JIRA.
Jira (PUP-9974) Regression: allow_virtual => true matches too much for dpkg provider
Title: Message Title Mihai Buzgau updated an issue Puppet / PUP-9974 Regression: allow_virtual => true matches too much for dpkg provider Change By: Mihai Buzgau Release Notes Summary: Removed the feature for virtual package support for dpkg provider. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322106.1566573534000.74552.1566927540471%40Atlassian.JIRA.
Jira (BOLT-1525) Add zypper implementation to package task
Title: Message Title Adrian Parreiras Horta commented on BOLT-1525 Re: Add zypper implementation to package task PR here https://github.com/puppetlabs/puppetlabs-package/pull/143 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322358.1566923951000.74293.1566924180240%40Atlassian.JIRA.
Jira (BOLT-1525) Add zypper implementation to package task
Title: Message Title Adrian Parreiras Horta created an issue Puppet Task Runner / BOLT-1525 Add zypper implementation to package task Issue Type: Improvement Assignee: Adrian Parreiras Horta Created: 2019/08/27 9:39 AM Priority: Normal Reporter: Adrian Parreiras Horta 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 view this discussion on the web visit
Jira (BOLT-1468) Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Title: Message Title
Sean McDonald updated an issue
Puppet Task Runner / BOLT-1468
Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Change By:
Sean McDonald
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.ORCH-2321 describes process of enabling "wait until available" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "wait until available" when there is no PCP transport available.**NOTE** the implementation of connection checks for wait until available is different from other bolt actions! Due to the nature of wait_until_available the bolt-server endpoint will *_not_* perform the same operation as an actual "wait_until_available" call. The differences are as follows:# Orchestrator will be performing the actual process of 'waiting' for nodes to be connected, so the endpoint in bolt-server *_should not wait_*. The bolt-server endpoint should check for the status of all node connections and then return immediately.# Node checks from the orchestrator are performed in batches, not one target at a time. The schema and implementation for checking connections in bolt server should expect an array of nodes to check.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the "check connected nodes" action in PCP-868. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support checking node connections via SSH and WinRM, using the new JSON schema. * Document the new endpoints in the
Jira (BOLT-1468) Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Title: Message Title Sean McDonald updated an issue Puppet Task Runner / BOLT-1468 Add 'check-node-connections' endpoint in bolt-server to support wait_until_available Change By: Sean McDonald Summary: implement wait_until_available Add 'check-node-connections' endpoint in bolt-server to support wait_until_available 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.315953.1562789343000.74244.1566923640248%40Atlassian.JIRA.
Jira (BOLT-1468) Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Title: Message Title
Sean McDonald updated an issue
Puppet Task Runner / BOLT-1468
Add 'check-node-connections' endpoint in bolt-server to support wait_until_available
Change By:
Sean McDonald
*Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp-agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt-server" service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints. PCP-868 and ORCH-2321 describe describes process of enabling "wait until available" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "wait until available" when there is no PCP transport available.**NOTE** the implementation of connection checks for wait until available is different from other bolt actions! Due to the nature of wait_until_available the bolt-server endpoint will *_not_* perform the same operation as an actual "wait_until_available" call. The differences are as follows:# Orchestrator will be performing the actual process of 'waiting' for nodes to be connected, so the endpoint in bolt-server *_should not wait_*. The bolt-server endpoint should check for the status of all node connections and then return immediately.# Node checks from the orchestrator are performed in batches, not one target at a time. The schema and implementation for checking connections in bolt server should expect an array of nodes to check.*Requirements*Changes will be made to the [bolt server app|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema.org/specification.html]. Add a description of the JSON schema for data passed to the new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for the "check connected nodes" action in PCP-868. * Add new POST endpoints in the transport sinatra app [here|https://github.com/puppetlabs/bolt/blob/master/lib/bolt_server/transport_app.rb] to support checking node connections via SSH and WinRM, using the new JSON schema. * Document the
Jira (BOLT-1468) implement wait_until_available in bolt-server
Title: Message Title
Sean McDonald updated an issue
Puppet Task Runner / BOLT-1468
implement wait_until_available in bolt-server
Change By:
Sean McDonald
Bolt *Background*When told to run a task on some nodes, a PE master typically contacts the nodes over the PCP protocol. It sends a formatted request over PCP to the pxp - agent service running on the nodes, directing them to run the task locally. But if the nodes don't have a pxp-agent service running, the PE master must contact them via SSH or WinRM instead. For these cases, the PE master runs a "pe-bolt- server needs " service, which is a sinatra application that waits for post requests to /ssh/run_task or /winrm/run_task, then runs the task via an instance of the bolt executor, just like bolt does when you run a task via the CLI. Basically, it's a thin REST API wrapper around normal bolt "task run" operations that the PE master can use when there's no PXP agent to talk to over PCP.In PE Kearney, "task run" is the only supported action over PCP, so it follows that the only endpoints in the bolt-server REST API are for "task run". For other typical bolt actions ("command run", "file upload", "script run"), PCP operations are handled by wrapping any non-task action in an ephemeral task in order to use the "task run" endpoints.PCP-868 and ORCH-2321 describe process of enabling "wait until available" without a task wrapper over PCP on the agent and server. This ticket describes the new endpoint on bolt-server that will support "wait until available" when there is no PCP transport available.**NOTE** the implementation of [ connection checks for wait until available is different from other bolt actions! Due to the nature of wait_until_available the bolt-server endpoint will *_not_* perform the same operation as an actual "wait_until_available" call. The differences are as follows:# Orchestrator will be performing the actual process of 'waiting' for nodes to be connected, so the endpoint in bolt-server *_should not wait_*. The bolt-server endpoint should check for the status of all node connections and then return immediately.# Node checks from the orchestrator are performed in batches, not one target at a time. The schema and implementation for checking connections in bolt server should expect an array of nodes to check.*Requirements*Changes will be made to the [bolt server app |https:// puppet github .com/ docs puppetlabs /bolt/ latest tree / plan_functions master/lib/bolt_server]: * The app follows the [json schema specification|https://json-schema . org/specification. html #wait-until-available ] . Add a description of the JSON schema for orchestrator data passed to use when the SSH or WinRM transports are used new endpoints [here|https://github.com/puppetlabs/bolt/tree/master/lib/bolt_server/schemas]. This schema should match the one defined for nodes not the "check connected to nodes" action in PCP -868 . As an example, Implementation of the run_task endpoint is available * Add new POST endpoints in the [ transport
Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-2634
PQL & Hashes: Provide hash projection capability for facts & resource params
Change By:
Austin Blatt
Acceptance Criteria:
Fact json projection for the following endpoints/parameters with AST and PQL support.In scope, format - (, ){{inventory}} - ({{facts}}, {{trusted}}){{resources}} - ({{parameters}})Out of scope, format - (, ){{factsets}} - ({{facts)}}
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.127261.1461089739000.74187.1566923104677%40Atlassian.JIRA.
Jira (PDB-2634) PQL & Hashes: Provide hash projection capability for facts & resource params
Title: Message Title
Austin Blatt updated an issue
PuppetDB / PDB-2634
PQL & Hashes: Provide hash projection capability for facts & resource params
Change By:
Austin Blatt
Acceptance Criteria:
Fact projection for the following endpoints/parameters with AST and PQL support. In scope, format - (, ){{inventory}} - ({{facts}}, {{trusted}}){{resources}} - ({{parameters}})Out of scope, format - (, ){{factsets}} - ({{facts)}}
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.127261.1461089739000.74087.1566922021921%40Atlassian.JIRA.
Jira (PUP-9974) Regression: allow_virtual => true matches too much for dpkg provider
Title: Message Title Alexandru Popa assigned an issue to Alexandru Popa Puppet / PUP-9974 Regression: allow_virtual => true matches too much for dpkg provider Change By: Alexandru Popa Assignee: Alexandru Popa 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.322106.1566573534000.73795.1566914040215%40Atlassian.JIRA.
Jira (FACT-1919) blank/negative facter cache due to timed out EC2 metadata
Title: Message Title
Gabriel Nagy updated an issue
Facter / FACT-1919
blank/negative facter cache due to timed out EC2 metadata
Change By:
Gabriel Nagy
Release Notes Summary:
Make the EC2 session timeout configurable via the {{EC2_SESSION_TIMEOUT}} environment variable (in milliseconds).If the environment variable does not exist or is set to an invalid value, Facter defaults it to 5000 (5 seconds).
Release Notes:
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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.307267.1556898834000.73755.1566908040140%40Atlassian.JIRA.
Jira (BOLT-1377) Include networking gem in bolt dependencies.
Title: Message Title David Schmitt commented on BOLT-1377 Re: Include networking gem in bolt dependencies. re-opened as https://github.com/puppetlabs/bolt-vanagon/issues/115 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.311783.1560160088000.73573.1566898680201%40Atlassian.JIRA.
Jira (PUP-9969) Update Public-facing Puppet docs to remove Ubuntu 14.04
Title: Message Title Dorin Pleava commented on PUP-9969 Re: Update Public-facing Puppet docs to remove Ubuntu 14.04 This will be completed in the next PE release. 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 view this discussion on the web visit https://groups.google.com/d/msgid/puppet-bugs/JIRA.321530.1566311767000.73542.1566891840124%40Atlassian.JIRA.
