fix: Avoid setting ansible_managed variable

[martinpitt]

Cause: The test used a temporary variable ansible_managed, but that is a "magic" string constant. Ansible 2.19 does not permit assigning to it any more.

Consequence: Tests failed with Ansible 2.19.

Fix: Rename the variable.

---

This should fix the F42/Ansible 2.19 failure introduced in #60

Summary by Sourcery

Prevent tests from assigning to the reserved ansible_managed variable to restore compatibility with Ansible 2.19

Bug Fixes:

• Rename the temporary ansible_managed variable to __ansible_managed in tests to avoid conflicts

Tests:

• Update check_present_header.yml and check_not_present_header.yml to use __ansible_managed in assertions and vars

[sourcery-ai]

Reviewer's Guide

Tests have been updated to avoid assigning to the magic ansible_managed variable by renaming it to __ansible_managed in both presence and absence assertion tasks, ensuring compatibility with Ansible 2.19.

File-Level Changes

Change	Details	Files
Rename test variable to avoid magic constant assignment	Changed assert conditions to check __ansible_managed instead of ansible_managed Updated vars section to define __ansible_managed via lookup template Retained fingerprint logic without modification	tests/tasks/check_not_present_header.yml tests/tasks/check_present_header.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 @martinpitt - 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.}

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Please upload report for BASE (main@6099174). Learn more about missing BASE report.

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #61   +/-   ##
=======================================
  Coverage        ?   52.31%           
=======================================
  Files           ?        1           
  Lines           ?      346           
  Branches        ?        0           
=======================================
  Hits            ?      181           
  Misses          ?      165           
  Partials        ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[martinpitt]

[citest]

[martinpitt]

remaining failure reproduces locally:

tox -e qemu-ansible-core-2.19 -- --image-name fedora-42 --log-level=debug tests/tests_multiple_sudoers.yml 
qemu-ansible-core-2.19: install_deps> python -I -m pip install --pre 'ansible-core==2.19.

Error is:

access to attribute 'append' of 'list' object is unsafe.

This is due to ansible/ansible#85202 . I fixed that, but it now still fails later on an inscrutable syntax error during validation. That smells similar to linux-system-roles/ssh#189