Keys can be listed and created with a key_bits parameter

LeSuisse · LeSuisse · commit 2231f30c3481 · 2018-02-20T23:23:59.000+01:00
With Vault 0.9.4 and the gRPC backend the key_bits can be specified
as an int as expected.
diff --git a/README.md b/README.md
@@ -62,7 +62,7 @@ This endpoint creates a new named GPG key.
 {
   "real_name": "John Doe",
   "email": "john.doe@example.com",
-  "key_bits": "4096"
+  "key_bits": 4096
 }
 ```
 
diff --git a/main.go b/main.go
@@ -17,10 +17,6 @@ func main() {
 	tlsConfig := apiClientMeta.GetTLSConfig()
 	tlsProviderFunc := pluginutil.VaultPluginTLSProvider(tlsConfig)
 
-	// Fail the version check, falling back to netRPC
-	// Workaround hashicorp/vault#3873
-	os.Unsetenv("VAULT_VERSION")
-
 	err := plugin.Serve(&plugin.ServeOpts{
 		BackendFactoryFunc: gpg.Factory,
 		TLSProviderFunc:    tlsProviderFunc,

Original file line number	Diff line number	Diff line change
`@@ -62,7 +62,7 @@ This endpoint creates a new named GPG key.`
`62`	`62`	`{`
`63`	`63`	`"real_name": "John Doe",`
`64`	`64`	`"email": "[email protected]",`
`65`		`- "key_bits": "4096"`
	`65`	`+ "key_bits": 4096`
`66`	`66`	`}`
`67`	`67`	```
`68`	`68`