I am noticing sometimes I have to do 2 puppet runs to get all dependencies to fully satisfy and for my system to configure itself at boot time. Most of my environment is completely stateless so its important that everything gets configured at runtime (I am currently doing puppet --test at boot up 2x now).
For example I have a yum module that sets yum configs up, but obviously I have other modules that depend on the installation of that yum module in order to use it to install rpms. How do some people deal with ordering of modules to make sure things get run first and foremost? I have read in previous threads of people have dependency issues and I am curious on potential solutions to get around it or to properly architect puppet to "do the right thing". -Chris -- 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.
