Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run many Playbooks from different Repositories #15281

Open
5 of 11 tasks
ITS1988 opened this issue Jun 18, 2024 · 0 comments
Open
5 of 11 tasks

Run many Playbooks from different Repositories #15281

ITS1988 opened this issue Jun 18, 2024 · 0 comments

Comments

@ITS1988
Copy link

ITS1988 commented Jun 18, 2024

Please confirm the following

  • I agree to follow this project's code of conduct.
  • I have checked the current issues for duplicates.
  • I understand that AWX is open source software provided for free and that I might not receive a timely response.
  • I am NOT reporting a (potential) security vulnerability. (These should be emailed to security@ansible.com instead.)

Bug Summary

Hello everyone,

I have a question. We use Ansible AWX. We have an Ansible repository where we manage our playbooks that can be used by multiple projects and the project repositories where we keep the playbooks that contain project specific stuff.

We want to have this structure so that if something needs to be changed in the nodejs playbook, we don't have to make the change several times in several places, but only once in the playbook repository.

Is there any way other than using workflows that I can merge and run all playbooks that are needed for my project (e.g. Java17 from playbooks repo, Nodejs14 from playbooks repo and main playbook from project repo)?

Many thanks in advance!

AWX version

17.0.1

Select the relevant components

  • UI
  • UI (tech preview)
  • API
  • Docs
  • Collection
  • CLI
  • Other

Installation method

docker development environment

Modifications

no

Ansible version

2.9.17

Operating system

Rhel9

Web browser

No response

Steps to reproduce

see summary

Expected results

see summary

Actual results

see summary

Additional information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant