mirror of
https://github.com/ansible/awx.git
synced 2026-01-17 20:51:21 -03:30
Removes references to Ansible Tower in favor of Ansible Controller (#12422)
This commit is contained in:
Alex Corey
GitHub
parent
26912a06d1
commit
c586f8bbc6
391
awx/ui/SEARCH.md
391
awx/ui/SEARCH.md
@ -2,26 +2,27 @@
|
||||
|
||||
## UX Considerations
|
||||
|
||||
Historically, the code that powers search in the AngularJS version of the AWX UI is very complex and prone to bugs. In order to reduce that complexity, we've made some UX decisions to help make the code easier to maintain.
|
||||
Historically, the code that powers search in the AngularJS version of the AWX UI is very complex and prone to bugs. In order to reduce that complexity, we've made some UX decisions to help make the code easier to maintain.
|
||||
|
||||
**ALL query params namespaced and in url bar**
|
||||
|
||||
This includes lists that aren't necessarily hyperlinked, like lookup lists. The reason behind this is so we can treat the url bar as the source of truth for queries always. Any params that have both a key AND value that is in the defaultParams section of the qs config are stripped out of the search string (see "Encoding for UI vs. API" for more info on this point)
|
||||
This includes lists that aren't necessarily hyperlinked, like lookup lists. The reason behind this is so we can treat the url bar as the source of truth for queries always. Any params that have both a key AND value that is in the defaultParams section of the qs config are stripped out of the search string (see "Encoding for UI vs. API" for more info on this point)
|
||||
|
||||
**Django fuzzy search (`?search=`) is not accessible outside of "advanced search"**
|
||||
|
||||
In current smart search typing a term with no key utilizes `?search=` i.e. for "foo" tag, `?search=foo` is given. `?search=` looks on a static list of field name "guesses" (such as name, description, etc.), as well as specific fields as defined for each endpoint (for example, the events endpoint looks for a "stdout" field as well). Due to the fact a key will always be present on the left-hand of simple search, it doesn't make sense to use `?search=` as the default.
|
||||
In current smart search typing a term with no key utilizes `?search=` i.e. for "foo" tag, `?search=foo` is given. `?search=` looks on a static list of field name "guesses" (such as name, description, etc.), as well as specific fields as defined for each endpoint (for example, the events endpoint looks for a "stdout" field as well). Due to the fact a key will always be present on the left-hand of simple search, it doesn't make sense to use `?search=` as the default.
|
||||
|
||||
We may allow passing of `?search=` through our future advanced search interface. Some details that were gathered in planning phases about `?search=` that might be helpful in the future:
|
||||
|
||||
We may allow passing of `?search=` through our future advanced search interface. Some details that were gathered in planning phases about `?search=` that might be helpful in the future:
|
||||
- `?search=` tags are OR'd together (union is returned).
|
||||
- `?search=foo&name=bar` returns items that have a name field of bar (not case insensitive) AND some text field with foo on it
|
||||
- `?search=foo&search=bar&name=baz` returns (foo in name OR foo in description OR ...) AND (bar in name OR bar in description OR ...) AND (baz in name)
|
||||
- similarly `?related__search=` looks on the static list of "guesses" for models related to the endpoint. The specific fields are not "searched" for `?related__search=`.
|
||||
- similarly `?related__search=` looks on the static list of "guesses" for models related to the endpoint. The specific fields are not "searched" for `?related__search=`.
|
||||
- `?related__search=` not currently used in awx ui
|
||||
|
||||
**A note on clicking a tag to putting it back into the search bar**
|
||||
|
||||
This was brought up as a nice to have when we were discussing our initial implementation of search in the new application. Since there isn't a way we would be able to know if the user created the tag from the simple or advanced search interface, we wouldn't know where to put it back. This breaks our idea of using the query params as the exclusive source of truth, so we've decided against implementing it for now.
|
||||
This was brought up as a nice to have when we were discussing our initial implementation of search in the new application. Since there isn't a way we would be able to know if the user created the tag from the simple or advanced search interface, we wouldn't know where to put it back. This breaks our idea of using the query params as the exclusive source of truth, so we've decided against implementing it for now.
|
||||
|
||||
## Tasklist
|
||||
|
||||
@ -50,171 +51,197 @@ This was brought up as a nice to have when we were discussing our initial implem
|
||||
- DONE remove button for search tags of duplicate keys are broken, fix that
|
||||
|
||||
### TODO pre-holiday break
|
||||
|
||||
- Update COLUMNS to SORT_COLUMNS and SEARCH_COLUMNS
|
||||
- Update to using new PF Toolbar component (currently an experimental component)
|
||||
- Change the right-hand input based on the type of key selected on the left-hand side. In addition to text input, for our MVP we will support:
|
||||
- Change the right-hand input based on the type of key selected on the left-hand side. In addition to text input, for our MVP we will support:
|
||||
- number input
|
||||
- select input (multiple-choice configured from UI or Options)
|
||||
- Update the following lists to have the following keys:
|
||||
|
||||
**Jobs list** (signed off earlier in chat)
|
||||
- Name (which is also the name of the job template) - search is ?name=jt
|
||||
- Job ID - search is ?id=13
|
||||
- Label name - search is ?labels__name=foo
|
||||
- Job type (dropdown on right with the different types) ?type = job
|
||||
- Created by (username) - search is ?created_by__username=admin
|
||||
- Status - search (dropdown on right with different statuses) is ?status=successful
|
||||
|
||||
- Name (which is also the name of the job template) - search is ?name=jt
|
||||
- Job ID - search is ?id=13
|
||||
- Label name - search is ?labels\_\_name=foo
|
||||
- Job type (dropdown on right with the different types) ?type = job
|
||||
- Created by (username) - search is ?created_by\_\_username=admin
|
||||
- Status - search (dropdown on right with different statuses) is ?status=successful
|
||||
|
||||
Instances of jobs list include:
|
||||
- Jobs list
|
||||
- Host completed jobs list
|
||||
- JT completed jobs list
|
||||
|
||||
- Jobs list
|
||||
- Host completed jobs list
|
||||
- JT completed jobs list
|
||||
|
||||
**Organization list**
|
||||
- Name - search is ?name=org
|
||||
- ? Team name (of a team in the org) - search is ?teams__name=ansible
|
||||
- ? Username (of a user in the org) - search is ?users__username=johndoe
|
||||
|
||||
- Name - search is ?name=org
|
||||
- ? Team name (of a team in the org) - search is ?teams\_\_name=ansible
|
||||
- ? Username (of a user in the org) - search is ?users\_\_username=johndoe
|
||||
|
||||
Instances of orgs list include:
|
||||
- Orgs list
|
||||
- User orgs list
|
||||
- Lookup on Project
|
||||
- Lookup on Credential
|
||||
- Lookup on Inventory
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
- Orgs list
|
||||
- User orgs list
|
||||
- Lookup on Project
|
||||
- Lookup on Credential
|
||||
- Lookup on Inventory
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
**Instance Groups list**
|
||||
- Name - search is ?name=ig
|
||||
- ? is_container_group boolean choice (doesn't work right now in API but will soon) - search is ?is_container_group=true
|
||||
- ? credential name - search is ?credentials__name=kubey
|
||||
|
||||
- Name - search is ?name=ig
|
||||
- ? is_container_group boolean choice (doesn't work right now in API but will soon) - search is ?is_container_group=true
|
||||
- ? credential name - search is ?credentials\_\_name=kubey
|
||||
|
||||
Instance of instance groups list include:
|
||||
- Lookup on Org
|
||||
- Lookup on JT
|
||||
- Lookup on Inventory
|
||||
|
||||
- Lookup on Org
|
||||
- Lookup on JT
|
||||
- Lookup on Inventory
|
||||
|
||||
**Users list**
|
||||
- Username - search is ?username=johndoe
|
||||
- First Name - search is ?first_name=John
|
||||
- Last Name - search is ?last_name=Doe
|
||||
- ? (if not superfluous, would not include on Team users list) Team Name - search is ?teams__name=team_of_john_does (note API issue: User has no field named "teams")
|
||||
- ? (only for access or permissions list) Role Name - search is ?roles__name=Admin (note API issue: Role has no field "name")
|
||||
- ? (if not superfluous, would not include on Organization users list) ORg Name - search is ?organizations__name=org_of_jhn_does
|
||||
|
||||
- Username - search is ?username=johndoe
|
||||
- First Name - search is ?first_name=John
|
||||
- Last Name - search is ?last_name=Doe
|
||||
- ? (if not superfluous, would not include on Team users list) Team Name - search is ?teams\_\_name=team_of_john_does (note API issue: User has no field named "teams")
|
||||
- ? (only for access or permissions list) Role Name - search is ?roles\_\_name=Admin (note API issue: Role has no field "name")
|
||||
- ? (if not superfluous, would not include on Organization users list) ORg Name - search is ?organizations\_\_name=org_of_jhn_does
|
||||
|
||||
Instance of user lists include:
|
||||
- User list
|
||||
- Org user list
|
||||
- Access list for Org, JT, Project, Credential, Inventory, User and Team
|
||||
- Access list for JT
|
||||
- Access list Project
|
||||
- Access list for Credential
|
||||
- Access list for Inventory
|
||||
- Access list for User
|
||||
- Access list for Team
|
||||
- Team add users list
|
||||
- Users list in access wizard (to add new roles for a particular list) for Org
|
||||
- Users list in access wizard (to add new roles for a particular list) for JT
|
||||
- Users list in access wizard (to add new roles for a particular list) for Project
|
||||
- Users list in access wizard (to add new roles for a particular list) for Credential
|
||||
- Users list in access wizard (to add new roles for a particular list) for Inventory
|
||||
|
||||
- User list
|
||||
- Org user list
|
||||
- Access list for Org, JT, Project, Credential, Inventory, User and Team
|
||||
- Access list for JT
|
||||
- Access list Project
|
||||
- Access list for Credential
|
||||
- Access list for Inventory
|
||||
- Access list for User
|
||||
- Access list for Team
|
||||
- Team add users list
|
||||
- Users list in access wizard (to add new roles for a particular list) for Org
|
||||
- Users list in access wizard (to add new roles for a particular list) for JT
|
||||
- Users list in access wizard (to add new roles for a particular list) for Project
|
||||
- Users list in access wizard (to add new roles for a particular list) for Credential
|
||||
- Users list in access wizard (to add new roles for a particular list) for Inventory
|
||||
|
||||
**Teams list**
|
||||
- Name - search is ?name=teamname
|
||||
- ? Username (of a user in the team) - search is ?users__username=johndoe
|
||||
- ? (if not superfluous, would not include on Organizations teams list) Org Name - search is ?organizations__name=org_of_john_does
|
||||
|
||||
- Name - search is ?name=teamname
|
||||
- ? Username (of a user in the team) - search is ?users\_\_username=johndoe
|
||||
- ? (if not superfluous, would not include on Organizations teams list) Org Name - search is ?organizations\_\_name=org_of_john_does
|
||||
|
||||
Instance of team lists include:
|
||||
- Team list
|
||||
- Org team list
|
||||
- User team list
|
||||
- Team list in access wizard (to add new roles for a particular list) for Org
|
||||
- Team list in access wizard (to add new roles for a particular list) for JT
|
||||
- Team list in access wizard (to add new roles for a particular list) for Project
|
||||
- Team list in access wizard (to add new roles for a particular list) for Credential
|
||||
- Team list in access wizard (to add new roles for a particular list) for Inventory
|
||||
|
||||
- Team list
|
||||
- Org team list
|
||||
- User team list
|
||||
- Team list in access wizard (to add new roles for a particular list) for Org
|
||||
- Team list in access wizard (to add new roles for a particular list) for JT
|
||||
- Team list in access wizard (to add new roles for a particular list) for Project
|
||||
- Team list in access wizard (to add new roles for a particular list) for Credential
|
||||
- Team list in access wizard (to add new roles for a particular list) for Inventory
|
||||
|
||||
**Credentials list**
|
||||
- Name
|
||||
- ? Type (dropdown on right with different types)
|
||||
- ? Created by (username)
|
||||
- ? Modified by (username)
|
||||
|
||||
- Name
|
||||
- ? Type (dropdown on right with different types)
|
||||
- ? Created by (username)
|
||||
- ? Modified by (username)
|
||||
|
||||
Instance of credential lists include:
|
||||
- Credential list
|
||||
- Lookup for JT
|
||||
- Lookup for Project
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
- Credential list
|
||||
- Lookup for JT
|
||||
- Lookup for Project
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
**Projects list**
|
||||
- Name - search is ?name=proj
|
||||
- ? Type (dropdown on right with different types) - search is scm_type=git
|
||||
- ? SCM URL - search is ?scm_url=github.com/ansible/test-playbooks
|
||||
- ? Created by (username) - search is ?created_by__username=admin
|
||||
- ? Modified by (username) - search is ?modified_by__username=admin
|
||||
|
||||
- Name - search is ?name=proj
|
||||
- ? Type (dropdown on right with different types) - search is scm_type=git
|
||||
- ? SCM URL - search is ?scm_url=github.com/ansible/test-playbooks
|
||||
- ? Created by (username) - search is ?created_by\_\_username=admin
|
||||
- ? Modified by (username) - search is ?modified_by\_\_username=admin
|
||||
|
||||
Instance of project lists include:
|
||||
- Project list
|
||||
- Lookup for JT
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
- Project list
|
||||
- Lookup for JT
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
**Templates list**
|
||||
- Name - search is ?name=cleanup
|
||||
- ? Type (dropdown on right with different types) - search is ?type=playbook_run
|
||||
- ? Playbook name - search is ?job_template__playbook=debug.yml
|
||||
- ? Created by (username) - search is ?created_by__username=admin
|
||||
- ? Modified by (username) - search is ?modified_by__username=admin
|
||||
|
||||
- Name - search is ?name=cleanup
|
||||
- ? Type (dropdown on right with different types) - search is ?type=playbook_run
|
||||
- ? Playbook name - search is ?job_template\_\_playbook=debug.yml
|
||||
- ? Created by (username) - search is ?created_by\_\_username=admin
|
||||
- ? Modified by (username) - search is ?modified_by\_\_username=admin
|
||||
|
||||
Instance of template lists include:
|
||||
- Template list
|
||||
- Project Templates list
|
||||
|
||||
- Template list
|
||||
- Project Templates list
|
||||
|
||||
**Inventories list**
|
||||
- Name - search is ?name=inv
|
||||
- ? Created by (username) - search is ?created_by__username=admin
|
||||
- ? Modified by (username) - search is ?modified_by__username=admin
|
||||
|
||||
- Name - search is ?name=inv
|
||||
- ? Created by (username) - search is ?created_by\_\_username=admin
|
||||
- ? Modified by (username) - search is ?modified_by\_\_username=admin
|
||||
|
||||
Instance of inventory lists include:
|
||||
- Inventory list
|
||||
- Lookup for JT
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
- Inventory list
|
||||
- Lookup for JT
|
||||
- User access add wizard list
|
||||
- Team access add wizard list
|
||||
|
||||
**Groups list**
|
||||
- Name - search is ?name=group_name
|
||||
- ? Created by (username) - search is ?created_by__username=admin
|
||||
- ? Modified by (username) - search is ?modified_by__username=admin
|
||||
|
||||
- Name - search is ?name=group_name
|
||||
- ? Created by (username) - search is ?created_by\_\_username=admin
|
||||
- ? Modified by (username) - search is ?modified_by\_\_username=admin
|
||||
|
||||
Instance of group lists include:
|
||||
- Group list
|
||||
|
||||
- Group list
|
||||
|
||||
**Hosts list**
|
||||
- Name - search is ?name=hostname
|
||||
- ? Created by (username) - search is ?created_by__username=admin
|
||||
- ? Modified by (username) - search is ?modified_by__username=admin
|
||||
|
||||
- Name - search is ?name=hostname
|
||||
- ? Created by (username) - search is ?created_by\_\_username=admin
|
||||
- ? Modified by (username) - search is ?modified_by\_\_username=admin
|
||||
|
||||
Instance of host lists include:
|
||||
- Host list
|
||||
|
||||
- Host list
|
||||
|
||||
**Notifications list**
|
||||
- Name - search is ?name=notification_template_name
|
||||
- ? Type (dropdown on right with different types) - search is ?type=slack
|
||||
- ? Created by (username) - search is ?created_by__username=admin
|
||||
- ? Modified by (username) - search is ?modified_by__username=admin
|
||||
|
||||
- Name - search is ?name=notification_template_name
|
||||
- ? Type (dropdown on right with different types) - search is ?type=slack
|
||||
- ? Created by (username) - search is ?created_by\_\_username=admin
|
||||
- ? Modified by (username) - search is ?modified_by\_\_username=admin
|
||||
|
||||
Instance of notification lists include:
|
||||
- Org notification list
|
||||
- JT notification list
|
||||
- Project notification list
|
||||
|
||||
- Org notification list
|
||||
- JT notification list
|
||||
- Project notification list
|
||||
|
||||
### TODO backlog
|
||||
- Change the right-hand input based on the type of key selected on the left-hand side. We will eventually want to support:
|
||||
|
||||
- Change the right-hand input based on the type of key selected on the left-hand side. We will eventually want to support:
|
||||
- lookup input (selection of particular resources, based on API list endpoints)
|
||||
- date picker input
|
||||
- Update the following lists to have the following keys:
|
||||
- Update all __name and __username related field search-based keys to be type-ahead lookup based searches
|
||||
- Update all **name and **username related field search-based keys to be type-ahead lookup based searches
|
||||
|
||||
## Code Details
|
||||
|
||||
@ -230,13 +257,13 @@ The component looks like this:
|
||||
/>
|
||||
```
|
||||
|
||||
**qsConfig** is used to get namespace so that multiple lists can be on the page. When tags are modified they append namespace to query params. The qsConfig is also used to get "type" of fields in order to correctly parse values as int or date as it is translating.
|
||||
**qsConfig** is used to get namespace so that multiple lists can be on the page. When tags are modified they append namespace to query params. The qsConfig is also used to get "type" of fields in order to correctly parse values as int or date as it is translating.
|
||||
|
||||
**columns** are passed as an array, as defined in the screen where the list is located. You pass a bool `isDefault` to indicate that should be the key that shows up in the left-hand dropdown as default in the UI. If you don't pass any columns, a default of `isDefault=true` will be added to a name column, which is nearly universally shared throughout the models of awx.
|
||||
**columns** are passed as an array, as defined in the screen where the list is located. You pass a bool `isDefault` to indicate that should be the key that shows up in the left-hand dropdown as default in the UI. If you don't pass any columns, a default of `isDefault=true` will be added to a name column, which is nearly universally shared throughout the models of awx.
|
||||
|
||||
There is a type attribute that can be `'string'`, `'number'` or `'choice'` (and in the future, `'date'` and `'lookup'`), which will change the type of input on the right-hand side of the search bar. For a key that has a set number of choices, you will pass a choices attribute, which is an array in the format choices: [{label: 'Foo', value: 'foo'}]
|
||||
There is a type attribute that can be `'string'`, `'number'` or `'choice'` (and in the future, `'date'` and `'lookup'`), which will change the type of input on the right-hand side of the search bar. For a key that has a set number of choices, you will pass a choices attribute, which is an array in the format choices: [{label: 'Foo', value: 'foo'}]
|
||||
|
||||
**onSearch** calls the `mergeParams` qs util in order to add new tags to the queryset. mergeParams is used so that we can support duplicate keys (see mergeParams vs. replaceParams for more info).
|
||||
**onSearch** calls the `mergeParams` qs util in order to add new tags to the queryset. mergeParams is used so that we can support duplicate keys (see mergeParams vs. replaceParams for more info).
|
||||
|
||||
### ListHeader component
|
||||
|
||||
@ -253,15 +280,16 @@ All of these functions act on the react-router history using the `pushHistorySta
|
||||
|
||||
**a note on sort_columns and search_columns**
|
||||
|
||||
We have split out column configuration into separate search and sort column array props--these are passed to the search and sort columns. Both accept an isDefault prop for one of the items in the array to be the default option selected when going to the page. Sort column items can pass an isNumeric boolean in order to chnage the iconography of the sort UI element. Search column items can pass type and if applicable choices, in order to configure the right-hand side of the search bar.
|
||||
We have split out column configuration into separate search and sort column array props--these are passed to the search and sort columns. Both accept an isDefault prop for one of the items in the array to be the default option selected when going to the page. Sort column items can pass an isNumeric boolean in order to chnage the iconography of the sort UI element. Search column items can pass type and if applicable choices, in order to configure the right-hand side of the search bar.
|
||||
|
||||
### FilterTags component
|
||||
|
||||
Similar to the way the list grabs data based on changes to the react-router params, the `FilterTags` component updates when new params are added. This component is a fairly straight-forward map (only slightly complex, because it needed to do a nested map over any values with duplicate keys that were represented by an inner-array). Both key and value are displayed for the tag.
|
||||
Similar to the way the list grabs data based on changes to the react-router params, the `FilterTags` component updates when new params are added. This component is a fairly straight-forward map (only slightly complex, because it needed to do a nested map over any values with duplicate keys that were represented by an inner-array). Both key and value are displayed for the tag.
|
||||
|
||||
### qs utility
|
||||
|
||||
The qs (queryset) utility is used to make the search speak the language of the REST API. The main functions of the utilities are to:
|
||||
The qs (queryset) utility is used to make the search speak the language of the REST API. The main functions of the utilities are to:
|
||||
|
||||
- add, replace and remove filters
|
||||
- translate filters as url params (for linking and maintaining state), in-memory representation (as JS objects), and params that Django REST Framework understands.
|
||||
|
||||
@ -269,7 +297,7 @@ More info in the below sections:
|
||||
|
||||
#### Encoding for UI vs. API
|
||||
|
||||
For the UI url params, we want to only encode those params that aren't defaults, as the default behavior was defined through configuration and we don't need these in the url as a source of truth. For the API, we need to pass these params so that they are taken into account when the response is built.
|
||||
For the UI url params, we want to only encode those params that aren't defaults, as the default behavior was defined through configuration and we don't need these in the url as a source of truth. For the API, we need to pass these params so that they are taken into account when the response is built.
|
||||
|
||||
#### mergeParams vs. replaceParams
|
||||
|
||||
@ -283,13 +311,13 @@ From a UX perspective, we wanted to be able to support searching on the same key
|
||||
}
|
||||
```
|
||||
|
||||
Concatenating terms in this way gives you the intersection of both terms (i.e. foo must be "bar" and "baz"). This is helpful for the most-common type of searching, substring (`__icontains`) searches. This will increase filtering, allowing the user to drill-down into the list as terms are added.
|
||||
Concatenating terms in this way gives you the intersection of both terms (i.e. foo must be "bar" and "baz"). This is helpful for the most-common type of searching, substring (`__icontains`) searches. This will increase filtering, allowing the user to drill-down into the list as terms are added.
|
||||
|
||||
**replaceParams** is used to support sorting, setting page_size, etc. These params only allow one choice, and we need to replace a particular key's value if one is passed.
|
||||
**replaceParams** is used to support sorting, setting page_size, etc. These params only allow one choice, and we need to replace a particular key's value if one is passed.
|
||||
|
||||
#### Working with REST API
|
||||
|
||||
The REST API is coupled with the qs util through the `paramsSerializer`, due to the fact we need axios to support the array for duplicate key values in the object representation of the params to pass to the get request. This is done where axios is configured in the Base.js file, so all requests and request types should support our array syntax for duplicate keys automatically.
|
||||
The REST API is coupled with the qs util through the `paramsSerializer`, due to the fact we need axios to support the array for duplicate key values in the object representation of the params to pass to the get request. This is done where axios is configured in the Base.js file, so all requests and request types should support our array syntax for duplicate keys automatically.
|
||||
|
||||
# Advanced Search - this section is a mess, update eventually
|
||||
|
||||
@ -305,85 +333,84 @@ Current thinking is Advanced Search will be post-3.6, or at least late 3.6 after
|
||||
|
||||
That being said, we want to plan it out so we make sure the infrastructure of how we set up adding/removing tags, what shows up in the url bar, etc. all doesn't have to be redone.
|
||||
|
||||
Users will get to advanced search with a button to the right of search bar. When selected type-ahead key thing opens, left dropdown of search bar goes away, and x is given to get back to regular search (this is in the mockups)
|
||||
Users will get to advanced search with a button to the right of search bar. When selected type-ahead key thing opens, left dropdown of search bar goes away, and x is given to get back to regular search (this is in the mockups)
|
||||
|
||||
It is okay to only make this typing representation available initially (i.e. they start doing stuff with the type-ahead and the phases, no more typing in to make a query that way).
|
||||
|
||||
when you click through or type in the search bar for the various phases of crafting the query ("not", "related resource project", "related resource key name", "value foo") which might be represented in the top bar as a series of tags that can be added and removed before submitting the tag.
|
||||
|
||||
We will try to form options data from a static file. Because options data is static, we may be able to generate and store as a static file of some sort (that we can use for managing smart search). Alan had ideas around this. If we do this it will mean we don't have to make a ton of requests as we craft smart search filters. It sounds like the cli may start using something similar.
|
||||
We will try to form options data from a static file. Because options data is static, we may be able to generate and store as a static file of some sort (that we can use for managing smart search). Alan had ideas around this. If we do this it will mean we don't have to make a ton of requests as we craft smart search filters. It sounds like the cli may start using something similar.
|
||||
|
||||
## Smart search flow
|
||||
|
||||
Smart search will be able to craft the tag through various states. Note that the phases don't necessarily need to be completed in sequential order.
|
||||
Smart search will be able to craft the tag through various states. Note that the phases don't necessarily need to be completed in sequential order.
|
||||
|
||||
PHASE 1: prefix operators
|
||||
PHASE 1: prefix operators
|
||||
|
||||
**TODO: Double check there's no reason we need to include or__ and chain__ and can just do not__**
|
||||
**TODO: Double check there's no reason we need to include or** and chain** and can just do not\_\_**
|
||||
|
||||
- not__
|
||||
- or__
|
||||
- chain__
|
||||
- not\_\_
|
||||
- or\_\_
|
||||
- chain\_\_
|
||||
|
||||
how these work:
|
||||
how these work:
|
||||
|
||||
To exclude results matching certain criteria, prefix the field parameter with not__:
|
||||
To exclude results matching certain criteria, prefix the field parameter with not\_\_:
|
||||
|
||||
?not__field=value
|
||||
By default, all query string filters are AND'ed together, so only the results matching all filters will be returned. To combine results matching any one of multiple criteria, prefix each query string parameter with or__:
|
||||
?not**field=value
|
||||
By default, all query string filters are AND'ed together, so only the results matching all filters will be returned. To combine results matching any one of multiple criteria, prefix each query string parameter with or**:
|
||||
|
||||
?or__field=value&or__field=othervalue
|
||||
?or__not__field=value&or__field=othervalue
|
||||
(Added in Ansible Tower 1.4.5) The default AND filtering applies all filters simultaneously to each related object being filtered across database relationships. The chain filter instead applies filters separately for each related object. To use, prefix the query string parameter with chain__:
|
||||
?or**field=value&or**field=othervalue
|
||||
?or**not**field=value&or**field=othervalue
|
||||
(Added in Ansible Controller 1.4.5) The default AND filtering applies all filters simultaneously to each related object being filtered across database relationships. The chain filter instead applies filters separately for each related object. To use, prefix the query string parameter with chain**:
|
||||
|
||||
?chain__related__field=value&chain__related__field2=othervalue
|
||||
?chain__not__related__field=value&chain__related__field2=othervalue
|
||||
If the first query above were written as ?related__field=value&related__field2=othervalue, it would return only the primary objects where the same related object satisfied both conditions. As written using the chain filter, it would return the intersection of primary objects matching each condition.
|
||||
?chain**related**field=value&chain**related**field2=othervalue
|
||||
?chain**not**related**field=value&chain**related**field2=othervalue
|
||||
If the first query above were written as ?related**field=value&related\_\_field2=othervalue, it would return only the primary objects where the same related object satisfied both conditions. As written using the chain filter, it would return the intersection of primary objects matching each condition.
|
||||
|
||||
PHASE 2: related fields, given by array, where __search is appended to them, i.e.
|
||||
PHASE 2: related fields, given by array, where \_\_search is appended to them, i.e.
|
||||
|
||||
```
|
||||
"related_search_fields": [
|
||||
"credentials__search",
|
||||
"labels__search",
|
||||
"created_by__search",
|
||||
"modified_by__search",
|
||||
"notification_templates__search",
|
||||
"custom_inventory_scripts__search",
|
||||
"notification_templates_error__search",
|
||||
"notification_templates_success__search",
|
||||
"notification_templates_any__search",
|
||||
"teams__search",
|
||||
"projects__search",
|
||||
"inventories__search",
|
||||
"applications__search",
|
||||
"workflows__search",
|
||||
"instance_groups__search"
|
||||
],
|
||||
```
|
||||
```
|
||||
"related_search_fields": [
|
||||
"credentials__search",
|
||||
"labels__search",
|
||||
"created_by__search",
|
||||
"modified_by__search",
|
||||
"notification_templates__search",
|
||||
"custom_inventory_scripts__search",
|
||||
"notification_templates_error__search",
|
||||
"notification_templates_success__search",
|
||||
"notification_templates_any__search",
|
||||
"teams__search",
|
||||
"projects__search",
|
||||
"inventories__search",
|
||||
"applications__search",
|
||||
"workflows__search",
|
||||
"instance_groups__search"
|
||||
],
|
||||
```
|
||||
|
||||
PHASE 3: keys, give by object key names for data.actions.GET
|
||||
- type is given for each key which we could use to help craft the value
|
||||
PHASE 3: keys, give by object key names for data.actions.GET - type is given for each key which we could use to help craft the value
|
||||
|
||||
PHASE 4: after key postfix operators can be
|
||||
PHASE 4: after key postfix operators can be
|
||||
|
||||
**TODO: will need to figure out which ones we support**
|
||||
|
||||
- exact: Exact match (default lookup if not specified).
|
||||
- iexact: Case-insensitive version of exact.
|
||||
- contains: Field contains value.
|
||||
- icontains: Case-insensitive version of contains.
|
||||
- startswith: Field starts with value.
|
||||
- istartswith: Case-insensitive version of startswith.
|
||||
- endswith: Field ends with value.
|
||||
- iendswith: Case-insensitive version of endswith.
|
||||
- regex: Field matches the given regular expression.
|
||||
- iregex: Case-insensitive version of regex.
|
||||
- gt: Greater than comparison.
|
||||
- gte: Greater than or equal to comparison.
|
||||
- lt: Less than comparison.
|
||||
- lte: Less than or equal to comparison.
|
||||
- isnull: Check whether the given field or related object is null; expects a boolean value.
|
||||
- in: Check whether the given field's value is present in the list provided; expects a list of items.
|
||||
- exact: Exact match (default lookup if not specified).
|
||||
- iexact: Case-insensitive version of exact.
|
||||
- contains: Field contains value.
|
||||
- icontains: Case-insensitive version of contains.
|
||||
- startswith: Field starts with value.
|
||||
- istartswith: Case-insensitive version of startswith.
|
||||
- endswith: Field ends with value.
|
||||
- iendswith: Case-insensitive version of endswith.
|
||||
- regex: Field matches the given regular expression.
|
||||
- iregex: Case-insensitive version of regex.
|
||||
- gt: Greater than comparison.
|
||||
- gte: Greater than or equal to comparison.
|
||||
- lt: Less than comparison.
|
||||
- lte: Less than or equal to comparison.
|
||||
- isnull: Check whether the given field or related object is null; expects a boolean value.
|
||||
- in: Check whether the given field's value is present in the list provided; expects a list of items.
|
||||
|
||||
PHASE 5: The value. Based on options, we can give hints or validation based on type of value (like number fields don't accept "foo" or whatever)
|
||||
PHASE 5: The value. Based on options, we can give hints or validation based on type of value (like number fields don't accept "foo" or whatever)
|
||||
|
||||
@ -58,7 +58,7 @@ function OtherPromptsStep({ launchConfig, variablesMode, onVarModeChange }) {
|
||||
aria-label={t`Job Tags`}
|
||||
tooltip={t`Tags are useful when you have a large
|
||||
playbook, and you want to run a specific part of a play or task.
|
||||
Use commas to separate multiple tags. Refer to Ansible Tower
|
||||
Use commas to separate multiple tags. Refer to Ansible Controller
|
||||
documentation for details on the usage of tags.`}
|
||||
/>
|
||||
)}
|
||||
@ -70,7 +70,7 @@ function OtherPromptsStep({ launchConfig, variablesMode, onVarModeChange }) {
|
||||
aria-label={t`Skip Tags`}
|
||||
tooltip={t`Skip tags are useful when you have a large
|
||||
playbook, and you want to skip specific parts of a play or task.
|
||||
Use commas to separate multiple tags. Refer to Ansible Tower
|
||||
Use commas to separate multiple tags. Refer to Ansible Controller
|
||||
documentation for details on the usage of tags.`}
|
||||
/>
|
||||
)}
|
||||
|
||||
@ -349,7 +349,7 @@ function HostFilterLookup({
|
||||
content={t`Populate the hosts for this inventory by using a search
|
||||
filter. Example: ansible_facts__ansible_distribution:"RedHat".
|
||||
Refer to the documentation for further syntax and
|
||||
examples. Refer to the Ansible Tower documentation for further syntax and
|
||||
examples. Refer to the Ansible Controller documentation for further syntax and
|
||||
examples.`}
|
||||
/>
|
||||
}
|
||||
|
||||
@ -421,12 +421,12 @@ msgid "An inventory must be selected"
|
||||
msgstr "An inventory must be selected"
|
||||
|
||||
#: screens/Template/WorkflowJobTemplateVisualizer/Modals/NodeModals/NodeTypeStep/InventorySourcesList.js:105
|
||||
#~ msgid "Ansible Tower"
|
||||
#~ msgstr "Ansible Tower"
|
||||
#~ msgid "Ansible Controller"
|
||||
#~ msgstr "Ansible Controller"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Ansible Tower Documentation."
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Ansible Controller Documentation."
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1079,11 +1079,11 @@ msgstr "Choose an HTTP method"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
@ -2818,26 +2818,26 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "Enter at least one search filter to create a new Smart Inventory"
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
"Ansible Controller documentation for example syntax."
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:65
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6358,9 +6358,9 @@ msgstr "Pass extra command line changes. There are two ansible command line para
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6586,13 +6586,13 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
@ -8143,12 +8143,12 @@ msgstr "Skip Tags"
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
@ -8331,10 +8331,10 @@ msgstr "Sources"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8693,12 +8693,12 @@ msgstr "Tabs"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
|
||||
@ -413,8 +413,8 @@ msgid "An inventory must be selected"
|
||||
msgstr "Debe seleccionar un inventario"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Documentación de Ansible Tower."
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Documentación de Ansible Controller."
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1063,9 +1063,9 @@ msgstr "Elegir un método HTTP"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr "Elija el tipo o formato de respuesta que desee como indicador para el usuario. Consulte la documentación de Ansible Tower para obtener más información sobre cada una de las opciones."
|
||||
msgstr "Elija el tipo o formato de respuesta que desee como indicador para el usuario. Consulte la documentación de Ansible Controller para obtener más información sobre cada una de las opciones."
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
msgid "Choose roles to apply to the selected resources. Note that all selected roles will be applied to all selected resources."
|
||||
@ -2774,26 +2774,25 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "Ingresar al menos un filtro de búsqueda para crear un nuevo inventario inteligente"
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Ingrese inyectores a través de la sintaxis JSON o YAML. Consulte la documentación de Ansible Tower para ver la sintaxis de ejemplo."
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Ingrese inyectores a través de la sintaxis JSON o YAML. Consulte la documentación de Ansible Controller para ver la sintaxis de ejemplo."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Ingrese entradas a través de la sintaxis JSON o YAML. Consulte la documentación de Ansible Tower para ver la sintaxis de ejemplo."
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Ingrese entradas a través de la sintaxis JSON o YAML. Consulte la documentación de Ansible Controller para ver la sintaxis de ejemplo."
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
msgstr ""
|
||||
"Ingrese variables de inventario mediante el uso de la sintaxis JSON o YAML.\n"
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr "Ingrese variables de inventario mediante el uso de la sintaxis JSON o YAML.\n"
|
||||
"Utilice el botón de selección para alternar entre las dos opciones. Consulte la\n"
|
||||
"documentación de Ansible Tower para acceder a ejemplos de sintaxis."
|
||||
"documentación de Ansible Controller para acceder a ejemplos de sintaxis."
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:92
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "Ingrese variables de inventario mediante el uso de la sintaxis JSON o YAML. Utilice el botón de selección para alternar entre las dos opciones. Consulte la documentación de Ansible Tower para acceder a ejemplos de sintaxis"
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "Ingrese variables de inventario mediante el uso de la sintaxis JSON o YAML. Utilice el botón de selección para alternar entre las dos opciones. Consulte la documentación de Ansible Controller para acceder a ejemplos de sintaxis"
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6258,20 +6257,19 @@ msgid "Pass extra command line changes. There are two ansible command line param
|
||||
msgstr "Trasladar cambios adicionales en la línea de comandos. Hay dos parámetros de línea de comandos de Ansible:"
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:413
|
||||
#~ msgid ""
|
||||
#~ "Pass extra command line variables to the playbook. This is the\n"
|
||||
#~ "-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr ""
|
||||
#~ "Traslade variables de línea de comando adicionales al playbook. Este es el\n"
|
||||
#~ "parámetro de línea de comando -e o --extra-vars para el playbook de Ansible.\n"
|
||||
#~ "Proporcione pares de claves/valores utilizando YAML o JSON. Consulte la\n"
|
||||
#~ "documentación para ver ejemplos de sintaxis."
|
||||
msgid ""
|
||||
"Pass extra command line variables to the playbook. This is the\n"
|
||||
"-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
"Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
"documentation for example syntax."
|
||||
msgstr "Traslade variables de línea de comando adicionales al playbook. Este es el\n"
|
||||
"parámetro de línea de comando -e o --extra-vars para el playbook de Ansible.\n"
|
||||
"Proporcione pares de claves/valores utilizando YAML o JSON. Consulte la\n"
|
||||
"documentación para ver ejemplos de sintaxis."
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Traslade variables de línea de comando adicionales al cuaderno de estrategias. Este es el parámetro de línea de comando -e o --extra-vars para el cuaderno de estrategias de Ansible. Proporcione pares de claves/valores utilizando YAML o JSON. Consulte la documentación de Ansible Tower para ver ejemplos de sintaxis."
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Traslade variables de línea de comando adicionales al cuaderno de estrategias. Este es el parámetro de línea de comando -e o --extra-vars para el cuaderno de estrategias de Ansible. Proporcione pares de claves/valores utilizando YAML o JSON. Consulte la documentación de Ansible Controller para ver ejemplos de sintaxis."
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6483,13 +6481,13 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr ""
|
||||
"Complete los hosts para este inventario utilizando un filtro de búsqueda\n"
|
||||
"de búsqueda. Ejemplo: ansible_facts.ansible_distribution: \"RedHat\".\n"
|
||||
"Consulte la documentación para obtener más sintaxis y\n"
|
||||
"ejemplos. Consulte la documentación de Ansible Tower para obtener más sintaxis y\n"
|
||||
"ejemplos. Consulte la documentación de Ansible Controller para obtener más sintaxis y\n"
|
||||
"ejemplos."
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
@ -8008,13 +8006,13 @@ msgstr "Omitir etiquetas"
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr ""
|
||||
"La omisión de etiquetas resulta útil cuando tiene un playbook\n"
|
||||
"de gran tamaño y desea omitir partes específicas de la tarea o la jugada.\n"
|
||||
"Utilice comas para separar las distintas etiquetas. Consulte la documentación\n"
|
||||
"de Ansible Tower para obtener información detallada sobre el uso de etiquetas."
|
||||
"de Ansible Controller para obtener información detallada sobre el uso de etiquetas."
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:21
|
||||
@ -8187,10 +8185,9 @@ msgstr "Fuentes"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
msgstr ""
|
||||
"Especifique los encabezados HTTP en formato JSON. Consulte la\n"
|
||||
"documentación de Ansible Tower para obtener ejemplos de sintaxis."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr "Especifique los encabezados HTTP en formato JSON. Consulte la\n"
|
||||
"documentación de Ansible Controller para obtener ejemplos de sintaxis."
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8536,12 +8533,12 @@ msgstr "Pestañas"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr ""
|
||||
"Las etiquetas resultan útiles cuando tiene un playbook de gran tamaño\n"
|
||||
"y desea ejecutar una parte específica de la tarea o la jugada. Utilice comas\n"
|
||||
"para separar varias etiquetas. Consulte la documentación de Ansible Tower\n"
|
||||
"para separar varias etiquetas. Consulte la documentación de Ansible Controller\n"
|
||||
"para obtener información detallada sobre el uso de etiquetas."
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
|
||||
@ -411,8 +411,8 @@ msgid "An inventory must be selected"
|
||||
msgstr "Un inventaire doit être sélectionné"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Documentation Ansible Tower"
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Documentation Ansible Controller"
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1053,9 +1053,9 @@ msgstr "Choisissez une méthode HTTP"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr "Spécifiez le type de format ou de type de réponse que vous souhaitez pour interroger l'utilisateur. Consultez la documentation d’Ansible Tower pour en savoir plus sur chaque option."
|
||||
msgstr "Spécifiez le type de format ou de type de réponse que vous souhaitez pour interroger l'utilisateur. Consultez la documentation d’Ansible Controller pour en savoir plus sur chaque option."
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
msgid "Choose roles to apply to the selected resources. Note that all selected roles will be applied to all selected resources."
|
||||
@ -2747,23 +2747,23 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "Veuillez saisir une expression de recherche au moins pour créer un nouvel inventaire Smart."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Entrez les injecteurs avec la syntaxe JSON ou YAML. Consultez la documentation d’Ansible Tower pour avoir un exemple de syntaxe."
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Entrez les injecteurs avec la syntaxe JSON ou YAML. Consultez la documentation d’Ansible Controller pour avoir un exemple de syntaxe."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Entrez les variables avec la syntaxe JSON ou YAML. Consultez la documentation d’Ansible Tower pour avoir un exemple de syntaxe."
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Entrez les variables avec la syntaxe JSON ou YAML. Consultez la documentation d’Ansible Controller pour avoir un exemple de syntaxe."
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
msgstr "Entrez les variables d’inventaire avec la syntaxe JSON ou YAML. Utilisez le bouton radio pour basculer entre les deux. Consultez la documentation d’Ansible Tower pour avoir un exemple de syntaxe."
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr "Entrez les variables d’inventaire avec la syntaxe JSON ou YAML. Utilisez le bouton radio pour basculer entre les deux. Consultez la documentation d’Ansible Controller pour avoir un exemple de syntaxe."
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:92
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "Entrez les variables d’inventaire avec la syntaxe JSON ou YAML. Utilisez le bouton radio pour basculer entre les deux. Consultez la documentation d’Ansible Tower pour avoir un exemple de syntaxe."
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "Entrez les variables d’inventaire avec la syntaxe JSON ou YAML. Utilisez le bouton radio pour basculer entre les deux. Consultez la documentation d’Ansible Controller pour avoir un exemple de syntaxe."
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6166,16 +6166,16 @@ msgid "Pass extra command line changes. There are two ansible command line param
|
||||
msgstr "Passez des changements supplémentaires en ligne de commande. Il y a deux paramètres de ligne de commande possibles :"
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:413
|
||||
#~ msgid ""
|
||||
#~ "Pass extra command line variables to the playbook. This is the\n"
|
||||
#~ "-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr "Transmettez des variables de ligne de commandes supplémentaires au playbook. Voici le paramètre de ligne de commande -e or --extra-vars pour ansible-playbook. Fournir la paire clé/valeur en utilisant YAML ou JSON. Consulter la documentation pour obtenir des exemples de syntaxe."
|
||||
msgid ""
|
||||
"Pass extra command line variables to the playbook. This is the\n"
|
||||
"-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
"Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
"documentation for example syntax."
|
||||
msgstr "Transmettez des variables de ligne de commandes supplémentaires au playbook. Voici le paramètre de ligne de commande -e or --extra-vars pour ansible-playbook. Fournir la paire clé/valeur en utilisant YAML ou JSON. Consulter la documentation pour obtenir des exemples de syntaxe."
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Transmettez des variables de ligne de commandes supplémentaires au playbook. Voici le paramètre de ligne de commande -e or --extra-vars pour ansible-playbook. Fournir la paire clé/valeur en utilisant YAML ou JSON. Consulter la documentation Ansible Tower pour obtenir des exemples de syntaxe."
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Transmettez des variables de ligne de commandes supplémentaires au playbook. Voici le paramètre de ligne de commande -e or --extra-vars pour ansible-playbook. Fournir la paire clé/valeur en utilisant YAML ou JSON. Consulter la documentation Ansible Controller pour obtenir des exemples de syntaxe."
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6387,9 +6387,9 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr "Remplissez les hôtes pour cet inventaire en utilisant un filtre de recherche. Exemple : ansible_facts.ansible_distribution : \"RedHat\". Reportez-vous à la documentation pour plus de syntaxe et d'exemples. Voir la documentation Ansible Tower pour des exemples de syntaxe."
|
||||
msgstr "Remplissez les hôtes pour cet inventaire en utilisant un filtre de recherche. Exemple : ansible_facts.ansible_distribution : \"RedHat\". Reportez-vous à la documentation pour plus de syntaxe et d'exemples. Voir la documentation Ansible Controller pour des exemples de syntaxe."
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:102
|
||||
@ -7853,21 +7853,21 @@ msgid "Skip Tags"
|
||||
msgstr "Balises de saut"
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:538
|
||||
#~ msgid ""
|
||||
#~ "Skip tags are useful when you have a\n"
|
||||
#~ "large playbook, and you want to skip specific parts of a\n"
|
||||
#~ "play or task. Use commas to separate multiple tags. Refer\n"
|
||||
#~ "to the documentation for details on the usage\n"
|
||||
#~ "of tags."
|
||||
#~ msgstr "Les balises de saut sont utiles si votre playbook est important et que vous souhaitez ignorer certaines parties d’un Job ou d’une Lecture. Utiliser des virgules pour séparer plusieurs balises. Consulter la documentation Ansible Tower pour obtenir des détails sur l'utilisation des balises."
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a\n"
|
||||
"large playbook, and you want to skip specific parts of a\n"
|
||||
"play or task. Use commas to separate multiple tags. Refer\n"
|
||||
"to the documentation for details on the usage\n"
|
||||
"of tags."
|
||||
msgstr "Les balises de saut sont utiles si votre playbook est important et que vous souhaitez ignorer certaines parties d’un Job ou d’une Lecture. Utiliser des virgules pour séparer plusieurs balises. Consulter la documentation Ansible Controller pour obtenir des détails sur l'utilisation des balises."
|
||||
|
||||
#: components/LaunchPrompt/steps/OtherPromptsStep.js:71
|
||||
#: components/LaunchPrompt/steps/OtherPromptsStep.js:70
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "Les balises de saut sont utiles si votre playbook est important et que vous souhaitez ignorer certaines parties d’un Job ou d’une Lecture. Utiliser des virgules pour séparer plusieurs balises. Consulter la documentation Ansible Tower pour obtenir des détails sur l'utilisation des balises."
|
||||
msgstr "Les balises de saut sont utiles si votre playbook est important et que vous souhaitez ignorer certaines parties d’un Job ou d’une Lecture. Utiliser des virgules pour séparer plusieurs balises. Consulter la documentation Ansible Controller pour obtenir des détails sur l'utilisation des balises."
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:21
|
||||
@ -8040,8 +8040,8 @@ msgstr "Sources"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
msgstr "Spécifier les En-têtes HTTP en format JSON. Voir la documentation Ansible Tower pour obtenir des exemples de syntaxe."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr "Spécifier les En-têtes HTTP en format JSON. Voir la documentation Ansible Controller pour obtenir des exemples de syntaxe."
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8381,9 +8381,9 @@ msgstr "Onglets"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "Les balises sont utiles si votre playbook est important et que vous souhaitez faire une lecture particulière ou exécuter une tâche spécifique. Utiliser des virgules pour séparer plusieurs balises. Consulter la documentation Ansible Tower pour obtenir des détails sur l'utilisation des balises."
|
||||
msgstr "Les balises sont utiles si votre playbook est important et que vous souhaitez faire une lecture particulière ou exécuter une tâche spécifique. Utiliser des virgules pour séparer plusieurs balises. Consulter la documentation Ansible Controller pour obtenir des détails sur l'utilisation des balises."
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:20
|
||||
|
||||
@ -411,8 +411,8 @@ msgid "An inventory must be selected"
|
||||
msgstr "インベントリーを選択する必要があります"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Ansible Tower ドキュメント。"
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Ansible Controller ドキュメント。"
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1053,9 +1053,9 @@ msgstr "HTTP メソッドの選択"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr "ユーザーに表示されるプロンプトとして使用する回答タイプまたは形式を選択します。各オプションの詳細については、Ansible Tower のドキュメントを参照してください。"
|
||||
msgstr "ユーザーに表示されるプロンプトとして使用する回答タイプまたは形式を選択します。各オプションの詳細については、Ansible Controller のドキュメントを参照してください。"
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
msgid "Choose roles to apply to the selected resources. Note that all selected roles will be applied to all selected resources."
|
||||
@ -2747,23 +2747,23 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "新規スマートインベントリーを作成するために 1 つ以上の検索フィルターを入力してください。"
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON または YAML 構文のいずれかを使用してインジェクターを入力します。構文のサンプルについては Ansible Tower ドキュメントを参照してください。"
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON または YAML 構文のいずれかを使用してインジェクターを入力します。構文のサンプルについては Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON または YAML 構文のいずれかを使用して入力を行います。構文のサンプルについては Ansible Tower ドキュメントを参照してください。"
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON または YAML 構文のいずれかを使用して入力を行います。構文のサンプルについては Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON または YAML 構文のいずれかを使用してインベントリー変数を入力します。ラジオボタンを使用して構文間で切り替えを行います。構文のサンプルについては Ansible Tower ドキュメントを参照してください。"
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON または YAML 構文のいずれかを使用してインベントリー変数を入力します。ラジオボタンを使用して構文間で切り替えを行います。構文のサンプルについては Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:92
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "JSON または YAML 構文のいずれかを使用してインベントリー変数を入力します。ラジオボタンを使用して構文で切り替えを行います。構文のサンプルについては Ansible Tower ドキュメントを参照してください。"
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "JSON または YAML 構文のいずれかを使用してインベントリー変数を入力します。ラジオボタンを使用して構文で切り替えを行います。構文のサンプルについては Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6164,16 +6164,16 @@ msgid "Pass extra command line changes. There are two ansible command line param
|
||||
msgstr "追加のコマンドライン変更を渡します。2 つの Ansible コマンドラインパラメーターがあります。"
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:413
|
||||
#~ msgid ""
|
||||
#~ "Pass extra command line variables to the playbook. This is the\n"
|
||||
#~ "-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr "追加のコマンドライン変数を Playbook に渡します。これは、ansible-playbook の -e または --extra-vars コマンドラインパラメーターです。YAML または JSON のいずれかを使用してキーと値のペアを指定します。構文のサンプルについてはドキュメントを参照してください。"
|
||||
msgid ""
|
||||
"Pass extra command line variables to the playbook. This is the\n"
|
||||
"-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
"Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
"documentation for example syntax."
|
||||
msgstr "追加のコマンドライン変数を Playbook に渡します。これは、ansible-playbook の -e または --extra-vars コマンドラインパラメーターです。YAML または JSON のいずれかを使用してキーと値のペアを指定します。構文のサンプルについてはドキュメントを参照してください。"
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "追加のコマンドライン変数を Playbook に渡します。これは、ansible-playbook の -e または --extra-vars コマンドラインパラメーターです。YAML または JSON のいずれかを使用してキーと値のペアを指定します。構文のサンプルについては Ansible Tower ドキュメントを参照してください。"
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "追加のコマンドライン変数を Playbook に渡します。これは、ansible-playbook の -e または --extra-vars コマンドラインパラメーターです。YAML または JSON のいずれかを使用してキーと値のペアを指定します。構文のサンプルについては Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6385,9 +6385,9 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr "検索フィルターを使用して、このインベントリーのホストにデータを入力します (例: ansible_facts__ansible_distribution:\"RedHat\")。詳細な構文と例については、ドキュメントを参照してください。構文と例の詳細については、Ansible Tower のドキュメントを参照してください。"
|
||||
msgstr "検索フィルターを使用して、このインベントリーのホストにデータを入力します (例: ansible_facts__ansible_distribution:\"RedHat\")。詳細な構文と例については、ドキュメントを参照してください。構文と例の詳細については、Ansible Controller のドキュメントを参照してください。"
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:102
|
||||
@ -7861,9 +7861,9 @@ msgstr "スキップタグ"
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "スキップタグは、Playbook のサイズが大きい場合にプレイまたはタスクの特定の部分をスキップする必要がある場合に役立ちます。コンマを使用して複数のタグを区切ります。タグの使用方法の詳細については、Ansible Tower ドキュメントを参照してください。"
|
||||
msgstr "スキップタグは、Playbook のサイズが大きい場合にプレイまたはタスクの特定の部分をスキップする必要がある場合に役立ちます。コンマを使用して複数のタグを区切ります。タグの使用方法の詳細については、Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:21
|
||||
@ -8036,8 +8036,8 @@ msgstr "ソース"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON 形式で HTTP ヘッダーを指定します。構文のサンプルについては Ansible Tower ドキュメントを参照してください。"
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON 形式で HTTP ヘッダーを指定します。構文のサンプルについては Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8371,9 +8371,9 @@ msgstr "タブ"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "タグは、Playbook のサイズが大きい場合にプレイまたはタスクの特定の部分を実行する必要がある場合に役立ちます。コンマを使用して複数のタグを区切ります。タグの使用方法の詳細については、Ansible Tower ドキュメントを参照してください。"
|
||||
msgstr "タグは、Playbook のサイズが大きい場合にプレイまたはタスクの特定の部分を実行する必要がある場合に役立ちます。コンマを使用して複数のタグを区切ります。タグの使用方法の詳細については、Ansible Controller ドキュメントを参照してください。"
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:20
|
||||
|
||||
@ -411,8 +411,8 @@ msgid "An inventory must be selected"
|
||||
msgstr "인벤토리를 선택해야 합니다"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Ansible Tower 설명서"
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Ansible Controller 설명서"
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1053,9 +1053,9 @@ msgstr "HTTP 방법 선택"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr "사용자에 대한 프롬프트로 원하는 응답 유형 또는 형식을 선택합니다. 각 옵션에 대한 자세한 내용은 Ansible Tower 설명서를 참조하십시오."
|
||||
msgstr "사용자에 대한 프롬프트로 원하는 응답 유형 또는 형식을 선택합니다. 각 옵션에 대한 자세한 내용은 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
msgid "Choose roles to apply to the selected resources. Note that all selected roles will be applied to all selected resources."
|
||||
@ -2747,23 +2747,23 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "새 스마트 인벤토리를 생성하려면 하나 이상의 검색 필터를 입력합니다."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 인젝터를 입력합니다. 구문 예제는 Ansible Tower 설명서를 참조하십시오."
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 인젝터를 입력합니다. 구문 예제는 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 입력합니다. 구문 예제는 Ansible Tower 설명서를 참조하십시오."
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 입력합니다. 구문 예제는 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 인벤토리 변수를 입력합니다. 라디오 버튼을 사용하여 두 항목 사이를 전환합니다. 구문 예제는 Ansible Tower 설명서를 참조하십시오."
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 인벤토리 변수를 입력합니다. 라디오 버튼을 사용하여 두 항목 사이를 전환합니다. 구문 예제는 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:92
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "JSON 또는 YAML 구문을 사용하여 인벤토리 변수를 입력합니다. 라디오 버튼을 사용하여 두 항목 사이를 전환합니다. 구문 예제는 Ansible Tower 설명서를 참조하십시오."
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "JSON 또는 YAML 구문을 사용하여 인벤토리 변수를 입력합니다. 라디오 버튼을 사용하여 두 항목 사이를 전환합니다. 구문 예제는 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6164,16 +6164,16 @@ msgid "Pass extra command line changes. There are two ansible command line param
|
||||
msgstr "추가 명령줄 변경 사항을 전달합니다. 두 가지 ansible 명령행 매개변수가 있습니다."
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:413
|
||||
#~ msgid ""
|
||||
#~ "Pass extra command line variables to the playbook. This is the\n"
|
||||
#~ "-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr "플레이북에 추가 명령줄 변수를 전달합니다. ansible-playbook에 대해 -e 또는 --extra-vars 명령줄 매개 변수입니다. YAML 또는 JSON을 사용하여 키/값 쌍을 제공합니다. 예제 구문에 대한 설명서를 참조하십시오."
|
||||
msgid ""
|
||||
"Pass extra command line variables to the playbook. This is the\n"
|
||||
"-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
"Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
"documentation for example syntax."
|
||||
msgstr "플레이북에 추가 명령줄 변수를 전달합니다. ansible-playbook에 대해 -e 또는 --extra-vars 명령줄 매개 변수입니다. YAML 또는 JSON을 사용하여 키/값 쌍을 제공합니다. 예제 구문에 대한 설명서를 참조하십시오."
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "플레이북에 추가 명령줄 변수를 전달합니다. ansible-playbook에 대해 -e 또는 --extra-vars 명령줄 매개 변수입니다. YAML 또는 JSON을 사용하여 키/값 쌍을 제공합니다. 예제 구문에 대한 Ansible Tower 설명서를 참조하십시오."
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "플레이북에 추가 명령줄 변수를 전달합니다. ansible-playbook에 대해 -e 또는 --extra-vars 명령줄 매개 변수입니다. YAML 또는 JSON을 사용하여 키/값 쌍을 제공합니다. 예제 구문에 대한 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6385,9 +6385,9 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr "검색 필터를 사용하여 이 인벤토리의 호스트를 채웁니다. 예: ansible_facts__ansible_distribution:\"RedHat\". 추가 구문 및 예제를 보려면 설명서를 참조하십시오. 추가 구문 및 예를 보려면 Ansible Tower 설명서를 참조하십시오."
|
||||
msgstr "검색 필터를 사용하여 이 인벤토리의 호스트를 채웁니다. 예: ansible_facts__ansible_distribution:\"RedHat\". 추가 구문 및 예제를 보려면 설명서를 참조하십시오. 추가 구문 및 예를 보려면 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:102
|
||||
@ -7861,9 +7861,9 @@ msgstr "태그 건너뛰기"
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "건너뛰기 태그는 대용량 플레이북이 있고 플레이 또는 작업의 특정 부분을 건너뛰려는 경우 유용합니다. 쉼표를 사용하여 여러 태그를 구분합니다. 태그 사용에 대한 자세한 내용은 Ansible Tower 설명서를 참조하십시오."
|
||||
msgstr "건너뛰기 태그는 대용량 플레이북이 있고 플레이 또는 작업의 특정 부분을 건너뛰려는 경우 유용합니다. 쉼표를 사용하여 여러 태그를 구분합니다. 태그 사용에 대한 자세한 내용은 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:21
|
||||
@ -8036,8 +8036,8 @@ msgstr "소스"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
msgstr "HTTP 헤더를 JSON 형식으로 지정합니다. 예를 들어 Ansible Tower 설명서를 참조하십시오."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr "HTTP 헤더를 JSON 형식으로 지정합니다. 예를 들어 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8371,9 +8371,9 @@ msgstr "탭"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "태그는 대용량 플레이북이 있고 플레이 또는 작업의 특정 부분을 실행하려는 경우 유용합니다. 쉼표를 사용하여 여러 태그를 구분합니다. 태그 사용에 대한 자세한 내용은 Ansible Tower 설명서를 참조하십시오."
|
||||
msgstr "태그는 대용량 플레이북이 있고 플레이 또는 작업의 특정 부분을 실행하려는 경우 유용합니다. 쉼표를 사용하여 여러 태그를 구분합니다. 태그 사용에 대한 자세한 내용은 Ansible Controller 설명서를 참조하십시오."
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:20
|
||||
|
||||
@ -411,8 +411,8 @@ msgid "An inventory must be selected"
|
||||
msgstr "Er moet een inventaris worden gekozen"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Documentatie Ansible Tower."
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Documentatie Ansible Controller."
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1055,9 +1055,9 @@ msgstr "Kies een HTTP-methode"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr "Kies een antwoordtype of -formaat dat u als melding voor de gebruiker wilt. Raadpleeg de documentatie van Ansible Tower voor meer informatie over iedere optie."
|
||||
msgstr "Kies een antwoordtype of -formaat dat u als melding voor de gebruiker wilt. Raadpleeg de documentatie van Ansible Controller voor meer informatie over iedere optie."
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
msgid "Choose roles to apply to the selected resources. Note that all selected roles will be applied to all selected resources."
|
||||
@ -2753,23 +2753,23 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "Voer ten minste één zoekfilter in om een nieuwe Smart-inventaris te maken."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Geef injectoren op met JSON- of YAML-syntaxis. Raadpleeg de documentatie voor Ansible Tower voor voorbeeldsyntaxis."
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Geef injectoren op met JSON- of YAML-syntaxis. Raadpleeg de documentatie voor Ansible Controller voor voorbeeldsyntaxis."
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Geef inputs op met JSON- of YAML-syntaxis. Raadpleeg de documentatie voor Ansible Tower voor voorbeeldsyntaxis."
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Geef inputs op met JSON- of YAML-syntaxis. Raadpleeg de documentatie voor Ansible Controller voor voorbeeldsyntaxis."
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
msgstr "Voer de variabelen van het inventaris in met JSON- of YAML-syntaxis. Gebruik de radio-knop om tussen de twee te wisselen. Raadpleeg de documentatie van Ansible Tower voor voorbeeldsyntaxis."
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr "Voer de variabelen van het inventaris in met JSON- of YAML-syntaxis. Gebruik de radio-knop om tussen de twee te wisselen. Raadpleeg de documentatie van Ansible Controller voor voorbeeldsyntaxis."
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:92
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "Voer de variabelen van het inventaris in met JSON- of YAML-syntaxis. Gebruik de radio-knop om tussen de twee te wisselen. Raadpleeg de documentatie van Ansible Tower voor voorbeeldsyntaxis."
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "Voer de variabelen van het inventaris in met JSON- of YAML-syntaxis. Gebruik de radio-knop om tussen de twee te wisselen. Raadpleeg de documentatie van Ansible Controller voor voorbeeldsyntaxis."
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6180,16 +6180,16 @@ msgid "Pass extra command line changes. There are two ansible command line param
|
||||
msgstr "Geef extra opdrachtregelwijzigingen in door. Er zijn twee opdrachtregelparameters voor Ansible:"
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:413
|
||||
#~ msgid ""
|
||||
#~ "Pass extra command line variables to the playbook. This is the\n"
|
||||
#~ "-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr "Geef extra opdrachtregelvariabelen op in het draaiboek. Dit is de opdrachtregelparameter -e of --extra-vars voor het Ansible-draaiboek. Geef sleutel/waarde-paren op met YAML of JSON. Raadpleeg de documentatie voor voorbeeldsyntaxis"
|
||||
msgid ""
|
||||
"Pass extra command line variables to the playbook. This is the\n"
|
||||
"-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
"Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
"documentation for example syntax."
|
||||
msgstr "Geef extra opdrachtregelvariabelen op in het draaiboek. Dit is de opdrachtregelparameter -e of --extra-vars voor het Ansible-draaiboek. Geef sleutel/waarde-paren op met YAML of JSON. Raadpleeg de documentatie voor voorbeeldsyntaxis"
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "Geef extra commandoregelvariabelen op in het draaiboek. Dit is de commandoregelparameter -e of --extra-vars voor het ansible-draaiboek. Geef sleutel/waarde-paren op met YAML of JSON. Raadpleeg de documentatie van Ansible Tower voor voorbeeldsyntaxis"
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "Geef extra commandoregelvariabelen op in het draaiboek. Dit is de commandoregelparameter -e of --extra-vars voor het ansible-draaiboek. Geef sleutel/waarde-paren op met YAML of JSON. Raadpleeg de documentatie van Ansible Controller voor voorbeeldsyntaxis"
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6401,12 +6401,12 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr ""
|
||||
"Vul de hosts voor deze inventaris door gebruik te maken van een zoekfilter. Voorbeeld: ansible_facts.ansible_distribution: \"RedHat\".\n"
|
||||
"Raadpleeg de documentatie voor verdere syntaxis en\n"
|
||||
"voorbeelden. Raadpleeg de documentatie van Ansible Tower voor verdere syntaxis en\n"
|
||||
"voorbeelden. Raadpleeg de documentatie van Ansible Controller voor verdere syntaxis en\n"
|
||||
"voorbeelden."
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
@ -7883,9 +7883,9 @@ msgstr "Tags overslaan"
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "Tags overslaan is nuttig wanneer u een groot draaiboek heeft en specifieke delen van het draaiboek of een taak wilt overslaan. Gebruik een komma om meerdere tags van elkaar te scheiden. Raadpleeg de documentatie van Ansible Tower voor meer informatie over het gebruik van tags."
|
||||
msgstr "Tags overslaan is nuttig wanneer u een groot draaiboek heeft en specifieke delen van het draaiboek of een taak wilt overslaan. Gebruik een komma om meerdere tags van elkaar te scheiden. Raadpleeg de documentatie van Ansible Controller voor meer informatie over het gebruik van tags."
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:21
|
||||
@ -8058,8 +8058,8 @@ msgstr "Bronnen"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
msgstr "Specificeer HTTP-koppen in JSON-formaat. Raadpleeg de documentatie van Ansible Tower voor voorbeeldsyntaxis."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr "Specificeer HTTP-koppen in JSON-formaat. Raadpleeg de documentatie van Ansible Controller voor voorbeeldsyntaxis."
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8397,9 +8397,9 @@ msgstr "Tabbladen"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "Tags zijn nuttig wanneer u een groot draaiboek heeft en specifieke delen van het draaiboek of een taak wilt uitvoeren. Gebruik een komma om meerdere tags van elkaar te scheiden. Raadpleeg de documentatie van Ansible Tower voor meer informatie over het gebruik van tags."
|
||||
msgstr "Tags zijn nuttig wanneer u een groot draaiboek heeft en specifieke delen van het draaiboek of een taak wilt uitvoeren. Gebruik een komma om meerdere tags van elkaar te scheiden. Raadpleeg de documentatie van Ansible Controller voor meer informatie over het gebruik van tags."
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:20
|
||||
|
||||
@ -411,8 +411,8 @@ msgid "An inventory must be selected"
|
||||
msgstr "必须选择一个清单"
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgstr "Ansible Tower 文档"
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr "Ansible Controller 文档"
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
msgid "Answer type"
|
||||
@ -1053,9 +1053,9 @@ msgstr "选择 HTTP 方法"
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr "选择您想要作为用户提示的回答类型或格式。请参阅 Ansible Tower 文档来了解每个选项的更多其他信息。"
|
||||
msgstr "选择您想要作为用户提示的回答类型或格式。请参阅 Ansible Controller 文档来了解每个选项的更多其他信息。"
|
||||
|
||||
#: components/AddRole/SelectRoleStep.js:20
|
||||
msgid "Choose roles to apply to the selected resources. Note that all selected roles will be applied to all selected resources."
|
||||
@ -2747,23 +2747,23 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr "请至少输入一个搜索过滤来创建一个新的智能清单。"
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "使用 JSON 或 YAML 语法输入注入程序。示例语法请参阅 Ansible Tower 文档。"
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "使用 JSON 或 YAML 语法输入注入程序。示例语法请参阅 Ansible Controller 文档。"
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "使用 JSON 或 YAML 语法进行输入。示例语法请参阅 Ansible Tower 文档。"
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "使用 JSON 或 YAML 语法进行输入。示例语法请参阅 Ansible Controller 文档。"
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
msgstr "使用 JSON 或 YAML 语法输入清单变量。使用单选按钮在两者之间切换。示例语法请参阅 Ansible Tower 文档。"
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr "使用 JSON 或 YAML 语法输入清单变量。使用单选按钮在两者之间切换。示例语法请参阅 Ansible Controller 文档。"
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:92
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr "使用 JSON 或 YAML 语法输入清单变量。使用单选按钮在两者之间切换。示例语法请参阅 Ansible Tower 文档"
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr "使用 JSON 或 YAML 语法输入清单变量。使用单选按钮在两者之间切换。示例语法请参阅 Ansible Controller 文档"
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6164,18 +6164,17 @@ msgid "Pass extra command line changes. There are two ansible command line param
|
||||
msgstr "传递额外的命令行更改。有两个 ansible 命令行参数："
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:413
|
||||
#~ msgid ""
|
||||
#~ "Pass extra command line variables to the playbook. This is the\n"
|
||||
#~ "-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
#~ "Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr ""
|
||||
#~ "向 playbook 传递额外的命令行变量。这是 ansible-playbook 的 -e 或 --extra-vars 命令行参数。使用 YAML \n"
|
||||
#~ "或 JSON 提供键/值对。示例语法请参阅相关文档。"
|
||||
msgid ""
|
||||
"Pass extra command line variables to the playbook. This is the\n"
|
||||
"-e or --extra-vars command line parameter for ansible-playbook.\n"
|
||||
"Provide key/value pairs using either YAML or JSON. Refer to the\n"
|
||||
"documentation for example syntax."
|
||||
msgstr "向 playbook 传递额外的命令行变量。这是 ansible-playbook 的 -e 或 --extra-vars 命令行参数。使用 YAML \n"
|
||||
"或 JSON 提供键/值对。示例语法请参阅相关文档。"
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgstr "向 playbook 传递额外的命令行变量。这是 ansible-playbook 的 -e 或 --extra-vars 命令行参数。使用 YAML 或 JSON 提供键/值对。示例语法请参阅 Ansible Tower 文档。"
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr "向 playbook 传递额外的命令行变量。这是 ansible-playbook 的 -e 或 --extra-vars 命令行参数。使用 YAML 或 JSON 提供键/值对。示例语法请参阅 Ansible Controller 文档。"
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:13
|
||||
@ -6387,9 +6386,9 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr "使用搜索过滤器填充此清单的主机。例如：ansible_facts__ansible_distribution:\"RedHat\"。如需语法和实例的更多信息，请参阅相关文档。请参阅 Ansible Tower 文档来获得更多信息。"
|
||||
msgstr "使用搜索过滤器填充此清单的主机。例如：ansible_facts__ansible_distribution:\"RedHat\"。如需语法和实例的更多信息，请参阅相关文档。请参阅 Ansible Controller 文档来获得更多信息。"
|
||||
|
||||
#: screens/NotificationTemplate/NotificationTemplateDetail/NotificationTemplateDetail.js:164
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:102
|
||||
@ -7865,9 +7864,9 @@ msgstr "跳过标签"
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "如果有一个大的 playbook，而您想要跳过某个 play 或任务的特定部分，则跳过标签会很有用。使用逗号分隔多个标签。请参阅 Ansible Tower 文档了解使用标签的详情。"
|
||||
msgstr "如果有一个大的 playbook，而您想要跳过某个 play 或任务的特定部分，则跳过标签会很有用。使用逗号分隔多个标签。请参阅 Ansible Controller 文档了解使用标签的详情。"
|
||||
|
||||
#: screens/Job/Job.helptext.js:19
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:21
|
||||
@ -8040,8 +8039,8 @@ msgstr "源"
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
msgstr "以 JSON 格式指定 HTTP 标头。示例语法请参阅 Ansible Tower 文档。"
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr "以 JSON 格式指定 HTTP 标头。示例语法请参阅 Ansible Controller 文档。"
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
msgid ""
|
||||
@ -8363,21 +8362,21 @@ msgid "Tabs"
|
||||
msgstr "制表符"
|
||||
|
||||
#: screens/Template/shared/JobTemplateForm.js:522
|
||||
#~ msgid ""
|
||||
#~ "Tags are useful when you have a large\n"
|
||||
#~ "playbook, and you want to run a specific part of a\n"
|
||||
#~ "play or task. Use commas to separate multiple tags.\n"
|
||||
#~ "Refer to the documentation for details on\n"
|
||||
#~ "the usage of tags."
|
||||
#~ msgstr "如果有一个大的 playbook，而您想要运行某个 play 或任务的特定部分，则标签会很有用。使用逗号分隔多个标签。请参阅 Ansible Tower 文档了解使用标签的详情。"
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a\n"
|
||||
"play or task. Use commas to separate multiple tags.\n"
|
||||
"Refer to the documentation for details on\n"
|
||||
"the usage of tags."
|
||||
msgstr "如果有一个大的 playbook，而您想要运行某个 play 或任务的特定部分，则标签会很有用。使用逗号分隔多个标签。请参阅 Ansible Controller 文档了解使用标签的详情。"
|
||||
|
||||
#: components/LaunchPrompt/steps/OtherPromptsStep.js:59
|
||||
#: components/LaunchPrompt/steps/OtherPromptsStep.js:58
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr "如果有一个大的 playbook，而您想要运行某个 play 或任务的特定部分，则标签会很有用。使用逗号分隔多个标签。请参阅 Ansible Tower 文档了解使用标签的详情。"
|
||||
msgstr "如果有一个大的 playbook，而您想要运行某个 play 或任务的特定部分，则标签会很有用。使用逗号分隔多个标签。请参阅 Ansible Controller 文档了解使用标签的详情。"
|
||||
|
||||
#: screens/Job/Job.helptext.js:18
|
||||
#: screens/Template/shared/JobTemplate.helptext.js:20
|
||||
|
||||
@ -412,11 +412,11 @@ msgid "An inventory must be selected"
|
||||
msgstr ""
|
||||
|
||||
#: screens/Template/WorkflowJobTemplateVisualizer/Modals/NodeModals/NodeTypeStep/InventorySourcesList.js:105
|
||||
#~ msgid "Ansible Tower"
|
||||
#~ msgid "Ansible Controller"
|
||||
#~ msgstr ""
|
||||
|
||||
#: screens/NotificationTemplate/shared/CustomMessagesSubForm.js:96
|
||||
msgid "Ansible Tower Documentation."
|
||||
msgid "Ansible Controller Documentation."
|
||||
msgstr ""
|
||||
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:43
|
||||
@ -1058,7 +1058,7 @@ msgstr ""
|
||||
#: screens/Template/Survey/SurveyQuestionForm.js:46
|
||||
msgid ""
|
||||
"Choose an answer type or format you want as the prompt for the user.\n"
|
||||
"Refer to the Ansible Tower Documentation for more additional\n"
|
||||
"Refer to the Ansible Controller Documentation for more additional\n"
|
||||
"information about each option."
|
||||
msgstr ""
|
||||
|
||||
@ -2764,23 +2764,23 @@ msgid "Enter at least one search filter to create a new Smart Inventory"
|
||||
msgstr ""
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:43
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgid "Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
|
||||
#: screens/CredentialType/shared/CredentialTypeForm.js:35
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax."
|
||||
msgid "Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
|
||||
#: screens/Inventory/shared/SmartInventoryForm.js:94
|
||||
msgid ""
|
||||
"Enter inventory variables using either JSON or YAML syntax.\n"
|
||||
"Use the radio button to toggle between the two. Refer to the\n"
|
||||
"Ansible Tower documentation for example syntax."
|
||||
"Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
|
||||
#: screens/Inventory/shared/InventoryForm.js:65
|
||||
#~ msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Tower documentation for example syntax"
|
||||
#~ msgstr ""
|
||||
msgid "Enter inventory variables using either JSON or YAML syntax. Use the radio button to toggle between the two. Refer to the Ansible Controller documentation for example syntax"
|
||||
msgstr ""
|
||||
|
||||
#: screens/NotificationTemplate/shared/TypeInputsSubForm.js:181
|
||||
#~ msgid "Enter one Annotation Tag per line, without commas."
|
||||
@ -6218,8 +6218,8 @@ msgstr ""
|
||||
#~ "documentation for example syntax."
|
||||
#~ msgstr ""
|
||||
|
||||
#: screens/Template/shared/WorkflowJobTemplate.helptext.js:14
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax."
|
||||
#: screens/Template/shared/WorkflowJobTemplateForm.js:215
|
||||
msgid "Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
|
||||
#: screens/Job/Job.helptext.js:12
|
||||
@ -6441,7 +6441,7 @@ msgid ""
|
||||
"Populate the hosts for this inventory by using a search\n"
|
||||
"filter. Example: ansible_facts__ansible_distribution:\"RedHat\".\n"
|
||||
"Refer to the documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Tower documentation for further syntax and\n"
|
||||
"examples. Refer to the Ansible Controller documentation for further syntax and\n"
|
||||
"examples."
|
||||
msgstr ""
|
||||
|
||||
@ -7943,7 +7943,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"Skip tags are useful when you have a large\n"
|
||||
"playbook, and you want to skip specific parts of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr ""
|
||||
|
||||
@ -8127,7 +8127,7 @@ msgstr ""
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:30
|
||||
msgid ""
|
||||
"Specify HTTP Headers in JSON format. Refer to\n"
|
||||
"the Ansible Tower documentation for example syntax."
|
||||
"the Ansible Controller documentation for example syntax."
|
||||
msgstr ""
|
||||
|
||||
#: screens/NotificationTemplate/shared/Notifications.helptext.js:24
|
||||
@ -8474,7 +8474,7 @@ msgstr ""
|
||||
msgid ""
|
||||
"Tags are useful when you have a large\n"
|
||||
"playbook, and you want to run a specific part of a play or task.\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Tower\n"
|
||||
"Use commas to separate multiple tags. Refer to Ansible Controller\n"
|
||||
"documentation for details on the usage of tags."
|
||||
msgstr ""
|
||||
|
||||
|
||||
@ -418,7 +418,7 @@ describe('<CredentialForm />', () => {
|
||||
).toBe(false);
|
||||
expect(wrapper.find('FormGroup[label="Credential Type"]').length).toBe(1);
|
||||
expect(
|
||||
wrapper.find('FormGroup[label="Ansible Tower Hostname"]').length
|
||||
wrapper.find('FormGroup[label="Ansible Controller Hostname"]').length
|
||||
).toBe(1);
|
||||
expect(wrapper.find('FormGroup[label="Username"]').length).toBe(1);
|
||||
expect(wrapper.find('FormGroup[label="Password"]').length).toBe(1);
|
||||
|
||||
@ -61,7 +61,7 @@
|
||||
},
|
||||
"created": "2020-05-18T21:53:35.334813Z",
|
||||
"modified": "2020-05-18T21:54:05.424087Z",
|
||||
"name": "Ansible Tower",
|
||||
"name": "Ansible Controller",
|
||||
"description": "",
|
||||
"kind": "cloud",
|
||||
"namespace": "tower",
|
||||
@ -70,9 +70,9 @@
|
||||
"fields": [
|
||||
{
|
||||
"id": "host",
|
||||
"label": "Ansible Tower Hostname",
|
||||
"label": "Ansible Controller Hostname",
|
||||
"type": "string",
|
||||
"help_text": "The Ansible Tower base URL to authenticate with."
|
||||
"help_text": "The Ansible Controller base URL to authenticate with."
|
||||
},
|
||||
{
|
||||
"id": "username",
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
"type": "credential",
|
||||
"url": "/api/v2/credentials/4/",
|
||||
"related": {
|
||||
"named_url": "/api/v2/credentials/Tower cred++Ansible Tower+cloud++/",
|
||||
"named_url": "/api/v2/credentials/Tower cred++Ansible Controller+cloud++/",
|
||||
"created_by": "/api/v2/users/2/",
|
||||
"modified_by": "/api/v2/users/2/",
|
||||
"activity_stream": "/api/v2/credentials/4/activity_stream/",
|
||||
@ -19,7 +19,7 @@
|
||||
"summary_fields": {
|
||||
"credential_type": {
|
||||
"id": 16,
|
||||
"name": "Ansible Tower",
|
||||
"name": "Ansible Controller",
|
||||
"description": ""
|
||||
},
|
||||
"created_by": {
|
||||
|
||||
@ -32,7 +32,7 @@ function CredentialTypeFormFields() {
|
||||
/>
|
||||
<FormFullWidthLayout>
|
||||
<VariablesField
|
||||
tooltip={t`Enter inputs using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax.`}
|
||||
tooltip={t`Enter inputs using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax.`}
|
||||
id="credential-type-inputs-configuration"
|
||||
name="inputs"
|
||||
label={t`Input configuration`}
|
||||
@ -40,7 +40,7 @@ function CredentialTypeFormFields() {
|
||||
</FormFullWidthLayout>
|
||||
<FormFullWidthLayout>
|
||||
<VariablesField
|
||||
tooltip={t`Enter injectors using either JSON or YAML syntax. Refer to the Ansible Tower documentation for example syntax.`}
|
||||
tooltip={t`Enter injectors using either JSON or YAML syntax. Refer to the Ansible Controller documentation for example syntax.`}
|
||||
id="credential-type-injectors-configuration"
|
||||
name="injectors"
|
||||
label={t`Injector configuration`}
|
||||
|
||||
@ -93,7 +93,7 @@ const SmartInventoryFormFields = ({ inventory }) => {
|
||||
label={t`Variables`}
|
||||
tooltip={t`Enter inventory variables using either JSON or YAML syntax.
|
||||
Use the radio button to toggle between the two. Refer to the
|
||||
Ansible Tower documentation for example syntax.`}
|
||||
Ansible Controller documentation for example syntax.`}
|
||||
/>
|
||||
</FormFullWidthLayout>
|
||||
</>
|
||||
|
||||
@ -93,7 +93,7 @@ function CustomMessagesSubForm({ defaultMessages, type }) {
|
||||
config
|
||||
)}/html/userguide/notifications.html#create-custom-notifications`}
|
||||
>
|
||||
{t`Ansible Tower Documentation.`}
|
||||
{t`Ansible Controller Documentation.`}
|
||||
</a>
|
||||
</small>
|
||||
</Text>
|
||||
|
||||
@ -28,7 +28,7 @@ const helpText = {
|
||||
twilioDestinationNumbers: t`Use one phone number per line to specify where to
|
||||
route SMS messages. Phone numbers should be formatted +11231231234. For more information see Twilio documentation`,
|
||||
webhookHeaders: t`Specify HTTP Headers in JSON format. Refer to
|
||||
the Ansible Tower documentation for example syntax.`,
|
||||
the Ansible Controller documentation for example syntax.`,
|
||||
};
|
||||
|
||||
export default helpText;
|
||||
|
||||
@ -44,7 +44,7 @@ function AnswerTypeField() {
|
||||
labelIcon={
|
||||
<Popover
|
||||
content={t`Choose an answer type or format you want as the prompt for the user.
|
||||
Refer to the Ansible Tower Documentation for more additional
|
||||
Refer to the Ansible Controller Documentation for more additional
|
||||
information about each option.`}
|
||||
/>
|
||||
}
|
||||
|
||||
@ -11,7 +11,7 @@ const wfHelpTextStrings = {
|
||||
labels: t`Optional labels that describe this job template,
|
||||
such as 'dev' or 'test'. Labels can be used to group and filter
|
||||
job templates and completed jobs.`,
|
||||
variables: t`Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Tower documentation for example syntax.`,
|
||||
variables: t`Pass extra command line variables to the playbook. This is the -e or --extra-vars command line parameter for ansible-playbook. Provide key/value pairs using either YAML or JSON. Refer to the Ansible Controller documentation for example syntax.`,
|
||||
enableWebhook: t`Enable Webhook for this workflow job template.`,
|
||||
enableConcurrentJobs: t`If enabled, simultaneous runs of this workflow job template will be allowed.`,
|
||||
webhookURL: t`Webhook services can launch jobs with this workflow job template by making a POST request to this URL.`,
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user