Afternoon all, I've just hit an issue with my Puppet-Glassfish module, where I'm using Type param validation to check for file existence on the client - typically on files that are also defined earlier in the catalogue, but have not yet been applied to the client. An example is [1], with the file it's validating being created in [2].
However on the first run, the validation is rightly blowing out due to the file not existing - but it would by the time the resource was called if the puppet run proceeded... Is there a way of handling this validation dependency scenario in a more Puppet friendly method? As I'd like to retain the validation logic if possible, just to allow for more robust error handling... Cheers Gavin [1] https://github.com/fatmcgav/fatmcgav-glassfish/blob/develop/lib/puppet/type/cluster.rb#L107-L111 [2] https://github.com/fatmcgav/fatmcgav-glassfish/blob/develop/manifests/init.pp#L155-L162 -- 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/ee7d86bb-60f2-4ff0-aa7a-af15c9edeb2e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
