On Tue, Feb 19, 2013 at 11:10 PM, Andrew Parker <[email protected]> wrote:
> > > On Feb 20, 2013, at 6:57 AM, Adrien Thebo <[email protected]> wrote: > > One clarification - this file is a configuration file but it's going to be > static, and specifically non-editable by the user. /usr being mounted as > read-only in this case would be fine. Effectively we're vendoring a static > file that should not change. Since it's going to be a static file, > /etc/puppet wouldn't be the best location because we're relying on it being > static and if it's in /etc/puppet it might get changed, which could break > things. > > > How about the provider just writes it out as a temp file when it needs it? > If it is static, should never be edited, and is needed for the provider to > execute correctly, then I can see just keeping it the code and writing it > out when needed. Also, I believe it was not a very large file, so it won't > bloat the code. > That's an approach that I hadn't considered. By having a heredoc in the code and then writing out something with Tempfile? -- Adrien Thebo | Puppet Labs -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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]. Visit this group at http://groups.google.com/group/puppet-dev?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
