| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
if files/custom-puppet/{manifests,modules} does not exist, it will be
created and files/custom-puppet/manifests/site.pp will be populated with
a comment and necessary tag to apply in the platform.
The site.pp must exist, if it does not, then the import in the
platform/manifest/site.pp will fail.
Any puppet resources put in custom-puppet/manifests/site.pp will be
executed, and any modules placed in custom-puppet/modules will be made
available through the --modulepath parameter to puppet.
This requires the associated platform changes (#6226)
|
|
|
|
|
|
unpin`. See `leap help env` for more information.
|
|
|
|
platform.version, platform.branch, and platform.commit
|
|
|
|
|
|
surprises. in the future, i have some ideas for a better way.
|
|
|
|
|
|
being updated.
|
|
/srv/leap/[puppet|bin], because doing so messes up the permissions of /srv/leap.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If a submodule had an update, it would show up as a + in the 'git submodule
status' output, and thus would not be automatically updated because we were only
looking for '-', so the regexp was changed to look for + as well as -
Additionally, add a 'git submodule sync' on every run in order to capture the
case where an upstream submodule URL was changed. This doesn't happen often, but
it can be quite painful when it does, and fortunately 'git submodule sync' is a
local (and thus, cheap) command.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
don't need to be embedded in hiera.yml. this is especially useful for binary files.
|
|
|
|
|
|
are required packages that are missing).
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
