Add support for Group inventory sources#9
Conversation
Initial pass at #9. Currently lacks tests.
|
+1 |
|
Can you provide an example of this being used for an addition/edit for a cloud provider to help with testing (and so that we may possibly show an example in the README?) Thanks! |
|
The idea in my case is to capture the data for Orgs, Teams, Creds, Projects, Inventories, Groups, and Job Templates in a YAML data structure driven by an Anisble playbook. This keeps the history of how it was configured, but also allows us the possibility to store the configuration of Job Templates and things like that in a given app's git repo. For now I will just put a pause task in the Groups step to ask folks to go manually configure the source and then come back to complete the playbook. Could definitely be that I am off my rocker with this use case :) But when I first saw this Tower CLI tool I thought it would be great for capturing the configuration of Tower in Ansible playbooks and data structures, and that the Tower GUI would be mostly for execution operations and not configuration of Tower itself. I have no idea if this use case is being considered by anyone else, but the next step for me would be to make some Ansible providers for configuring Ansible Tower, rather than using the command module to execute tower-cli. And in case it is not obvious, I will state that it is not a high-priority concern for me :) I just ran across this feature request and thought I would +1 it. |
|
My above comment was asking @jsmartin to add a copy/paste command line example |
|
Right now what I have in mind (and implemented on the branch) is something like: It gets a little bit tricky when you're modifying, though, because the What I have so far (in the |
|
@lukesneeringer got around to testing the issue-9-unstable branch. Works for me. Creating some additional RFE's now :). Thanks. |
Conflicts: lib/tower_cli/models/base.py lib/tower_cli/resources/group.py tests/test_resources_group.py
Add support for Group inventory sources
upgrade cli to support 3.0 prompt fields of JT
Would be great if we could set a group's source (EC2, RAX, etc).