Can someone explain this to me? I thought I'd be able to change the title of a
nagios_host resource but leave name_var the same to effectively write two
nagios_host files to disk with the same content, but instead I'm triggering an
error in the resouce alias code. I didn't realise changing namevar was using
resource aliases under the hood?
Any ideas on how I could make this work?
[root@localhost ~]# cat test.pp
nagios_host { 'foo':
ensure => present,
host_name => 'foo',
address => 'foo',
target => '/tmp/foo',
}
nagios_host { 'foo_again':
ensure => present,
host_name => 'foo',
address => 'foo',
target => '/tmp/foo_again',
}
[root@localhost ~]#
[root@localhost ~]#
[root@localhost ~]# puppet apply test.pp
Notice: Compiled catalog for localhost in environment production in 0.10 seconds
Error: Cannot alias Nagios_host[foo_again] to ["foo"] at /root/test.pp:13;
resource ["Nagios_host", "foo"] already declared at /root/test.pp:6
--
Luke Bigum
Senior Systems Engineer
Information Systems
---
LMAX Exchange, Yellow Building, 1A Nicholas Road, London W11 4AN
http://www.LMAX.com/
Recognised by the most prestigious business and technology awards
2016 Best Trading & Execution, HFM US Technology Awards
2016, 2015, 2014, 2013 Best FX Trading Venue - ECN/MTF, WSL Institutional
Trading Awards
2015 Winner, Deloitte UK Technology Fast 50
2015, 2014, 2013, One of the UK's fastest growing technology firms, The Sunday
Times Tech Track 100
2015 Winner, Deloitte EMEA Technology Fast 500
2015, 2014, 2013 Best Margin Sector Platform, Profit & Loss Readers' Choice
Awards
---
FX and CFDs are leveraged products that can result in losses exceeding your
deposit. They are not suitable for everyone so please ensure you fully
understand the risks involved.
This message and its attachments are confidential, may not be disclosed or used
by any person other than the addressee and are intended only for the named
recipient(s). This message is not intended for any recipient(s) who based on
their nationality, place of business, domicile or for any other reason, is/are
subject to local laws or regulations which prohibit the provision of such
products and services. This message is subject to the following terms
(http://lmax.com/pdf/general-disclaimers.pdf), if you cannot access these,
please notify us by replying to this email and we will send you the terms. If
you are not the intended recipient, please notify the sender immediately and
delete any copies of this message.
LMAX Exchange is the trading name of LMAX Limited. LMAX Limited operates a
multilateral trading facility. LMAX Limited is authorised and regulated by the
Financial Conduct Authority (firm registration number 509778) and is a company
registered in England and Wales (number 6505809).
LMAX Hong Kong Limited is a wholly-owned subsidiary of LMAX Limited. LMAX Hong
Kong is licensed by the Securities and Futures Commission in Hong Kong to
conduct Type 3 (leveraged foreign exchange trading) regulated activity with CE
Number BDV088.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/1154755873.4737099.1469807604114.JavaMail.zimbra%40lmax.com.
For more options, visit https://groups.google.com/d/optout.
