feature request - push config from dev to prod Tower clusters

[gforster]

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]

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:

ansible-tower-cicd/roles/tower-config/defaults/main.yaml

Line 63 in e0eed4d

- name: ansible-tower-cicd

ansible-tower-cicd/roles/tower-config/tasks/main.yaml

Line 82 in e0eed4d

scm_branch: "{{ item.scm_branch | default(omit) }}"

[gforster]

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.