-
Notifications
You must be signed in to change notification settings - Fork 23.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
{{ "test" | regex_replace('^(.).*', '\\1') }} produces a literal '\1' in v2, when used in a standalone template #12198
Comments
Some points about the trailing newline bit:
|
Fix for one half of hte bug reported in #12198
@mgedmin Thanks for continuing to find problems and make quality bug reports! There were a few changes in this past week that could affect a lot of code so continue to let us know if you find stuff and we'll either fix it or decide that it's a change of behaviour that we want in v2. Closing This TicketHi! We believe recent commits (likely detailed above) should resolve this question or problem for you. This will also be included in the next major release. If you continue seeing any problems related to this issue, or if you have any further questions, please let us know by stopping by one of the two mailing lists, as appropriate:
Because this project is very active, we're unlikely to see comments made on closed tickets, but the mailing list is a great way to ask questions, or post if you don't think this particular Thank you! |
Issue Type: Bug Report
Ansible Version:
Ansible Configuration: none whatsoever
Environment: Ubuntu 15.04
Summary:
Commit 7f5080f introduced a regression: now backslashes in standalone template files are doubled, breaking them.
Steps To Reproduce:
Expected Results:
(This is what expect, and also what I get with Ansible 1.9.2.)
also note that the file ought to have a trailing newline, since there was one in the source template:
Actual Results:
also note that the file lacks a trailing newline:
The text was updated successfully, but these errors were encountered: