On Fri, 2022-07-22 at 19:45 +0200, Johannes Kastl wrote:
Hi Scott,
On 22.07.22 at 19:33 Scott Bradnick wrote:
Was using (sudo zypper rm ansible): ansible | package | 2.9.27-1.4 | noarch | Main Repository (OSS)
Switched to (sudo zypper in ansible-core): ansible-core | package | 2.13.2-1.1 | noarch | All things ansible
No issues on an initial run using ansible-playbook 👍️
If you are only using modules that are now being called "ansible.builtin.*", then ansible-core is enough. That is things like file, template, service and the likes.
But e.g. zypper_repository is now inside the community.* collections, and then ansible-core is failing...
Johannes
-- Johannes Kastl Linux Consultant & Trainer Tel.: +49 (0) 151 2372 5802 Mail: kastl@b1-systems.de
B1 Systems GmbH Osterfeldstraße 7 / 85088 Vohburg http://www.b1-systems.de GF: Ralph Dehner Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Yep, you've described my use-case quite spot-on: I'm basically using these in various places -- (`rg --trim --no-line-number --no-filename -g \*.yml "ansible\." | sort -u`) ansible.builtin.command ansible.builtin.debug ansible.builtin.file ansible.builtin.get_url ansible.builtin.git ansible.builtin.lineinfile ansible.builtin.package ansible.builtin.package_facts ansible.builtin.unarchive I am at a point though where I should look into something to manage zypper repos ~ at worst as a learning experience for how ansible will be packaged going forward 😉️ -- ~ Scott Bradnick |- Windows Subsystem for Linux (WSL) Developer |-- Tumbleweed: |--- Dell Precision 5540 [NVIDIA Quadro T1000] (x86_64) |--- O-DROID H2+ [UHD Graphics 600] (x86_64) |--- 2x Raspberry Pi 4 Model B Rev 1.2 (aarch64) |--- 1x Raspberry Pi 3 Model B Rev 1.2 (aarch64) |--- WinBook TW100 (x86_64) https://keys.openpgp.org/ :: DBC5AA9A2D2BAEBC