mirror of
https://github.com/ansible/awx.git
synced 2026-03-18 01:17:35 -02:30
replace certain terms with more inclusive language
see: https://www.redhat.com/en/blog/making-open-source-more-inclusive-eradicating-problematic-language
This commit is contained in:
@@ -11,7 +11,7 @@ This IP address can be found by making a GET to any page on the browsable API an
|
||||
awx_1 | 14:42:08 uwsgi.1 | 172.18.0.1 GET /api/v2/tokens/ - HTTP/1.1 200
|
||||
```
|
||||
|
||||
Whitelist this IP address by adding it to the `INTERNAL_IPS` variable in `local_settings`, then navigate to the API and you should see DDT on the
|
||||
Allow this IP address by adding it to the `INTERNAL_IPS` variable in `local_settings`, then navigate to the API and you should see DDT on the
|
||||
right side. If you don't see it, make sure to set `DEBUG=True`.
|
||||
> Note that enabling DDT is detrimental to the performance of AWX and adds overhead to every API request. It is
|
||||
recommended to keep this turned off when you are not using it.
|
||||
|
||||
@@ -32,7 +32,7 @@ The standard pattern applies to the following fields:
|
||||
- `ask_inventory_on_launch` allows use of `inventory`
|
||||
|
||||
Surveys are a special-case of prompting for variables - applying a survey to
|
||||
a template whitelists variable names in the survey spec (requires the survey
|
||||
a template allows variable names in the survey spec (requires the survey
|
||||
spec to exist and `survey_enabled` to be true). On the other hand,
|
||||
if `ask_variables_on_launch` is true, users can provide any variables in
|
||||
`extra_vars`.
|
||||
|
||||
@@ -132,7 +132,7 @@ user performing the copy, and `new_objs`, a list of all sub objects of the creat
|
||||
`user`'s permission against these new sub objects and unlink related objects or send
|
||||
warning logs as necessary. `deep_copy_permission_check_func` should not return anything.
|
||||
|
||||
Lastly, macro `REENCRYPTION_BLACKLIST_AT_COPY` is available as part of a model definition. It is a
|
||||
Lastly, macro `REENCRYPTION_BLOCKLIST_AT_COPY` is available as part of a model definition. It is a
|
||||
list of field names which will escape re-encryption during copy. For example, the `extra_data` field
|
||||
of workflow job template nodes.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user