search

dmsimard / ansible-tower-cicd

A framework for continuous integration and continuous delivery with Ansible Tower.
https://www.ansible.com/products/tower
GNU General Public License v3.0
36 stars 9 forks source link

feature request - push config from dev to prod Tower clusters #5

Open gforster opened 5 years ago

gforster commented 5 years ago

Maybe this isn't exactly withing scope, but I have dev and production Tower clusters. It would be cool to utilize this (or something like it) to be able to get the config from dev, commit it to git in a dev branch, do a PR to master, then push it to prod, keeping the production Tower cluster a "read-only" type of place.

dmsimard commented 5 years ago

What would this look like in practice ?

Two standalone Tower clusters, one hooked to the dev branch and one hooked to the master branch ?

I guess the framework already allows something like this: https://github.com/dmsimard/ansible-tower-cicd/blob/e0eed4d596ea56af323adbde45d746569fd74928/roles/tower-config/defaults/main.yaml#L63

https://github.com/dmsimard/ansible-tower-cicd/blob/e0eed4d596ea56af323adbde45d746569fd74928/roles/tower-config/tasks/main.yaml#L82

gforster commented 5 years ago

I guess I was thinking more along the lines of getting the config out of Tower, into a vars file/modifying the defaults/main.yml/something and then being able to utilize the existing framework. I suppose one could figure it out in the dev Tower gui and then manually add the config, but it would be nice to have the option to figure it out in the gui and then push existing changes into git. Or more simply, for those that may already have an existing instance, pulling in any existing config into the format to be used here.