Replies: 2 comments 2 replies
-
|
Hi! We are currently transitioning to the Ansible Collection format, and this was requested by many users. We even received some feedback that directly using the source code tree is not considered a best practice in the Ansible ecosystem, and we’ve taken this into account. Up to version 2.2.0 (inclusive), you can still use your usual workflow and run the playbooks directly from the source code as before.
|
Beta Was this translation helpful? Give feedback.
-
|
@snoby Assuming you have installed the collection from Ansible Galaxy: - name: Autobase
hosts: etcd_cluster
become: true
gather_facts: true
any_errors_fatal: true
become_user: root
- name: Run Autobase config_pgcluster
ansible.builtin.import_playbook: vitabaks.autobase.config_pgclusterSee also the README section for this. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I've gone through the docs and reviewed the reasons and the work done to change to the new ansible deploy methodology. Great job, I'm sure that was a lot of work. My question is if I want to work out of the source code tree with ansible, I'm failing to see what is the proper way to run the playbooks. Pretend that i don't want to use ansible collections.
chatgpt is telling me to do some magic with paths and fake the playbooks like they are a collection. Or i could change all the roles that have - role: vitabaks.autobase.xxxx to just - role: xxx
Just wondering what your workflow is or how you think my workflow should be if i want to work on the playbooks or debug them.
thanks.
Beta Was this translation helpful? Give feedback.
All reactions