mirror of https://github.com/zulip/zulip.git
7dc7962c04
The existing `except subprocess.CalledProcessError` only catches if there are syntax errors which prevent the `lastrun` file from being written; it does not handle if there are properly-defined resources which fail to evaluate (e.g. due to a missing dependency or file). Check the `failed` resource count, and exit 2 if there are any such resources. This will cause `zulip-puppet-apply --force --noop` (which is used as a pre-flight check during upgrades) to properly detect and signal on more types of invalid puppet configurations. In turn, this will cause `upgrade-zulip` to not attempt to power through upgrades it knows are destined to fail. |
||
---|---|---|
.. | ||
lib | ||
nagios | ||
setup | ||
README.md | ||
__init__.py | ||
get-django-setting | ||
log-search | ||
purge-old-deployments | ||
refresh-sharding-and-restart | ||
restart-server | ||
start-server | ||
stop-server | ||
upgrade-zulip | ||
upgrade-zulip-from-git | ||
zulip-puppet-apply |
README.md
This directory contains scripts that:
-
Generally do not require access to Django or the database (those are "management commands"), and thus are suitable to run operationally.
-
Are useful for managing a production deployment of Zulip (many are also used in a Zulip development environment, though development-only scripts live in
tools/
).
For more details, see https://zulip.readthedocs.io/en/latest/overview/directory-structure.html.