Jira (PUP-9055) Compile catalogs on demand with user-specified facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9055 Compile catalogs on demand with user-specified facts Change By: Josh Cooper Release Notes Summary: The "puppet catalog compile" action will compile a catalog in the same way that the "puppet master --compile" application did, before being removed in Puppet 6. The command must be run on the puppetserver with access to modules, hiera data, etc 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 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-9055) Compile catalogs on demand with user-specified facts
Title: Message Title Josh Cooper updated an issue Puppet / PUP-9055 Compile catalogs on demand with user-specified facts Change By: Josh Cooper Fix Version/s: PUP 6.y Fix Version/s: PUP 6.5.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9055) Compile catalogs on demand with user-specified facts
Title: Message Title Josh Cooper commented on PUP-9055 Re: Compile catalogs on demand with user-specified facts Watchers on the ticket: Alan Smith contributed a PR to restore the functionality of puppet master --compile using puppet catalog compile, and it's been merged to master in https://github.com/puppetlabs/puppet/commit/5d30e1e091199729b9d10dbe7c1566b4bcd7cded. It has the same limitation that puppet master had where you have to "preload" the facts for the node being compiled by saving a facts file with the name $certname.yaml. But at least we've restored the capabilities that were removed when puppet master --compile was removed. If folks are interested in explicitly passing the facts to use on the command line, let's file a new ticket and link to this one. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1263) Rerun should create default project directory when neccessary or silently fail
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1263 Rerun should create default project directory when neccessary or silently fail Change By: Cas Donoghue Release Notes Summary: Bolt will create a default project directory when one does not exists to support rerun. Release Notes: Bug Fix Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1263) Rerun should create default project directory when neccessary or silently fail
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1263 Rerun should create default project directory when neccessary or silently fail Change By: Cas Donoghue Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-4349) Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4349 Reconcile git commits, JIRA tickets, and versions (PuppetDB 6.3.2) Issue Type: Task Assignee: Zachary Kent Created: 2019/04/23 4:56 PM Due Date: 2019/04/23 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) Ensure all tickets referenced in the commit log have a bug targeted at the release, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by inspecting the git log and comparing against 'Project=PDB and fixVersion="PDB x.y.z"' in JIRA. BE SURE TO DO THIS FOR BOTH REPOS (puppetdb and pe-puppetdb-extensions) Add Comment
Jira (PDB-4350) Bump versions, push directly, and tag (PuppetDB 6.3.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4350 Bump versions, push directly, and tag (PuppetDB 6.3.2) Issue Type: Task Assignee: Zachary Kent Created: 2019/04/23 4:56 PM Due Date: 2019/04/26 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) (if you're making the first release off a new branch you may already have done some of this) Check that there aren't any essential updates to ezbake needed in this release before pushing a non-snapshot version and tagging. Perform a test promotion: With the version still a -SNAPSHOT, and all commmits merged into the release branch, attempt a test promotion by running the "manual promotion kickoff" job. This is to make sure the pipelines will work when the actual tag is promoted. Set the real version for release: Remove the -SNASPHOT portion of the verison in project.clj in puppetdb and push directly to the branch you're releasing. Go into the 'release-new' hipchat room to make yourself a tag ! tag puppetdb at with Remove the -SNASPHOT portions of the versions in the file 'version' and project.clj in pe-puppetdb-extensions and push directly to the branch
Jira (PDB-4352) Update winston (PuppetDB 6.3.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4352 Update winston (PuppetDB 6.3.2) Issue Type: Task Assignee: Zachary Kent Created: 2019/04/23 4:56 PM Due Date: 2019/05/01 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) Update winston to make these tickets more accurate for next time. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PDB-4351) Check builds, promote to PE (PuppetDB 6.3.2)
Title: Message Title Nirupama Mantha created an issue PuppetDB / PDB-4351 Check builds, promote to PE (PuppetDB 6.3.2) Issue Type: Task Assignee: Zachary Kent Created: 2019/04/23 4:56 PM Due Date: 2019/04/27 Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) Check that all the builds are green. Choose the tab for your branch over at https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/, then run the "manual promotion kickoff" job. Once builds are promoted push SNAPSHOT versions to both pdb and pdbext github repos targeting the next release. Remember to revert pe-puppetdb-extensions to reading the version from the file
Jira (PDB-4348) Merge-up, branch, and create pipelines (PuppetDB 6.3.2)
Title: Message Title
Nirupama Mantha created an issue
PuppetDB / PDB-4348
Merge-up, branch, and create pipelines (PuppetDB 6.3.2)
Issue Type:
Task
Assignee:
Zachary Kent
Created:
2019/04/23 4:56 PM
Due Date:
2019/04/23
Priority:
Normal
Reporter:
Nirupama Mantha
(Initial planned release date: 2019-04-30) Is the code ready for release? Check that the latest nightly ("Periodic") build was green. You only need to check the links that are relevant to the release that you're preparing (for example, doing a release that doesn't include LTS).
master: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/master
6.0.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/6.0.x/
5.2.x: https://cinext-jenkinsmaster-enterprise-prod-1.delivery.puppetlabs.net/view/puppetdb/view/5.2.x/
pe-puppetdb-extensions travis builds: https://travis-ci.com/puppetlabs/pe-puppetdb-extensions/branches
Do merge-ups:
Merge 5.2.x -> 6.0.x
Merge
Jira (PUP-9684) Communicate scope and timeline of next release (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9684 Communicate scope and timeline of next release (Puppet Platform 6.4.2) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:55 PM Due Date: 2019/05/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9683) Update Confluence and JIRA based on release (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9683 Update Confluence and JIRA based on release (Puppet Platform 6.4.2) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:54 PM Due Date: 2019/05/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9680) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9680 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.4.2) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:54 PM Due Date: 2019/04/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9681) Publish documentation and updates and release notes (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9681 Publish documentation and updates and release notes (Puppet Platform 6.4.2) Issue Type: Task Assignee: Jean Bond Created: 2019/04/23 4:54 PM Due Date: 2019/04/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9682) Send release announcement (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9682 Send release announcement (Puppet Platform 6.4.2) Issue Type: Task Assignee: Eric Griswold Created: 2019/04/23 4:54 PM Due Date: 2019/04/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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.4.2 is now available".
Jira (PUP-9676) Prepare JIRA and Confluence for release (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9676 Prepare JIRA and Confluence for release (Puppet Platform 6.4.2) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:53 PM Due Date: 2019/04/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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.4.2 and puppet-agent 6.4.2 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-9677) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9677 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.4.2) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:53 PM Due Date: 2019/04/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 HipChat) 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-9678) Prepare documentation updates and release notes (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9678 Prepare documentation updates and release notes (Puppet Platform 6.4.2) Issue Type: Task Assignee: Jean Bond Created: 2019/04/23 4:53 PM Due Date: 2019/04/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9679) Prepare release announcement (Puppet Platform 6.4.2)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9679 Prepare release announcement (Puppet Platform 6.4.2) Issue Type: Task Assignee: Bill Tang Created: 2019/04/23 4:53 PM Due Date: 2019/04/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9675) Puppet Platform 6.4.2 Release - 2019-04-30
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9675 Puppet Platform 6.4.2 Release - 2019-04-30 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/04/23 4:53 PM Due Date: 2019/04/30 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.4.2 Release - 2019-04-30 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9673) Update Confluence and JIRA based on release (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9673 Update Confluence and JIRA based on release (Puppet Platform 6.0.9) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:49 PM Due Date: 2019/05/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9674) Communicate scope and timeline of next release (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9674 Communicate scope and timeline of next release (Puppet Platform 6.0.9) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:49 PM Due Date: 2019/05/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9672) Send release announcement (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9672 Send release announcement (Puppet Platform 6.0.9) Issue Type: Task Assignee: Eric Griswold Created: 2019/04/23 4:49 PM Due Date: 2019/04/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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.0.9 is now available".
Jira (PUP-9670) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9670 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 6.0.9) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:48 PM Due Date: 2019/04/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9666) Prepare JIRA and Confluence for release (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9666 Prepare JIRA and Confluence for release (Puppet Platform 6.0.9) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:48 PM Due Date: 2019/04/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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.0.9 and puppet-agent 6.0.9 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y
Jira (PUP-9668) Prepare documentation updates and release notes (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9668 Prepare documentation updates and release notes (Puppet Platform 6.0.9) Issue Type: Task Assignee: Jean Bond Created: 2019/04/23 4:48 PM Due Date: 2019/04/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9669) Prepare release announcement (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9669 Prepare release announcement (Puppet Platform 6.0.9) Issue Type: Task Assignee: Bill Tang Created: 2019/04/23 4:48 PM Due Date: 2019/04/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9671) Publish documentation and updates and release notes (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9671 Publish documentation and updates and release notes (Puppet Platform 6.0.9) Issue Type: Task Assignee: Jean Bond Created: 2019/04/23 4:48 PM Due Date: 2019/04/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9667) Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.9)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9667 Declare Stop Ship Line (code complete) milestone (Puppet Platform 6.0.9) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:48 PM Due Date: 2019/04/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 HipChat) 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-9665) Puppet Platform 6.0.9 Release - 2019-04-30
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9665 Puppet Platform 6.0.9 Release - 2019-04-30 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/04/23 4:47 PM Due Date: 2019/04/30 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 6.0.9 Release - 2019-04-30 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-126) Support WinRM with Kerberos
Title: Message Title Ethan Brown commented on BOLT-126 Re: Support WinRM with Kerberos Blocking this on the merge of the PR that I put up for the WinRM gem at https://github.com/WinRb/WinRM/pull/302 to fix the Kerberos corruption. We'll want a new gem to be cut prior to integrating Kerberos support into Bolt. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9664) Communicate scope and timeline of next release (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9664 Communicate scope and timeline of next release (Puppet Platform 5.5.14) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:38 PM Due Date: 2019/05/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9663) Update Confluence and JIRA based on release (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9663 Update Confluence and JIRA based on release (Puppet Platform 5.5.14) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:38 PM Due Date: 2019/05/01 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9662) Send release announcement (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9662 Send release announcement (Puppet Platform 5.5.14) Issue Type: Task Assignee: Eric Griswold Created: 2019/04/23 4:38 PM Due Date: 2019/04/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 5.5.14 is now available".
Jira (PUP-9659) Prepare release announcement (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9659 Prepare release announcement (Puppet Platform 5.5.14) Issue Type: Task Assignee: Bill Tang Created: 2019/04/23 4:37 PM Due Date: 2019/04/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9660) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9660 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 5.5.14) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:37 PM Due Date: 2019/04/29 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 ‘Platform Core’ HipChat room for go/no-go decision. 4) Send email indicating Ready To Ship milestone has been achieved. Add Comment
Jira (PUP-9661) Publish documentation and updates and release notes (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9661 Publish documentation and updates and release notes (Puppet Platform 5.5.14) Issue Type: Task Assignee: Jean Bond Created: 2019/04/23 4:37 PM Due Date: 2019/04/30 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-9657) Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9657 Declare Stop Ship Line (code complete) milestone (Puppet Platform 5.5.14) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:36 PM Due Date: 2019/04/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 HipChat) 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-9656) Prepare JIRA and Confluence for release (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9656 Prepare JIRA and Confluence for release (Puppet Platform 5.5.14) Issue Type: Task Assignee: Nirupama Mantha Created: 2019/04/23 4:36 PM Due Date: 2019/04/24 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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 5.5.14 and puppet-agent 5.5.14 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform
Jira (PUP-9655) Puppet Platform 5.5.14 Release - 2019-04-30
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9655 Puppet Platform 5.5.14 Release - 2019-04-30 Issue Type: Epic Assignee: Nirupama Mantha Created: 2019/04/23 4:36 PM Due Date: 2019/04/30 Priority: Normal Reporter: Nirupama Mantha Puppet Platform 5.5.14 Release - 2019-04-30 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9658) Prepare documentation updates and release notes (Puppet Platform 5.5.14)
Title: Message Title Nirupama Mantha created an issue Puppet / PUP-9658 Prepare documentation updates and release notes (Puppet Platform 5.5.14) Issue Type: Task Assignee: Jean Bond Created: 2019/04/23 4:37 PM Due Date: 2019/04/26 Labels: release Priority: Normal Reporter: Nirupama Mantha (Initial planned release date: 2019-04-30) 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-7513) Explore puppet-server FIPS compliance work
Title: Message Title Eric Thompson updated an issue Puppet / PUP-7513 Explore puppet-server FIPS compliance work Change By: Eric Thompson Summary: Explore puppet-server and PE service FIPS compliance options 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 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-7137) Support Using TPM-Backed SSL Private Keys for Puppet Agent
Title: Message Title Josh Cooper updated an issue Puppet / PUP-7137 Support Using TPM-Backed SSL Private Keys for Puppet Agent Change By: Josh Cooper Sprint: Coremunity Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1266) we should ship a yaml plan oob
Title: Message Title Yasmin Rajabi created an issue Puppet Task Runner / BOLT-1266 we should ship a yaml plan oob Issue Type: Improvement Assignee: Unassigned Created: 2019/04/23 2:15 PM Priority: Normal Reporter: Yasmin Rajabi it would be helpful to get started if there was a yaml plan that shipped with bolt Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1263) Rerun should create default project directory when neccessary or silently fail
Title: Message Title Alex Dreyer assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-1263 Rerun should create default project directory when neccessary or silently fail Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-3041) Implement a priority queue with a deadline for command processing
Title: Message Title Nick Walker commented on PDB-3041 Re: Implement a priority queue with a deadline for command processing I think given the situation it might make sense to prioritize different commands. If a customer doesn't use exported resources or pdb query much they may not care about catalogs. Each customer might make a different determination on what is important but we should ship a good default. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9585) Do not output password for user type if it is marked Sensitive
Title: Message Title Kris Bosland updated an issue Puppet / PUP-9585 Do not output password for user type if it is marked Sensitive Change By: Kris Bosland Sprint: Coremunity Grooming Platform Core KANBAN Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1231) Use targets instead of nodes in v2 inventory
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1231 Use targets instead of nodes in v2 inventory Change By: Cas Donoghue Fix Version/s: BOLT Next Fix Version/s: BOLT 1.17.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1244) SELinux management does not work on localhost
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1244 SELinux management does not work on localhost Change By: Cas Donoghue Fix Version/s: BOLT Next Fix Version/s: BOLT 1.17.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-843) Generate a "rerun" file after every command
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-843 Generate a "rerun" file after every command Change By: Cas Donoghue Fix Version/s: BOLT Next Fix Version/s: BOLT 1.17.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1196) bolt-inventory-pdb examples in public documentation are incorrect
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1196 bolt-inventory-pdb examples in public documentation are incorrect Change By: Cas Donoghue Fix Version/s: BOLT Next Fix Version/s: BOLT 1.17.0 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1264 Allow puppetdb plugin to set host and name independently Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1263) Rerun should create default project directory when neccessary or silently fail
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1263 Rerun should create default project directory when neccessary or silently fail Change By: Alex Dreyer Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1109) Create plugin hook for populating inventory groups dynamically
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1109 Create plugin hook for populating inventory groups dynamically Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1265) target-lookup plugin to discover targets from a terraform state file.
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1265 target-lookup plugin to discover targets from a terraform state file. Issue Type: New Feature Assignee: Unassigned Created: 2019/04/23 9:01 AM Priority: Normal Reporter: Alex Dreyer Questions: How will the user specify where the statefile is? Is this config for the plugin or part of the lookup? How will the user specify the name of the target? How will the user specify connection info(host)? Is there anything we can do that is terraform specific? Add Comment
Jira (BOLT-1264) Allow puppetdb plugin to set host and name independently
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1264 Allow puppetdb plugin to set host and name independently Issue Type: New Feature Assignee: Unassigned Created: 2019/04/23 8:58 AM Priority: Normal Reporter: Alex Dreyer The puppetdb plugin will only accept a query that returns a certname and then set that certname to be the targets uri. For some users the node is not accessible through the certname so they need to lookup an IP address and set the name and certname of the target separately. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1231) Use targets instead of nodes in v2 inventory
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1231 Use targets instead of nodes in v2 inventory Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1232) Document experimental v2 Inventory
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-1232
Document experimental v2 Inventory
Change By:
Alex Dreyer
Release Notes Summary:
Inventory version 2. This new inventory format is under development but you can experiment with it by adding {{version: 2}} to the top of your inventory file. (link to docs)
Release Notes:
New Feature
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at https://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1232) Document experimental v2 Inventory
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1232 Document experimental v2 Inventory Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1232) Document experimental v2 Inventory
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-1232 Document experimental v2 Inventory Change By: Alex Dreyer Labels: docs Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9654) Add support for encrypted hocon files.
Title: Message Title Henrik Lindberg assigned an issue to Unassigned Puppet / PUP-9654 Add support for encrypted hocon files. Change By: Henrik Lindberg Assignee: Thomas Hallgren Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9654) Add support for encrypted hocon files.
Title: Message Title Henrik Lindberg commented on PUP-9654 Re: Add support for encrypted hocon files. As I understand how eyaml support is implemented in Puppet/ Hiera 5 it is the responsibility of the `eyaml_lookup_key` function to read the data file. A similar function for hocon would simply read a hocon file (parse it to a hash) and then use eyaml's support for encrypt and decrypt. All of this can be implemented in a separate module (no need for it to be in Puppet itself). Given that the interest in hocon has not been great I doubt that this will be added to core puppet - maybe if first proven to be used by many as a separate module... Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-1263) Rerun should create default project directory when neccessary or silently fail
Title: Message Title Alex Dreyer created an issue Puppet Task Runner / BOLT-1263 Rerun should create default project directory when neccessary or silently fail Issue Type: Bug Assignee: Unassigned Created: 2019/04/23 8:28 AM Priority: Normal Reporter: Alex Dreyer When there is no project directory bolt will fail to create a .rerun.json file. It should either create the default project directly ~/.puppetlabs/bolt or fail before it writes the file. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-1262) File upload hangs, task wrapper does not respect run-as owner
Title: Message Title Cas Donoghue updated an issue Puppet Task Runner / BOLT-1262 File upload hangs, task wrapper does not respect run-as owner Change By: Cas Donoghue Summary: File upload hangs when destination file exists and cannot be deleted by user , task wrapper does not respect run-as owner In the case where a user specified with run-as tried to upload a file to a destination owned by a user with different privilages a command prompt is raised which causes the command to hang indefinitely. By adding the -f flag to the mv command an appropriate permission error is raised and the operation does not hang. When using the task wrapper, the tempfile is written with the permissions of the user who ran the command and not the run-as user. https://github.com/puppetlabs/bolt/blob/55de205f60b5ca69c1812cec18ef2bec8db47f1b/lib/bolt/transport/local/shell.rb#L70 Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (PUP-9654) Add support for encrypted hocon files.
Title: Message Title Robert August Vincent II created an issue Puppet / PUP-9654 Add support for encrypted hocon files. Issue Type: New Feature Assignee: Thomas Hallgren Components: Hiera & Lookup Created: 2019/04/23 7:45 AM Priority: Normal Reporter: Robert August Vincent II As requested in HI-524, a Hiera, version 5 lookup_key function for encrypted hocon should be added. According to Henrik Lindberg, this would be trivial to implement. Add Comment This message was sent by Atlassian JIRA
Jira (PUP-9642) puppet device permissions preventing reading dirs
Title: Message Title David Schmitt commented on PUP-9642 Re: puppet device permissions preventing reading dirs Dimitri Tischenko The long-term solution is to not run puppet device as root. I'd love to hear your opinion about that. Meanwhile I've got some code changes in https://github.com/puppetlabs/puppet/pull/7483 which will likely fix the initialisation problem. I'm a bit concerned that it went away with 6.4, because that means that there is sometihng else going on that I do not fully understand yet (or I have messed up my testing). Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-9502) codesigning puppet executables on macOS 10.14
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-9502
codesigning puppet executables on macOS 10.14
Change By:
Gheorghe Popescu
Release Notes Summary:
Fixed user management on OS X 10.14A couple of changes need to be made to our documentation on the things that we need to whitelist under Full Disk Access to be able to use all the puppet functionalities on OS X 10.14Whitelist under Full Disk Access the parent process that triggers puppet run. For example: - sshd - run puppet from a remote machine trough SSH commands - terminal.app - runt puppet commands from terminal - pxp-agent - run puppet in a master-agent infrastructure(for example in PE)Also there are some limitations for User management: - puppet is not able to change the UID or the home directory of an existing user, trying to do this will end-up with an error: " OS X version 10 \ .14 does not allow changing #{field} using puppet"
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
Jira (PUP-9502) codesigning puppet executables on macOS 10.14
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-9502
codesigning puppet executables on macOS 10.14
Change By:
Gheorghe Popescu
Release Notes Summary:
Fixed user management on OS X 10.14A couple of changes need to be made to our documentation on the things that we need to whitelist under Full Disk Access to be able to use all the puppet functionalities on OS X 10.14Whitelist under Full Disk Access the parent process that triggers puppet run. For example: - sshd - run puppet from a remote machine trough SSH commands - terminal.app - runt puppet commands from terminal - pxp-agent - run puppet in a master-agent infrastructure(for example in PE)Also there are some limitations for User management: - puppet is not able to change the UID or the home directory of an existing user, trying to do this will end-up with an error:" OS X version 10\.14 does not allow changing #{field} using puppet"
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send
Jira (PUP-9502) codesigning puppet executables on macOS 10.14
Title: Message Title
Gheorghe Popescu updated an issue
Puppet / PUP-9502
codesigning puppet executables on macOS 10.14
Change By:
Gheorghe Popescu
Release Notes Summary:
Fixed user management on OS X 10.14 A couple of changes need to be made to our documentation on the things that we need to whitelist under Full Disk Access to be able to use all the puppet functionalities on OS X 10.14Whitelist under Full Disk Access the parent process that triggers puppet run. For example: - sshd - run puppet from a remote machine trough SSH commands - terminal.app - runt puppet commands from terminal - pxp-agent - run puppet in a master-agent infrastructure(for example in PE)Also there are some limitations for User management: - puppet is not able to change the UID or the home directory of an existing user, trying to do this will end-up with an error: " OS X version 10.14 does not allow changing #{field} using puppet"
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email
Jira (PUP-9502) codesigning puppet executables on macOS 10.14
Title: Message Title Gheorghe Popescu updated an issue Puppet / PUP-9502 codesigning puppet executables on macOS 10.14 Change By: Gheorghe Popescu Release Notes Summary: Fixed user management on OS X 10.14A couple of changes need to be made to our documentation on the things that we need to whitelist under Full Disk Access to be able to use all the puppet functionalities on OS X 10.14Whitelist under Full Disk Access the parent process that triggers puppet run. For example: - sshd - run puppet from a remote machine trough SSH commands - terminal.app - runt puppet commands from terminal - pxp-agent - run puppet in a master-agent infrastructure(for example in PE) Also there are some limitations for User management: - puppet is not able to change the UID or the home directory of an existing user, trying to do this will end-up with an error: Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at
