summaryrefslogtreecommitdiff
path: root/lib/puppet/parser
diff options
context:
space:
mode:
authorJeff McCune <jeff@puppetlabs.com>2011-05-26 10:21:42 -0700
committerJeff McCune <jeff@puppetlabs.com>2011-05-26 10:21:42 -0700
commit6e9e838a0e9abdf66e3a14bc17e35771bb453966 (patch)
tree442108cd6ad323621aa5d5221966316def1e6a8f /lib/puppet/parser
parent46533ae4281bb58065a8f068c1334e5525deca1f (diff)
downloadpuppet-stdlib-6e9e838a0e9abdf66e3a14bc17e35771bb453966.tar.gz
puppet-stdlib-6e9e838a0e9abdf66e3a14bc17e35771bb453966.tar.bz2
Move stages to after main
Working with the stages in stdlib, I quickly ran into an issue where most of the stages were before the main stage. This made it difficult to declare any resources in a traditional "include" style class while hiding the end user from the stages being associated with other module classes. For example, in class mcollective, a package would be declared in main. However, if mcollective declared class mcollective::service in stage infra_deploy and this was before main, there would be a dependency loop between the package and the service. There appears to be a convention around "chain your stages after main" to avoid the need to create relatively empty shell classes.
Diffstat (limited to 'lib/puppet/parser')
0 files changed, 0 insertions, 0 deletions