Jira (PUP-11621) Drop Hiera 3 Requirement
Title: Message Title Michael Hashizume assigned an issue to Michael Hashizume Puppet / PUP-11621 Drop Hiera 3 Requirement Change By: Michael Hashizume Assignee: Michael Hashizume Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.465779.1661814931000.71609.1673390340057%40Atlassian.JIRA.
Jira (PDB-5573) Merge-up, branch, and create pipelines (Puppet Platform 7.22.0)
Title: Message Title
tefoji created an issue
PuppetDB / PDB-5573
Merge-up, branch, and create pipelines (Puppet Platform 7.22.0)
Issue Type:
Task
Assignee:
Arthur Lawson
Created:
2023/01/10 1:46 PM
Due Date:
2023/02/01
Priority:
Normal
Reporter:
tefoji
(Initial planned release date: 2023-02-07) 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).
jenkins: main
jenkins: 6.x
travis: puppetdb
travis: pe-puppetdb-extensions
Do merge-ups:
Merge 6.x -> main
Important: Do this for both the core puppetdb repo and the pe-puppetdb-extensions repo! These should be submitted as PRs and merged after tests pass, if there's anything remotely interesting about the merges. If the merges are boring, then direct push is fine. SKIP ALL REMAINING STEPS - We are leaving them here until we have a better place to document the process to create a new branch. When we release a new Y version we do it off of main and cut a maintained branch later (if at all). Then, prepare the branch for release:
If needed, create the branch (off of main, almost certainly)
Jira (PDB-5574) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5574 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.22.0) Issue Type: Task Assignee: Arthur Lawson Created: 2023/01/10 1:46 PM Due Date: 2023/02/01 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Ensure all tickets referenced in the commit log have the release's fixVersion, and ensure all tickets targeted at the release have a corresponding commit. You can do this manually by checking out the branches you will be releasing, ensuring they are in sync with the upstream puppetlabs repo, and running the rake task. bundle install; bundle exec rake release:reconcile[NEXT_VER,LAST_VER] This assumes you have the puppetdb repo as the cwd and the pe repo at ../pe-puppetdb-extensions. These can be overridden by the PDB_PATH and PDB_PE_PATH environment variables. The rake task will explain any mismatches that exist between Jira and the repos and ask you to investigate any tickets that do not start with a PDB ticket, (maint), (docs), or (i18n) Add Comment
Jira (PDB-5576) Bump versions, push directly, and tag (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5576 Bump versions, push directly, and tag (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478372.1673387185000.71562.1673387220725%40Atlassian.JIRA.
Jira (PDB-5577) Check builds, promote to PE (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5577 Check builds, promote to PE (Puppet Platform 7.22.0) Issue Type: Task Assignee: Arthur Lawson Created: 2023/01/10 1:46 PM Due Date: 2023/02/04 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Check that all the builds are green. The parameterized acceptance tests' upgrade_latest jobs in Jenkins are expected to fail at this point with an error like: Error: Could not update: Execution of '/usr/bin/yum -d 0 -e 0 -y install puppetdb-7.11.0-1.el7' returned 1: Error: Nothing to do Choose the tab for your branch over at https://jenkins-enterprise.delivery.puppetlabs.net/view/puppetdb/, then run the "Manual Kickoff" job with the GIT_SHA set to the git tag version and PROMOTION_ENABLED set to TRUE. If an enterprise-dist release branch has already been cut, rebuild the package pr
Jira (PDB-5576) Bump versions, push directly, and tag (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5576 Bump versions, push directly, and tag (Puppet Platform 7.22.0) Issue Type: Task Assignee: Arthur Lawson Created: 2023/01/10 1:46 PM Due Date: 2023/02/04 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) (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 and that the ezbake versions match between puppetdb and pe-puppetdb-extensions before pushing a non-snapshot version and tagging. Check that puppetdb and pe-puppetdb-extensions are on the same version of clj-parent, and that is the same clj-parent version that puppetserver will release with. Disable automatic promotions: If a PE release branch has not been cut, disable automatic promotions on the branch(es) you are releasing from. This is done via a PR to ci-job-configs, see https://github.com/puppetlabs/ci-job-configs/pull/6324/files for an example. Run the `tag-release` command: Change to a clean checkout of the relevant `puppetdb` branch (e.g. 6.x, main, ...). Run the `tag-release` script. This exampl
Jira (PDB-5578) Update ticket templates (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5578 Update ticket templates (Puppet Platform 7.22.0) Issue Type: Task Assignee: Arthur Lawson Created: 2023/01/10 1:46 PM Due Date: 2023/02/08 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) If appropriate, raise a PR to adjust the ticket templates more accurate for the next time. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PDB-5575) Draft release notes (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue PuppetDB / PDB-5575 Draft release notes (Puppet Platform 7.22.0) Issue Type: Task Assignee: Arthur Lawson Created: 2023/01/10 1:46 PM Due Date: 2023/02/05 Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Ensure all tickets have release notes. This query, once you've reconciled the Jira ticket fix versions in the previous step and configured the query with the current release version(s), will identify tickets whose release notes are not complete. Ask your team members to complete any tickets that need release notes (if the ticket's release note is simple you may write release notes for other people's tickets, but you certainly don't have to). Write release notes for the release based on the tickets found in the previous step. One of the simplest ways to gather release notes (once you've completed the step above to ensure every ticket that needs a release note has one) is to use this Jira query be sure to replace the fixVersions with the versions you are releasing and if you don't see release notes you'll need to verify that you're in List View and add the "Release Notes", "Release Notes Summary", and "fixVersion/s" columns to the page. All those view settings are configured in the top right via the two drop-downs below Share, Export, and Tools. Check any tickets for a docs tab with desired information. The release notes go in puppetdb\/documentation\/release_notes.markdown. Request review from the docs team by pinging @heston in the opened PR, at least one day before Ready to Ship
Jira (PDB-5578) Update ticket templates (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5578 Update ticket templates (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478374.1673387187000.71566.1673387220917%40Atlassian.JIRA.
Jira (PDB-5574) Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5574 Reconcile git commits, JIRA tickets, and versions (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478370.1673387183000.71558.1673387220529%40Atlassian.JIRA.
Jira (PDB-5575) Draft release notes (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5575 Draft release notes (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478371.1673387184000.71560.1673387220629%40Atlassian.JIRA.
Jira (PDB-5577) Check builds, promote to PE (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5577 Check builds, promote to PE (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478373.1673387186000.71564.1673387220820%40Atlassian.JIRA.
Jira (PDB-5573) Merge-up, branch, and create pipelines (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue PuppetDB / PDB-5573 Merge-up, branch, and create pipelines (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478369.1673387182000.71556.1673387220433%40Atlassian.JIRA.
Jira (PUP-11703) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11703 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/02 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11706) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11706 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478349.1673387146000.71542.1673387160897%40Atlassian.JIRA.
Jira (PUP-11708) Send release announcement (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11708 Send release announcement (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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 7.22.0 is now available"
Jira (PUP-11708) Send release announcement (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11708 Send release announcement (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478352.1673387148000.71546.1673387161017%40Atlassian.JIRA.
Jira (PUP-11711) Communicate scope and timeline of next release (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11711 Communicate scope and timeline of next release (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478355.1673387151000.71552.1673387161187%40Atlassian.JIRA.
Jira (PUP-11702) Prepare JIRA and Confluence for release (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11702 Prepare JIRA and Confluence for release (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/02 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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 7.22.0 and puppet-agent 7.22.0 to reference the “Fixed in” filters created above. 6) Update the community feedback filter for Puppet Platform X.y to reference the “I
Jira (PUP-11701) Puppet Platform 7.22.0 Release - 2023-02-07
Title: Message Title tefoji created an issue Puppet / PUP-11701 Puppet Platform 7.22.0 Release - 2023-02-07 Issue Type: Epic Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/07 Priority: Normal Reporter: tefoji Puppet Platform 7.22.0 Release - 2023-02-07 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11705) Prepare release announcement (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11705 Prepare release announcement (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Draft the release announcement using the guidance provided here. Paste the text of the announcement in a comment on this ticket and ping Parker Leach 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-11703) Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11703 Declare Stop Ship Line (code complete) milestone (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478345.1673387142000.71536.1673387160725%40Atlassian.JIRA.
Jira (PUP-11710) Update Confluence and JIRA based on release (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11710 Update Confluence and JIRA based on release (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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 description and rele
Jira (PUP-11711) Communicate scope and timeline of next release (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11711 Communicate scope and timeline of next release (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/09 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11706) Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11706 Declare Ready to Ship (go/no-go) milestone (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/06 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11707) Publish documentation and updates and release notes (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11707 Publish documentation and updates and release notes (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478350.1673387147000.71544.1673387160961%40Atlassian.JIRA.
Jira (PUP-11710) Update Confluence and JIRA based on release (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11710 Update Confluence and JIRA based on release (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478354.167338715.71550.1673387161128%40Atlassian.JIRA.
Jira (PUP-11704) Prepare documentation updates and release notes (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11704 Prepare documentation updates and release notes (Puppet Platform 7.22.0) Issue Type: Task Assignee: Parker Leach Created: 2023/01/10 1:45 PM Due Date: 2023/02/04 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11709) Schedule a retrospective (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11709 Schedule a retrospective (Puppet Platform 7.22.0) Issue Type: Task Assignee: Mae Caballes Created: 2023/01/10 1:45 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) Schedule a retrospective for this release. This should happen as soon as possible after the release, so that details are fresh in our heads. Ensure all current release leads are invited and that the Trello board is shared with them. Eric Griswold Parker Leach Aria Li Cas Donoghue Arthur Lawson Add Comment
Jira (PUP-11702) Prepare JIRA and Confluence for release (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11702 Prepare JIRA and Confluence for release (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478344.1673387141000.71534.1673387160670%40Atlassian.JIRA.
Jira (PUP-11707) Publish documentation and updates and release notes (Puppet Platform 7.22.0)
Title: Message Title tefoji created an issue Puppet / PUP-11707 Publish documentation and updates and release notes (Puppet Platform 7.22.0) Issue Type: Task Assignee: Parker Leach Created: 2023/01/10 1:45 PM Due Date: 2023/02/07 Labels: release Priority: Normal Reporter: tefoji (Initial planned release date: 2023-02-07) 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-11709) Schedule a retrospective (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11709 Schedule a retrospective (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478353.1673387149000.71548.1673387161074%40Atlassian.JIRA.
Jira (PUP-11705) Prepare release announcement (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11705 Prepare release announcement (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478347.1673387144000.71540.1673387160838%40Atlassian.JIRA.
Jira (PUP-11704) Prepare documentation updates and release notes (Puppet Platform 7.22.0)
Title: Message Title tefoji updated an issue Puppet / PUP-11704 Prepare documentation updates and release notes (Puppet Platform 7.22.0) Change By: tefoji Epic Link: PUP-11701 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478346.1673387143000.71538.1673387160780%40Atlassian.JIRA.
Jira (PUP-11691) Provide setting to report non-versioned path to resource when using versioned dirs
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-11691 Provide setting to report non-versioned path to resource when using versioned dirs Change By: Morgan Rhodes Epic Link: PUP-11658 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477092.1671051703000.71519.1673387040167%40Atlassian.JIRA.
Jira (PUP-11691) Provide setting to report non-versioned path to resource when using versioned dirs
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-11691 Provide setting to report non-versioned path to resource when using versioned dirs Change By: Morgan Rhodes Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477092.1671051703000.71518.1673387040070%40Atlassian.JIRA.
Jira (PUP-11688) Allow options to be passed to the pkg provider
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-11688 Allow options to be passed to the pkg provider Change By: Morgan Rhodes Epic Link: PUP-11659 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.476804.1670534477000.71506.1673386380112%40Atlassian.JIRA.
Jira (PUP-11688) Allow options to be passed to the pkg provider
Title: Message Title Morgan Rhodes commented on PUP-11688 Re: Allow options to be passed to the pkg provider Ok, talking to the dev team we should be able to pass `install_options` to the `pkg list` command. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.476804.1670534477000.71505.1673386320106%40Atlassian.JIRA.
Jira (PUP-11695) Windows package uninstall uses msi provider when exe provider available
Title: Message Title Morgan Rhodes commented on PUP-11695 Re: Windows package uninstall uses msi provider when exe provider available Hi GeorgesZ, It seems like there's an issue with that particular .net core sdk that doesn't accurately report how the package was installed. The code to check whether or not a package is a valid MSI is here, so you may be able to clear that registry key. Unfortunately since this is an issue with a specific package there's nothing we can do to resolve it. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477888.167287293.71499.1673386080105%40Atlassian.JIRA.
Jira (PUP-11696) Unless parameter of Exec evaluated before Requires
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-11696 Unless parameter of Exec evaluated before Requires Change By: Morgan Rhodes Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477892.1672895132000.71493.1673385600212%40Atlassian.JIRA.
Jira (PUP-11696) Unless parameter of Exec evaluated before Requires
Title: Message Title Morgan Rhodes commented on PUP-11696 Re: Unless parameter of Exec evaluated before Requires Hi Dagan McGregor, Does this work as expected if you run without --noop? --noop isn't a perfect simulation and these sorts of errors are hard to avoid in situations like this. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477892.1672895132000.71492.1673385600204%40Atlassian.JIRA.
Jira (PUP-11700) puppet generate types --environment doesn't accept full path
Title: Message Title Pat Riehecky commented on PUP-11700 Re: puppet generate types --environment doesn't accept full path Can you add those flags to `–help` as they are both missing Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478334.1673381987000.71489.1673385480211%40Atlassian.JIRA.
Jira (FACT-3174) Facter logging debugonce is O^2
Title: Message Title Morgan Rhodes updated an issue Facter / FACT-3174 Facter logging debugonce is O^2 Change By: Morgan Rhodes Epic Link: PUP-11659 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478019.167303725.71485.1673385360097%40Atlassian.JIRA.
Jira (FACT-3174) Facter logging debugonce is O^2
Title: Message Title Morgan Rhodes updated an issue Facter / FACT-3174 Facter logging debugonce is O^2 Change By: Morgan Rhodes Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478019.167303725.71484.1673385360049%40Atlassian.JIRA.
Jira (FACT-3175) Remove sys-filesystem monkey patch
Title: Message Title Morgan Rhodes updated an issue Facter / FACT-3175 Remove sys-filesystem monkey patch Change By: Morgan Rhodes Epic Link: PUP-11659 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478020.1673037606000.71483.1673385300209%40Atlassian.JIRA.
Jira (FACT-3175) Remove sys-filesystem monkey patch
Title: Message Title Morgan Rhodes updated an issue Facter / FACT-3175 Remove sys-filesystem monkey patch Change By: Morgan Rhodes Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478020.1673037606000.71482.1673385300161%40Atlassian.JIRA.
Jira (PUP-11697) rpm package installation: confusing error message when there is no such package
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-11697 rpm package installation: confusing error message when there is no such package Change By: Morgan Rhodes Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478029.1673258903000.71479.1673385180104%40Atlassian.JIRA.
Jira (PUP-11697) rpm package installation: confusing error message when there is no such package
Title: Message Title Morgan Rhodes commented on PUP-11697 Re: rpm package installation: confusing error message when there is no such package Hi Konrad Bucheli, Could you run again with --debug so we can better diagnose this issue? Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478029.1673258903000.71478.1673385180098%40Atlassian.JIRA.
Jira (PUP-11700) puppet generate types --environment doesn't accept full path
Title: Message Title Morgan Rhodes updated an issue Puppet / PUP-11700 puppet generate types --environment doesn't accept full path Change By: Morgan Rhodes Team: Phoenix Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478334.1673381987000.71458.1673384820042%40Atlassian.JIRA.
Jira (PUP-11700) puppet generate types --environment doesn't accept full path
Title: Message Title Morgan Rhodes commented on PUP-11700 Re: puppet generate types --environment doesn't accept full path Hi Pat Riehecky, You could do this by running `puppet generate types --environmentpath /etc/puppetlabs/code/environments --environment test` Please let us know if that doesn't work as expected. Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.478334.1673381987000.71457.1673384760137%40Atlassian.JIRA.
Jira (PUP-11526) Evaluate deferred functions lazily by default
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-11526
Evaluate deferred functions lazily by default
Change By:
Josh Cooper
This is a follow up to PUP-9323 so that deferred functions are evaluated lazily by default. Change Deferred functions are executed on the default setting for agent when the parameter added agent applies a catalog. A good example is to call Vault to lookup a Sensitive password. That way the password is never stored in PUP the catalog. For example, see [https://www.puppet.com/docs/puppet/7/deferring_functions.html#deferring_functions - 9323 deferred-function-example]Historically , may deferred functions were called before the catalog was enforced, which meant you couldn't use puppet to install dependencies needed by the deferred function. For example, to install gems, libraries, configuration needed to connect to vault.For this ticket, we want to change the default value of the {{preprocess_deferred}} setting so that they are not preprocessed by default. Instead they will be test changes as well evaluated during catalog application . In the vault example, the deferred function would be called when applying the {{File['/etc/secrets.conf']}} resource.
Add Comment
This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8)
Jira (PUP-11700) puppet generate types --environment doesn't accept full path
Title: Message Title
Pat Riehecky created an issue
Puppet / PUP-11700
puppet generate types --environment doesn't accept full path
Issue Type:
Improvement
Affects Versions:
PUP 7.20.0
Assignee:
Unassigned
Components:
Type System
Created:
2023/01/10 12:19 PM
Priority:
Normal
Reporter:
Pat Riehecky
When running `puppet generate types --environment /etc/puppetlabs/code/environments/test` I get an error: Could not find a directory environment named '/etc/puppetlabs/code/environments/test' {{}} It would be helpful if I could use full paths.{}
Add Comment
Jira (PUP-11526) Evaluate deferred functions lazily by default
Title: Message Title Aria Li assigned an issue to Aria Li Puppet / PUP-11526 Evaluate deferred functions lazily by default Change By: Aria Li Assignee: Aria Li Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.445008.1651113322000.71419.1673378820045%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Fix Version/s: PDB 7.12.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477993.1672942656000.71234.1673366940109%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Affects Version/s: PDB 7.12.0 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477993.1672942656000.71233.1673366940059%40Atlassian.JIRA.
Jira (PDB-5568) Query failure when ordering by json element
Title: Message Title Austin Blatt updated an issue PuppetDB / PDB-5568 Query failure when ordering by json element Change By: Austin Blatt Fix Version/s: PDB 7.12.1 Add Comment This message was sent by Atlassian Jira (v8.20.11#820011-sha1:0629dd8) -- 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.477993.1672942656000.71235.1673366940157%40Atlassian.JIRA.
