On Fri, Dec 24, 2010 at 15:37, William Van Hevelingen <wva...@gmail.com> wrote:
> Its helpful if you include error messages
There were no error messages, just incorrect behaviour, but it is a
fair request. :)
> but the answer is
> puppet resource host some.example.com ip=127.0.0.1
> host_aliases="['www.example.com','mail.example.com']"
Sorry, nope:
dan...@ea:~$ puppet resource host some.example.com target=${PWD}/demo
ip=127.0.0.1 host_aliases="['www.example.com','mail.example.com']"
notice: /Host[some.example.com]/ensure: created
host { 'some.example.com':
ip => '127.0.0.1',
host_aliases => ['['www.example.com','mail.example.com']'],
target => '/Users/daniel/demo',
ensure => 'present'
}
dan...@ea:~$ cat demo
# HEADER: This file was autogenerated at Fri Dec 24 15:49:25 +1100 2010
# HEADER: by puppet. While it can still be managed manually, it
# HEADER: is definitely not recommended.
127.0.0.1 some.example.com ['www.example.com','mail.example.com']
That would ... well, "not work" is a nice way to put it. Puppet just
did as asked, but broke my hosts file in the process. If I used that
live. :)
Regards,
Daniel
--
✣ Daniel Pittman ✉ dan...@rimspace.net ☎ +61 401 155 707
♽ made with 100 percent post-consumer electrons
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
