I have only recently started using modules off the forge and running a
recent version of Puppet (the majority of our network is still utilising
0.25.4). I spent a significant amount of time ensuring that dependencies
in our existing Puppet implementation result in a single Puppet run will
always succeed with the intended config applied to a node.
When making use of puppetlabs-apt I notice that there is nothing included
in that module that would make the Exec['apt_update'] run before other
package resources in my catalogue. My thought would be to add something
like this to update.pp:
Exec['apt_update'] -> Package <| title != "python-software-properties" and title != "software-properties-common" |>
I have also tried using the tag metaparameter ( tag != "apt" ) but then
ended up with a dependency cycle.
Does anyone have an opinion as to why this is a terrible idea? I ask
because I have submitted a pull request for the change prior to reading the
very informative page about contributing to puppetlabs modules and would
value any community feedback on my approach.
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@example.com.
To post to this group, send email to firstname.lastname@example.org.
Visit this group at http://groups.google.com/group/puppet-users.
For more options, visit https://groups.google.com/groups/opt_out.