##### SUMMARY
Customer request: When typing the string to encrypt, it shows up as plain text. Since the string is being encrypted, it's safe to assume that it's sensitive (e.g. passwords) and should therefore be hidden. At the very least, maybe this could be a command line option. If it is hidden, I'd prefer to be forced to enter it twice to avoid mismatch. To mitigate this issue, I am currently using "stty -echo", but that shouldn't be necessary.

##### ISSUE TYPE
- Feature Idea

##### COMPONENT NAME
ansible-vault
new_vault_ids = []
            if encrypt_vault_id:
                new_vault_ids = default_vault_ids
            if context.CLIARGS['new_vault_id']:
                new_vault_ids.append(context.CLIARGS['new_vault_id'])
            new_vault_password_files = []
            if context.CLIARGS['new_vault_password_file']:
                new_vault_password_files.append(context.CLIARGS['new_vault_password_file'])
            new_vault_secrets = \
                self.setup_vault_secrets(loader,
                                         vault_ids=new_vault_ids,
                                         vault_password_files=new_vault_password_files,
                                         ask_vault_pass=context.CLIARGS['ask_vault_pass'],
                                         create_new_password=True)
            if not new_vault_secrets:
                raise AnsibleOptionsError("A new vault password is required to use Ansible's Vault rekey")
            
            
            new_encrypt_secret = match_encrypt_secret(new_vault_secrets,
                                                      encrypt_vault_id=encrypt_vault_id)
            self.new_encrypt_vault_id = new_encrypt_secret[0]
            self.new_encrypt_secret = new_encrypt_secret[1]
        loader.set_vault_secrets(vault_secrets)
        
        vault = VaultLib(vault_secrets)
        self.editor = VaultEditor(vault)
        context.CLIARGS['func']()
        
        os.umask(old_umask)
    def execute_encrypt(self):