Project

General

Profile

Actions

Feature #25581

open

Make AWX configuration more streamlined

Added by Ondřej Pražák over 5 years ago. Updated about 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

Description

We added the ability to make a callback to AWX after provisioning a host.
Right now this is done by adding a bunch of host parameters manually.

We should look to make Ansible Tower/AWX instances (and other bits) first class citizens, which has the following advantages:
- Better Discoverability
- Better UX, better visualization
- Makes centralizing configs cleaner.

As an example. The user would be able to create "AWX" objects and associate them to Hosts, Host Groups, Orgs, etc. With the current integration this object would probably only contain a name and the tower URL. However, it might grow to include things like API keys, AWX Org, etc if we want to add features that need those things.

Additionally Hosts (and related items like Host groups) should probably have a regular fields for things like ansible_job_template_id and ansible_host_config_key, these could be contained in an "AWX" tab so the user only needs to specify the value (since the field name is well known).

These would probably still be host_params at the end of the day, but we can make them more prominent in the UI/CLI/etc and create the params behind the scenes.

Actions #1

Updated by Ondřej Ezr about 3 years ago

  • Subject changed from Make AWX configuration more streamlined to Make AWX configuration more streamlined
  • Triaged changed from No to Yes
Actions

Also available in: Atom PDF