vault-tool 0.0.0.1 → 0.0.0.3

raw patch · 3 files changed

+9/−7 lines, 3 filesdep ~base

Dependency ranges changed: base

Files

• README.md +1/−3
• src/Network/VaultTool.hs +6/−2
• vault-tool.cabal +2/−2

@@ -5,9 +5,7 @@  Tested with Vault versions: -    - Vault 0.6.0-    - Vault 0.6.1-    - Vault 0.6.2+- Vault 0.9.0  The tests for this library are in the package [vault-tool-server](../vault-tool-server/)

@@ -70,7 +70,9 @@ -- -- See 'vaultHealth' data VaultHealth = VaultHealth-    { _VaultHealth_Initialized :: Bool+    { _VaultHealth_Version :: Text+    , _VaultHealth_ServerTimeUtc :: Int+    , _VaultHealth_Initialized :: Bool     , _VaultHealth_Sealed :: Bool     , _VaultHealth_Standby :: Bool     }@@ -79,6 +81,8 @@ instance FromJSON VaultHealth where     parseJSON (Object v) =         VaultHealth <$>+             v .: "version" <*>+             v .: "server_time_utc" <*>              v .: "initialized" <*>              v .: "sealed" <*>              v .: "standby"@@ -93,7 +97,7 @@     manager <- newManager tlsManagerSettings     vaultRequestJSON manager "GET" (vaultUrl vaultAddress "/sys/health") [] (Nothing :: Maybe ()) expectedStatusCodes     where-    expectedStatusCodes = [200, 429, 500, 501, 503]+    expectedStatusCodes = [200, 429, 501, 503]  -- | Just initializes the 'VaultConnection' objects, does not actually make any -- contact with the vault server. (That is also the explanation why there is no

@@ -1,5 +1,5 @@ name:                vault-tool-version:             0.0.0.1+version:             0.0.0.3 synopsis:            Client library for HashiCorp's Vault tool (via HTTP API) description:         Client library for HashiCorp's Vault tool (via HTTP API) license:             MIT@@ -24,7 +24,7 @@   other-modules:       Network.VaultTool.Internal,                        Network.VaultTool.Types -  build-depends:       base >=4.8 && <4.10,+  build-depends:       base >=4.8 && <4.11,                        text,                        bytestring,                        http-client,