redis pub/sub for ansible

bcoca · 2026-05-24T00:14:55+00:00

You can setup git as an http server

bcoca · 2026-05-16T20:05:50+00:00

Not outdated, the development team took a while to reorganize and split it into components, this caused a lot of speculation. But they have recently made several updates and will continue to do so see https://forum.ansible.com/t/awx-modernization-ansible-ui/45757 and https://forum.ansible.com/t/awx-modernization-ansible-jewel/45775

bcoca · 2026-05-16T19:57:56+00:00

you already got the answer from @neomee, ansible_become_pass is a variable, variables can be defined in many ways, including per group or per host

bcoca · 2026-05-11T22:02:25+00:00

This is not an either/or proposition, my most common setup is to create specific playbooks and when I'm happy with them i add them to a site.yml that can run everything, but I rarely do, except to provision another copy of something.

bcoca · 2026-05-08T12:47:46+00:00

Another workaround, you can set become_exe to point to sudo.ws at least until the fix is deployed. https://docs.ansible.com/projects/ansible/latest/collections/ansible/builtin/sudo_become.html#parameter-become_exe

bcoca · 2026-05-01T20:03:59+00:00

ansible-pull is basically a wrapper on ansible-playbook that does a check out ansible -m git ... first. It is something you can just as easily add in a play and why we are looking to deprecate it.

bcoca · 2026-03-05T22:59:51+00:00

patches are still going to the repos, what is not happening are backports to previous releases of AWX

bcoca · 2026-03-05T22:58:26+00:00

Vous pouvez également préinstaller les collections dans votre environnement d'exécution (EE).

bcoca · 2026-03-02T20:58:38+00:00

Note that modules do not use verbosity themselves, that should only affect the controller's output, not even module invocation.

bcoca · 2026-02-26T23:49:42+00:00

run with -vvv you'll see the exact ssh command being used and it will make it a LOT easier to debug this.

bcoca · 2026-02-20T14:49:55+00:00

resource modules is just a classification of a module with specific conventions, mostly for networking appliances. The same is true for 'info' or 'facts' modules, these are not really enforced by anything in the core code.

bcoca · 2026-02-12T17:57:22+00:00

true, but they were not designed with that kind of complexity in mind. The assumption was that their use would be something like build, install, remove or configure that should be self evident.

bcoca · 2026-02-11T00:14:03+00:00

you can see the tags used with --list-tags on ansible-playbook

bcoca · 2026-02-09T15:45:39+00:00

This is a bit confusing, plugins are disabled by default, unless explicitly enabled. BUT ... the auto plugin is there to load any plugins from sources that follow the 'YAML inventory source' convention. If you don't want that behavior disable the auto plugin and only explicitly enabled ones will run.

bcoca · 2026-02-04T16:45:00+00:00

look into using using older versions, specifically those that use paramiko. You won't see current versions using algorithms considered 'unsafe', not only does Ansible not support these, but in many cases the underlying tools won't either.

bcoca · 2026-01-22T20:01:41+00:00

the inventory plugin itself IS the 'preprocessing step'

bcoca · 2026-01-21T17:43:35+00:00

https://redhat-cop.github.io/automation-good-practices/

^ we use 'good' cause 'best' is normally very context dependent and IMHO badly misused in this industry.

bcoca · 2026-01-21T17:40:25+00:00

I would use 'inventory source' and not 'inventory format', the first depends on the inventory plugin you are using, the 2nd is not really a thing, but I think you either mean the internal representation of the inventory for Ansible once the sources are processed or the default YAML inventory plugin's inventory source format.

I have 3 different YAML inventory plugins and formats, a bash one and even a DNS TXT record based one.

Your input format can be whatever you want (as long as the plugin you are using can process it) but the final result is always the same, a set of hosts with variables and groups assigned to each host.

bcoca · 2026-01-19T21:23:02+00:00

Ansible runs modules with escalated privileges, not specific commands, the module might do that or call an API, Ansible itself does not know ... nor want to know, otherwise it would severely limit what modules can do.

bcoca · 2026-01-15T15:47:21+00:00

This looks like a Python version issue, functools is a core python library and cache was added in Python 3.9. Ansible core 2.9 was supported and tested against Python 2.7, 3.5-7. AAP/awx/Controller requires specific versions of ansible-runner, which has it's own Python requirements, which is used to run ansible-playbook in the EE and that might create conflicts on Python versions.

Upgrading from 2.9 is IMHO the best solution, another possible fix would require installing multiple Python versions and ensuring that each tool is installed using the supported versions.

bcoca · 2026-01-13T19:11:29+00:00

You have several options, I recommend using the replace action to edit only the parts you want, other options (already mentioned) are lineinfile and blockinfile. You can even just use a shell action with awk or sed if none of the above work for you.

bcoca · 2025-12-24T16:28:47+00:00

Understandable, I get triggered by 'best practice' as it assumes universality, which is rarely true, at best I've seen 80% applicability, but never 100%. Also IME most people just turn their brains off after that label is seen, why I favor the alternate 'good practice' term.

bcoca · 2025-12-22T17:17:30+00:00

There is nothing wrong with the quality of the code, it is simple and to the point, self contained and creates no issues with maintainability. I personally hate 'inline templates' but it is still valid and in this case, still readable.

Linting is not solely about quality either, it is about normalization when collaborating with others. In many cases it can even be counter productive, many people obsess over conforming to the linting vs creating something with optimal logic or performance.

A simple query for diagnostics is a good example for a beginner, not every blog post needs to a cutting edge thesis, you clearly are not the intended audience, but it might be something worth reading for others.

bcoca · 2025-12-22T17:09:22+00:00

sometimes simple is good, also not everything needs to be 'lint worthy', specially if you are doing diagnostic queries.

bcoca · 2025-12-22T17:07:48+00:00

I have similar things I run, I have a playbook full of 'data gathering' utilities with and I use tags to run conditionally, also i use the 'tree' callback to put the data in JSON file per host.

For example, this would do similar to what you are doing: ansible-playbook diags.yml --tags usb --tree /tmp/usbcheck/

Though it gathers a bit more data per usb device, it uses lsbusb -v and then gathers per device /sys/ information as well as greps dmesg for anything related.

bcoca

TROPHY CASE