Merge pull request #1332 from hashicorp/fix-revocation-output

Clarify output of idempotent calls

command/delete.go

@@ -41,7 +41,7 @@ func (c *DeleteCommand) Run(args []string) int {
 		return 1
 	}
 
-	c.Ui.Output(fmt.Sprintf("Success! Deleted '%s' if it existed", path))
+	c.Ui.Output(fmt.Sprintf("Success! Deleted '%s' if it existed.", path))
 	return 0
 }
 

command/revoke.go

@@ -56,7 +56,7 @@ func (c *RevokeCommand) Run(args []string) int {
 		return 1
 	}
 
-	c.Ui.Output(fmt.Sprintf("Key revoked with ID '%s'.", leaseId))
+	c.Ui.Output(fmt.Sprintf("Success! Revoked the secret with ID '%s', if it existed.", leaseId))
 	return 0
 }
 

command/token_revoke.go

@@ -65,7 +65,7 @@ func (c *TokenRevokeCommand) Run(args []string) int {
 		return 2
 	}
 
-	c.Ui.Output("Revocation successful.")
+	c.Ui.Output("Success! Token revoked if it existed.")
 	return 0
 }
 

website/source/intro/getting-started/authentication.html.md

@@ -58,7 +58,7 @@ After a token is created, you can revoke it with `vault token-revoke`:
 
 ```
 $ vault token-revoke c2c2fbd5-2893-b385-6fa5-30050439f698
-Revocation successful.
+Success! Token revoked if it existed.
 ```
 
 In a previous section, we use the `vault revoke` command. This command

website/source/intro/getting-started/dynamic-secrets.html.md

@@ -148,7 +148,7 @@ outputted from `vault read` when you ran it:
 
 ```
 $ vault revoke aws/creds/deploy/0d042c53-aa8a-7ce7-9dfd-310351c465e5
-Key revoked with ID 'aws/creds/deploy/0d042c53-aa8a-7ce7-9dfd-310351c465e5'.
+Success! Revoked the secret with ID 'aws/creds/deploy/0d042c53-aa8a-7ce7-9dfd-310351c465e5', if it existed.
 ```
 
 Done! If you look at your AWS account, you'll notice that no IAM users

website/source/intro/getting-started/first-secret.html.md

@@ -110,7 +110,7 @@ and delete it. We can do this with `vault delete`:
 
 ```
 $ vault delete secret/hello
-Success! Deleted 'secret/hello' if it existed
+Success! Deleted 'secret/hello' if it existed.
 ```
 
 ## Next