[chkp-ameera]

Red Hat's Automation Hub certification review of 7.1.0 asked for the changes below. Automation Hub doesn't accept the same version twice, so this is released as 7.1.1. The modules and plugins are unchanged.

Required change: minimum ansible-core version

• meta/runtime.yml: requires_ansible: '>=2.16.0' (was >=2.15.0). Ansible Automation Platform no longer supports ansible-core 2.15.
• CI: drop the stable-2.15 sanity job. The stable-2.16 job already runs on Python 3.12, as Red Hat requested.

README and test config

1. Add a Support section that explains the Create issue button on Automation Hub.
2. Remove the "Ansible 2.9+ is required" line, which conflicted with meta/runtime.yml.
3. Supported Python versions: 3.10 and newer, instead of 2.7. The same is declared in a new tests/config.yml (python_requires: ">=3.10").
4. Add installation instructions for Automation Hub, including authentication. The token is passed through an environment variable, not stored in ansible.cfg.
5. Management Proxy section:
   • Host the diagram in this repository (docs/images/mgmt_proxy.png) instead of a personal GitHub account. It's linked with an absolute URL, as Red Hat's template requires, so it shows after this PR is merged.
   • Replace the removed mgmt_proxy enabled=True setup with the ansible_checkpoint_mgmt_proxy_enabled inventory variable from 7.1.0.

Release

• galaxy.yml: version 7.1.1.
• CHANGELOG.rst: new 7.1.1 section. Dropping ansible-core 2.15 is listed under Breaking Changes, with who is affected. I also clarified the 7.1.0 Management Proxy entry: without the new variable, requests go to the Management Server's own Gaia API instead of being forwarded to the target gateway.

Testing

• ansible-test sanity passes on ansible-core 2.16.3 with Python 3.11.
• A test build of the collection gives version 7.1.1 and requires_ansible: '>=2.16.0', and includes LICENSE, tests/config.yml and the image.
• Not run locally:
  • Sanity on Python 3.12: the build container's Python 3.12 is broken. The CI stable-2.16 job covers it.
  • The unit tests: they fail to import units.modules.utils both before and after this change, and CI doesn't run them.

🤖 Generated with Claude Code