mirror of
https://github.com/ansible/awx.git
synced 2026-02-19 20:20:06 -03:30
Assorted renaming and string changes
This commit is contained in:
@@ -1,5 +1,5 @@
|
||||
# Inventory Refresh Overview
|
||||
Tower should have an inventory view that is more aligned towards systems management
|
||||
AWX should have an inventory view that is more aligned towards systems management
|
||||
rather than merely maintaining inventory for automation.
|
||||
|
||||
## Inventory Source Promotion
|
||||
@@ -7,7 +7,7 @@ Starting with Tower 3.2, `InventorySource` will be associated directly with an `
|
||||
|
||||
|
||||
## Fact Searching
|
||||
Facts generated by an Ansible playbook during a Job Template run are stored by Tower into the database
|
||||
Facts generated by an Ansible playbook during a Job Template run are stored by AWX into the database
|
||||
whenever `use_fact_cache=True` is set per-Job-Template. New facts are merged with existing
|
||||
facts and are per-host. These stored facts can be used to filter hosts via the
|
||||
`/api/v2/hosts` endpoint, using the GET query parameter `host_filter` *i.e.*,
|
||||
@@ -77,7 +77,7 @@ Creating a new _Smart Inventory_ for all of our GCE and EC2 groups might look li
|
||||
|
||||
### More On Searching
|
||||
The `host_filter` that is set will search over the entirety of the hosts the user has
|
||||
access to in Tower. If the user wants to restrict their search in anyway, they will
|
||||
access to in AWX. If the user wants to restrict their search in anyway, they will
|
||||
want to declare that in their host filter.
|
||||
|
||||
For example, if wanting to restrict the search to only hosts in an inventory
|
||||
|
||||
Reference in New Issue
Block a user