minor doc fixes on win_template
This commit is contained in:
parent
0636f7207a
commit
2c8b765cf0
1 changed files with 8 additions and 13 deletions
|
@ -24,25 +24,20 @@ options:
|
|||
description:
|
||||
- Path of a Jinja2 formatted template on the local server. This can be a relative or absolute path.
|
||||
required: true
|
||||
default: null
|
||||
aliases: []
|
||||
dest:
|
||||
description:
|
||||
- Location to render the template to on the remote machine.
|
||||
required: true
|
||||
default: null
|
||||
notes:
|
||||
- "templates are loaded with C(trim_blocks=True)."
|
||||
- By default, windows line endings are not created in the generated file.
|
||||
- In order to ensure windows line endings are in the generated file,
|
||||
add the following header as the first line of your template:
|
||||
"#jinja2: newline_sequence:'\r\n'"
|
||||
and ensure each line of the template ends with \r\n
|
||||
- "In order to ensure windows line endings are in the generated file, add the following header
|
||||
as the first line of your template: #jinja2: newline_sequence:'\r\n' and ensure each line
|
||||
of the template ends with \r\n"
|
||||
- Beware fetching files from windows machines when creating templates
|
||||
because certain tools, such as Powershell ISE, and regedit's export facility
|
||||
add a Byte Order Mark as the first character of the file, which can cause tracebacks.
|
||||
- Use "od -cx" to examine your templates for Byte Order Marks.
|
||||
requirements: []
|
||||
author: "Jon Hawkesworth (@jhawkesworth)"
|
||||
'''
|
||||
|
||||
|
|
Loading…
Reference in a new issue