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:

• Replace Fedora 41 with Fedora 43 in the Testing Farm workflow matrix and supported platforms, and bump the associated Ansible version to 2.20.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates Testing Farm CI to drop Fedora 41 and start testing on Fedora 43, including workflow logic and matrix configuration changes.

Flow diagram for supported Fedora platform resolution in CI

flowchart TD
  A[Start_Workflow] --> B[Load_meta_main_yml]
  B --> C{galaxy_tags_contains_fedora}
  C -->|no| D[Do_not_add_generic_Fedora_versions]
  C -->|yes| E[Add_Fedora_42_to_supported_platforms]
  E --> F[Add_Fedora_43_to_supported_platforms]

  F --> G[Check_for_specific_Fedora_versions_in_galaxy_tags]
  G --> H[Build_Testing_Farm_Matrix]
  H --> I[Run_CI_on_Fedora_42]
  H --> J[Run_CI_on_Fedora_43]
  H --> K[Run_CI_on_other_platforms]
  D --> G

Loading

File-Level Changes

Change	Details	Files
Update supported Fedora versions in Testing Farm workflow generation logic.	Remove Fedora 41 from the automatically constructed supported_platforms list. Ensure Fedora 42 remains in the supported_platforms list. Add Fedora 43 to the supported_platforms list so new releases are tested.	.github/workflows/tft.yml
Adjust Testing Farm CI matrix to align with new Fedora targets and Ansible versions.	Remove the Fedora-41 / Ansible 2.17 test combination from the matrix. Keep Fedora-42 testing but bump its associated Ansible version to 2.19 if not already. Introduce a new Fedora-43 matrix entry using Ansible 2.20 for coverage on the latest Fedora release. Leave CentOS matrix entries unchanged.	.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 left some high level feedback:

• Consider defining the Fedora versions and corresponding Ansible versions in a single shared variable or matrix and reusing it for both supported_platforms construction and the strategy.matrix.include list to avoid duplication and reduce the chance of inconsistencies when updating versions in the future.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider defining the Fedora versions and corresponding Ansible versions in a single shared variable or matrix and reusing it for both `supported_platforms` construction and the `strategy.matrix.include` list to avoid duplication and reduce the chance of inconsistencies when updating versions in the future.

---

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.}

[sfeifer]

Looks good