External-Mirrors/awx
2
0
Fork 0
mirror of https://github.com/ansible/awx.git synced 2026-02-01 01:28:09 -03:30
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #6232 from ryanpetrello/jt_promptable_extra_creds

Browse Source 
add prompting for JT.extra_credentials
This commit is contained in:
Ryan Petrello
2017-05-11 07:51:36 -04:00
committed by GitHub
parent 2b15d04096 53c3ece32b
commit 44c1935590
12 changed files with 304 additions and 38 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/CHANGELOG.md
View File

@@ -14,3 +14,18 @@
[[#5741](https://github.com/ansible/ansible-tower/issues/5741)]
* support sourcing inventory from a file inside of a project's source
tree [[#2477](https://github.com/ansible/ansible-tower/issues/2477)]
* added support for custom cloud and network credential types, which give the
customer the ability to modify environment variables, extra vars, and
generate file-based credentials (such as file-based certificates or .ini
files) at `ansible-playbook` runtime
[[#5876](https://github.com/ansible/ansible-tower/issues/5876)]
* added support for assigning multiple cloud and network credential types on
`JobTemplates`. ``JobTemplates`` can prompt for "extra credentials" at
launch time in the same manner as promptable machine credentials
[[#5807](https://github.com/ansible/ansible-tower/issues/5807)]
[[#2913](https://github.com/ansible/ansible-tower/issues/2913)]
* custom inventory sources can now specify a ``Credential``; you
can store third-party credentials encrypted within Tower and use their
values from within your custom inventory script (by - for example - reading
an environment variable or a file's contents)
[[#5879](https://github.com/ansible/ansible-tower/issues/5879)]

5
docs/custom_credential_types.md
View File

@@ -36,6 +36,11 @@ Important Changes
Engine credential. You cannot, however, create a ``Job Template`` that uses
two OpenStack credentials.
* In the same manner as "promptable SSH credentials", ``Job Templates`` can now
be flagged with ``ask_extra_credentials_on_launch = true``. When this flag
is enabled, ``extra_credentials`` for a ``Job Template`` can be specified in
the launch payload.
* Custom inventory sources can now utilize a ``Credential``; you
can store third-party credentials encrypted within Tower and use their
values from within your custom inventory script (by - for example - reading