[chef] Re: Re: Re: RE: Re: RE: RE: Newlines in templates

[Tensibai < >]

 

FWIW:

I think the file format and encoding is the responsability of the cookbook/template writer.

There's plenty of editors allowing to set the file encoding and line endings the way you wish.

I think about gvim and notepad++ for thoose I actually use for this purpose.

At least it must be an option as magically converting a file at rendering could become confusing.

I think about rendering config files on a server to push them toward a switch later, you may wish to keep the encoding of the file even if it is not the server base encoding.

 

Tensibai

 

Le 2013-11-07 04:40, Daniel Condomitti a écrit :

Could it be done at the time that the template is actually parsed and written to disk based on the platform type?

 

On Wednesday, November 6, 2013 at 7:02 PM, Julian C. Dunn wrote:

On Wed, Nov 6, 2013 at 9:03 AM, THARP, JOSHUA L < "> > wrote:

I am using Git, and with a little work (and a global setting that affects

all repositories) I can have it change the newlines. However, the question

remains if it is possible for Chef to do newline conversions. If I’m editing

on a Windows PC, and I upload my cookbook – targeting a *nix platform – the

cookbook is going to have the wrong line endings, and many Linux

configuration files as well as shell interpreters are sensitive to the line

endings. I would think mine is a fairly common scenario.

 

Joshua,

 

While that's true, there's no sensible default that Chef could take.

What if you're managing a mixed Linux/Windows infrastructure with

Chef, and some of the templates need Windows-format line-endings and

others need Unix-format ones?

 

- Julian

 

--

[ Julian C. Dunn < "> > * Sorry, I'm ]

[ WWW: http://www.aquezada.com/staff/julian * only Web 1.0 ]

[ gopher://sdf.org/1/users/keymaker/ * compliant! ]

[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9 ]