Add option for tower inventory to give general metadata

[AlanCoding]

SUMMARY

This adds an option which, if enabled, will return additional information about the remote tower server which the plugin is returning mirroring content from.

ISSUE TYPE

• Feature Pull Request

COMPONENT NAME

lib/ansible/plugins/inventory/tower.py

Ansible Tower inventory plugin

ADDITIONAL INFORMATION

We need to know license type to tell apart AWX vs. Ansible Tower, and I also thought that version and ansible_version would be of general utility.

Ping @matburt @wenottingham

Example of using this parameter:

ansible-inventory -i private/tower/tower.yml --list --export

{
    "_meta": {
        "hostvars": {
            "HostMachinePossiblenew": {
                "ansible_connection": "local", 
                "ansible_host": "127.0.0.1", 
                "remote_tower_enabled": "true", 
                "remote_tower_id": 588
            }
        }
    }, 
    "all": {
        "children": [
            "ungrouped"
        ], 
        "vars": {
            "tower_metadata": {
                "ansible_version": "2.7.5", 
                "license_type": "open", 
                "version": "2.0.1-1068-g09684e2c41"
            }
        }
    }, 
    "ungrouped": {
        "hosts": [
            "HostMachinePossiblenew"
        ]
    }
}

The id and enabled variables are already kind of "metadata", but are host specific.

I did wonder if it might be better to create a new group, and put the variables in there (that way, if you are using multiple inventory sources, they don't get messed up). Either way, it doesn't matter to me. This is my initial pass because it seems like the path of least clutter.

[AlanCoding]

Requesting review @ryanpetrello @rooftopcellist

[ryanpetrello]

shipit

[matburt]

shipit

[rooftopcellist]

shipit

[AlanCoding]

bot_status

[ansibot]

Components

lib/ansible/plugins/inventory/tower.py
support: community
maintainers:

Metadata

waiting_on: maintainer
changes_requested_by: null
needs_info: False
needs_revision: False
needs_rebase: False
merge_commits: []
too many files or commits: False
mergeable_state: clean
shippable_status: success
maintainer_shipits (module maintainers): 0
community_shipits (namespace maintainers): 0
ansible_shipits (core team members): 0
shipit_actors (maintainer or core team member): []
shipit_actors_other: ryanpetrello matburt rooftopcellist
automerge: automerge shipit test failed

click here for bot help

[AlanCoding]

automerge: automerge shipit test failed

What does that mean? Where can I find the output from this test?

[gundalow]

Looks like commit was after the last s h i p i t which resets the counter to zero

shipit

[kdelee]

shipit

[rooftopcellist]

shipit

[gundalow]

That did it thanks, merged into devel for release in Ansible 2.8.