After much base64 decoding of Powershell commands the following will work:
raw:
C:\Temp\db_scripts\copy_db_file.ps1 "{{ system_db_default_location
}}/master.mdf" "{{ system_db_master_mdf_location }}/master.mdf"
I removed the PowerShell call at the beginning, unquoted the script path
and then removed the escaping slash \ before the quotation marks around the
arguments.
Hopefully this will help somebody!
On Wednesday, 20 January 2016 17:39:45 UTC+11, Rob White wrote:
>
> I've starting seeing the following problem since I upgraded to Ansible v2.0
>
> Here's the task:
>
> raw:
>
> PowerShell "C:\Temp\db_scripts\copy_db_file.ps1" \"{{
> system_db_default_location }}/master.mdf\" \"{{
> system_db_master_mdf_location }}/master.mdf\"
>
> It used to work fine in Ansible 1.9 but now I get a PowerShell error:
>
> "stderr": "The string is missing the terminator: \".\r\n +
> CategoryInfo : ParserError: (:) [], ParentContainsErrorRecordEx
> \r\n ception\r\n + FullyQualifiedErrorId :
> TerminatorExpectedAtEndOfString\r\n \r\n"
>
>
>
> This is obviously something to do with the way Ansible has changed how it
> handles escaped characters but I've tried a number of other different
> options for escaping my task and i can't get it to work.
>
>
> I appreciate any suggestions.
>
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/ae01a30a-6bcd-4f5c-a739-21d31c3d27d9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
