Import error `Consul.Agent` with `community.general.consul`

[mlech-reef]

Summary

Consul module is referring to consul.Consul.Agent which doesn't exist in py-consul

I tested with the version 12.0.0 and py-consul 1.5 and 1.6

~/Workspace/oss/community.general main• ❱ git sh-s
commit c984b89667dc2b555f3f4dbf43cfd2708e890681 (HEAD -> main, origin/main, origin/HEAD)
Author:     Alexei Znamensky <103110+russoz@users.noreply.github.com>
AuthorDate: Fri Nov 7 10:29:44 2025 +1300
Commit:     GitHub <noreply@github.com>
CommitDate: Fri Nov 7 10:29:44 2025 +1300

    docs style adjustments (#11037)
    
    docs adjustments
~/Workspace/oss/community.general main• ❱ rg 'Consul\.Agent'
plugins/modules/consul.py
229:    class PatchedConsulAgentService(consul.Consul.Agent.Service):

tmp/collections/ansible_collections/community/general/plugins/modules/consul.py
248:    class PatchedConsulAgentService(consul.Consul.Agent.Service):

Issue Type

Bug Report

Component Name

consul

Ansible Version

$ ansible --version
ansible [core 2.19.4]

Community.general Version

12.0.0

Configuration

$ ansible-config dump --only-changed
N/A

OS / Environment

Fedora Silverblue/Debian Trixie

Steps to Reproduce

Any usage of community.general.consul with most recent version of py-consul

Expected Results

It works without error

Actual Results

ImportError Consul.Agent

Code of Conduct

• I agree to follow the Ansible Code of Conduct

[ansibullbot]

Files identified in the description:

• plugins/modules/consul.py

If these files are incorrect, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @Ilgmi @apollo13 @sgargan
click here for bot help

[felixfontein]

I guess it has been removed from py-consul then, so you need to use an older version with the module. py-consul was changed in this commit: criteo/py-consul@37a5dd1#diff-87d94b41a52bb393bfca3dc4b47be3807560585a919ef66394f9fe6e20c216c2, which apparently first appeared in version 1.4.0. So any version before 1.4.0 probably still works (or at least it won't not work because of this specific issue).