summaryrefslogtreecommitdiff
path: root/manifests
AgeCommit message (Collapse)Author
2015-07-25Style fixesEwoud Kohl van Wijngaarden
2015-04-20uses include type class declarationChris Barker
previous behavior used class { 'stdlib::stages':} which isn't singleton and could cause duplication resource declaration on the stages class. Since many community modules work by calling 'include stdlib' we should make stdlib's include of stages singleton as well.
2011-08-18Docs: Update documentation of stdlib classesnfagerlund
This commit edits the puppetdoc text of the stdlib and stdlib::stages classes to remove redundancy and add additional information.
2011-05-26Move stages to after mainJeff McCune
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.
2011-05-24Add standard set of run stages.Jeff McCune
Many modules I'm working on need a standard but relatively granular location in the catalog. For example, any module that configures the packaging system should run "early" Add the following stages which have inter-dependencies in the top to bottom order listed: * setup * deploy * runtime * setup_infra * deploy_infra * main * setup_app * deploy_app
2011-05-24Initial commitJeff McCune