| 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
|
|
|
|
|
|
requirements.rb
|
|
|
|
monitor ssh keys
|
|
|
|
|
|
unique, to prevent unncessary regeneration of certificates.
|
|
|
|
|
|
|
|
services/webapp.production.json). requires latest platform.
|
|
|
|
|
|
surprises. in the future, i have some ideas for a better way.
|
|
https://leap.se/code/issues/3725)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
vagrant key)
|
|
|
|
provider.production.json)
|
|
|
|
|
|
|
|
options -- this should prevent ssh from trying all the keys in ~/.ssh. you might still get the error "Too many authentication failures" if you have a ton of keys activated in ~/.ssh/config
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
