From 11151af1dc8bfd39448c8d1e5c598d5864f75e82 Mon Sep 17 00:00:00 2001 From: Jeff Mitchell Date: Mon, 8 Feb 2016 11:52:04 -0500 Subject: [PATCH] Add change of exit code for status to upgrade page --- website/source/docs/install/upgrade-to-0.5.html.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/website/source/docs/install/upgrade-to-0.5.html.md b/website/source/docs/install/upgrade-to-0.5.html.md index 6fdc4ebfef..07de541f71 100644 --- a/website/source/docs/install/upgrade-to-0.5.html.md +++ b/website/source/docs/install/upgrade-to-0.5.html.md @@ -48,6 +48,11 @@ endpoint. Since the `default` policy contains `auth/token/renew-self` this makes it much more likely that the request will succeed rather than somewhat confusingly failing due to a lack of permissions on `auth/token/renew`. +## `status` CLI Command +The `status` CLI command now returns an exit code of `0` for an unsealed Vault +(as before), `2` for a sealed Vault, and `1` for an error. This keeps error +return codes consistent across commands. + ## Transit Upsertion Behavior Uses Capabilities Previously, attempting to encrypt with a key that did not exist would create a