ci: Add Fedora 43, remove Fedora 41 from Testing Farm CI

[richm]

Add Fedora 43, remove Fedora 41 from Testing Farm CI

Signed-off-by: Rich Megginson rmeggins@redhat.com

Summary by Sourcery

CI:

• Adjust Testing Farm CI workflow to test on Fedora 42 and 43 instead of Fedora 41, updating corresponding Ansible versions.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI to drop Fedora 41 and add Fedora 43, including adjusting supported platform detection and the test matrix with appropriate Ansible versions.

Flow diagram for updated supported_platforms detection in Testing Farm CI

flowchart TD
  A[Read meta_main meta/main.yml] --> B[Extract galaxy_tags with yq]
  B --> C{Contains tag matching fedora$?}
  C -- Yes --> D[Append Fedora-42 to supported_platforms]
  D --> E[Append Fedora-43 to supported_platforms]
  C -- No --> F[Do not add generic Fedora versions]

  B --> G{Contains tag matching fedora\d+$?}
  G -- Yes --> H[Use specific Fedora version tags from meta_main]
  G -- No --> I[No specific Fedora versions added]

Loading

File-Level Changes

Change	Details	Files
Update supported Fedora versions in the Testing Farm workflow script logic.	Stop appending Fedora-41 to the supported_platforms list when Fedora is detected in galaxy_tags. Continue appending Fedora-42 and additionally append Fedora-43 to the supported_platforms list.	.github/workflows/tft.yml
Adjust Testing Farm CI matrix to target newer Fedora and Ansible versions.	Remove the Fedora-41 platform entry using Ansible 2.17 from the matrix include list. Keep Fedora-42 in the matrix and associate it with Ansible 2.19. Add Fedora-43 to the matrix and associate it with Ansible 2.20.	.github/workflows/tft.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}