ci: use ANSIBLE_INJECT_FACT_VARS=false by default for testing

[richm]

Ansible 2.20 has deprecated the use of Ansible facts as variables. For
example, ansible_distribution is now deprecated in favor of
ansible_facts["distribution"]. This is due to making the default
setting INJECT_FACTS_AS_VARS=false. For now, this will create WARNING
messages, but in Ansible 2.24 it will be an error.

In order to ensure that commits and PRs conform to this, use
ANSIBLE_INJECT_FACT_VARS=false by default in our CI testing.

Update README-ostree.md if needed.

See https://docs.ansible.com/projects/ansible/latest/porting_guides/porting_guide_core_2.20.html#inject-facts-as-vars

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

Summary by Sourcery

Update CI Ansible configuration and documentation to disable fact injection as vars and use the new ansible_facts-based access pattern.

CI:

• Set ANSIBLE_INJECT_FACT_VARS to false in qemu-kvm integration tests workflow.
• Pass SR_ANSIBLE_INJECT_FACT_VARS=false into the TFT GitHub Actions job environment.

Documentation:

• Update README-ostree to reference ansible_facts["distribution"] and ansible_facts["distribution_version"] instead of deprecated fact variables.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Configure CI to run with Ansible facts not injected as variables and update documentation to reference the new ansible_facts access pattern.

File-Level Changes

Change	Details	Files
Run all GitHub Actions Ansible-based tests with fact variables injection disabled to surface deprecated fact usage.	Set ANSIBLE_INJECT_FACT_VARS="false" in the qemu-kvm integration tests workflow environment so Ansible facts are no longer injected as top-level variables. Introduce SR_ANSIBLE_INJECT_FACT_VARS=false in the TFT workflow Terraform variable exports so downstream test runs also use the new fact injection behavior.	.github/workflows/qemu-kvm-integration-tests.yml .github/workflows/tft.yml
Update documentation to describe the new Ansible facts access pattern.	Replace references to ansible_distribution and ansible_distribution_version with ansible_facts["distribution"] and ansible_facts["distribution_version"] in the OSTree README to align with Ansible 2.20 deprecations and CI behavior.	README-ostree.md

---

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:

• You set SR_ANSIBLE_INJECT_FACT_VARS=false in the TFT workflow, but there’s no corresponding usage shown here; double-check that the downstream scripts or Terraform actually read this variable, or rename it to match whatever the consumer expects.
• In the qemu-kvm integration workflow you use ANSIBLE_INJECT_FACT_VARS="false"; consider aligning the naming with the Ansible config option (INJECT_FACTS_AS_VARS) or adding a brief comment so it’s clear this is the env var that controls that setting.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- You set `SR_ANSIBLE_INJECT_FACT_VARS=false` in the TFT workflow, but there’s no corresponding usage shown here; double-check that the downstream scripts or Terraform actually read this variable, or rename it to match whatever the consumer expects.
- In the qemu-kvm integration workflow you use `ANSIBLE_INJECT_FACT_VARS="false"`; consider aligning the naming with the Ansible config option (`INJECT_FACTS_AS_VARS`) or adding a brief comment so it’s clear this is the env var that controls that setting.

---

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