Parse password field from dialog and decrypt before job launch

[bzwei]

https://bugzilla.redhat.com/show_bug.cgi?id=1438923

A password text field from service dialog will appear in the options field with the format
password::dialog_param_field_name: v2:{encrypted_word}

At option parsing the prefix will be removed, only field_name remains. The value remains encrypted.

An extra var can be set by three means in the following priority

1. Through automat code. The value can be either plain or encrypted. Encryption is recommended for password.
2. Through service dialog. The value from a password text box is always encrypted.
3. Through service item design time. The value is always plain. A future enhancement can be created to encrypt selected vars.

Before the job launching time we attempt to decrypt all values. A plain text can pass decryption with no problem.

[bzwei]

@miq-bot add_label bug, providers/ansible_tower, services, fine/yes
@miq-bot assign @gmcculloug

[miq-bot]

Checked commit bzwei@b206694 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks good. 🍰

[mkanoor]

@bzwei
Since every extra var defined by the user is going to be added via our Dialogs, can they set the type to be Password. And when we decide to launch the playbook we can figure out that the field is encrypted by fetching the dialog_field that corresponds to the extra var. This will shift the onus on the end user to decide which fields (extra vars) are encrypted fields.

[bzwei]

@mkanoor yes. It is a proposed enhancement after the initial release. I will create a pivotal story.

[simaishi]

Fine backport details:

$ git log -1
commit fee3b18e8d151ee2bd6dd9dd8eefa54614ac0cf7
Author: Greg McCullough <[email protected]>
Date:   Thu Apr 6 10:19:04 2017 -0400

    Merge pull request #14636 from bzwei/playbook_password_decrypt
    
    Parse password field from dialog and decrypt before job launch
    (cherry picked from commit 9bb8653267137d5cf03c5d36aeea17e8c9236f75)
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1439938