Ansible 2,7 "use_tty" fix

Per Issue #6453, Ansible@2.7 targetting Windows was throwing the following error when setup as the docs instruct:
"Requested option use_tty was not defined in configuration"

This is caused by something in Ansible silently discarding the whole `DOCUMENTATION` string configuration when it can't parse it. The changed line in this PR fixes that. :)
This commit is contained in:
John Jones 2019-04-02 21:17:08 -07:00 committed by GitHub
parent e4842b69b4
commit d0eb2609a8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 2 deletions

View File

@ -262,8 +262,7 @@ DOCUMENTATION = '''
connection: packer
short_description: ssh based connections for powershell via packer
description:
- This connection plugin allows ansible to communicate to the target packer
machines via ssh based connections for powershell.
- This connection plugin allows ansible to communicate to the target packer machines via ssh based connections for powershell.
author: Packer
version_added: na
options: