Closed vitorbaptista closed 1 year ago
Hi,
Which version of Ansible are you using?
This looks like a breaking change with a recent version of Ansible because this wasn't an issue back when v2.2.0 shipped.
This is a problem with ansible 2.9.6 (which I am currently stuck with temporarily).
What fixed it was to change this line: https://github.com/nickjj/ansible-docker/blob/master/tasks/main.yml#L142
I changed it to the following:
meta: "flush_handlers"
(Basically just removing the ansible.builtin
prefix.
Not ideal, but works for now. Still pending to test whether it works with a newer ansible version
Ah, that makes sense then.
Part of the changelog for v2.2.0 includes Bump minimum Ansible version to 2.10.0 to start using collection namespaces
. That's the Ansible feature that begins using ansible.builtin
namespaces.
I'm surprised the other tasks work with ansible.builtin
tho.
If I change the meta task to remove the namespace then ansible-lint
throws:
fqcn[action-core]: Use FQCN for builtin module actions (meta).
tasks/main.yml:141 Use `ansible.builtin.meta` or `ansible.legacy.meta` instead.
First of all, thank you for this great project.
I haven't pinned
nickjj/ansible-docker
version, so when deploying my product, I started seeing the following error:This was fixed by downgrading ansible-docker to v2.1.0. I'm guessing this breaking change wasn't intentional, otherwise it should be released as version v3.0.0 (assuming you're following the semantic versioning standard). Regardless, downgrading fixed it for me.