On Tuesday, March 17, 2015 at 10:46:05 PM UTC-5, Alex Harvey wrote: > > Can't you avoid this problem altogether by determining the PHP version in > your custom provider code? Then you wouldn't need a custom fact at all, > and in your manifest, have the custom type require the PHP package. > > Great insight! I didn't think to question whether the fact was required at all. If indeed it is used to determine *how* to apply the resource in question, as opposed to determining *what* to apply, then having the provider perform the version check is definitely the way to go. If it's in a gray area between "how" and "what", then choosing the "how" side with a possibility to override via resource parameter is probably best.
John -- 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/2f29eb22-edee-4300-bcfa-81d100c26f6d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
