leap deploy fails if leap.se is not available
if leap.se is offline, leap deploy fails:
~# leap deploy unstable = Updating submodule puppet/modules/apache = run git submodule update --init puppet/modules/apache 2>&1 - FAILED (exit 1) Submodule 'puppet/modules/apache' (https://leap.se/git/puppet_apache) registered for path 'puppet/modules/apache' Cloning into 'puppet/modules/apache'... fatal: unable to access 'https://leap.se/git/puppet_apache/': Failed to connect to leap.se port 443: Connection timed out Clone of 'https://leap.se/git/puppet_apache' into submodule path 'puppet/modules/apache' failed = bailing out
This might be harmful if an attacker wants to prevent updates on all installations at the same time :)
(from redmine: created on 2015-12-02)