From this example:
package { 'foo':
ensure => '1.0.0',
}
package { 'foo':
ensure => '1.0.1',
}
package { 'foo':
ensure => 'latest',
}
Which one wins? Since resources can be evaluated and applied in any
order (barring dependencies), you could end up in a situation where a
package gets flipped between different versions on subsequent runs of
the agent. It breaks the idea of being idempotent.
On 03/19/2015 02:55 AM, [email protected] wrote:
I've encountered the problem where 2 modules declare the identical
package.
I wonder why package { .. } doesn't check if the package is already
declared, and the redundant declaration can be ignored.
Will it be a nice improvement? If not, why not?
Thank you,
Tanin
--
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 [email protected]
<mailto:[email protected]>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/aeaf617d-aeb0-47f9-9997-69544489b8e7%40googlegroups.com
<https://groups.google.com/d/msgid/puppet-users/aeaf617d-aeb0-47f9-9997-69544489b8e7%40googlegroups.com?utm_medium=email&utm_source=footer>.
For more options, visit https://groups.google.com/d/optout.
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/puppet-users/550AD7E1.4030803%40alter3d.ca.
For more options, visit https://groups.google.com/d/optout.
