control-repo-template/site-modules/role/manifests, branch productionpuppetlabs/control-repo extended with not-so-core stuffhttps://git.pfeiffer.tech/control-repo-template/atom?h=production2022-09-16T18:08:02ZMoved the roles and profile comments to the top2022-09-16T18:08:02ZAndrew Jonesandrew.jones@puppet.com2022-09-16T18:08:02Zurn:sha1:bd6640ef12c79f7bcbe426e724d60a4010d332d3Revert "add db2_server role and profile"2019-12-03T19:35:22ZIristyleIristyle@github2019-12-03T19:16:31Zurn:sha1:c52c39d245c050289e11aefb81588a337a5c4120
This reverts commit 58103e4ef4478f7c997c769a7111ca48cdf269eb.
add db2_server role and profile2019-11-29T22:49:21ZJesse Reynoldsjesse@va.com.au2019-11-29T22:49:21Zurn:sha1:58103e4ef4478f7c997c769a7111ca48cdf269ebRename site directory to site-modules2019-02-01T00:58:13ZNick Walkernick.walker@puppetlabs.com2019-02-01T00:58:13Zurn:sha1:ead7f3c706657bbfae37ff40c8f919fb57c8a841
Prior to this commit, we placed modules local to a users installation
in the `site` directory. This was just a convention and the name
`site` doesn't clearly convey what it is for.
After this commit, we place modules local to a users installation in
the `site-modules` directory. This makes it more clear to users
that this is a directory that modules go i. When users start
with bolt they won't even know what a control-repo is and
renaming site to site-modules gives them a better idea of why
they should put their modules with tasks in them. Also see:
https://tickets.puppetlabs.com/browse/BOLT-1108