minor doc fixes on win_template

This commit is contained in:
Brian Coca 2015-06-11 11:35:49 -04:00 committed by Matt Clay
parent 4cb7df2631
commit f66ed3a85e

View file

@ -24,25 +24,20 @@ options:
description: description:
- Path of a Jinja2 formatted template on the local server. This can be a relative or absolute path. - Path of a Jinja2 formatted template on the local server. This can be a relative or absolute path.
required: true required: true
default: null
aliases: []
dest: dest:
description: description:
- Location to render the template to on the remote machine. - Location to render the template to on the remote machine.
required: true required: true
default: null
notes: notes:
- "templates are loaded with C(trim_blocks=True)." - "templates are loaded with C(trim_blocks=True)."
- By default, windows line endings are not created in the generated file. - By default, windows line endings are not created in the generated file.
- In order to ensure windows line endings are in the generated file, - "In order to ensure windows line endings are in the generated file, add the following header
add the following header as the first line of your template: as the first line of your template: #jinja2: newline_sequence:'\r\n' and ensure each line
"#jinja2: newline_sequence:'\r\n'" of the template ends with \r\n"
and ensure each line of the template ends with \r\n
- Beware fetching files from windows machines when creating templates - Beware fetching files from windows machines when creating templates
because certain tools, such as Powershell ISE, and regedit's export facility 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. 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. - Use "od -cx" to examine your templates for Byte Order Marks.
requirements: []
author: "Jon Hawkesworth (@jhawkesworth)" author: "Jon Hawkesworth (@jhawkesworth)"
''' '''