Clarify caching of exec auth tokens (#7881)

* Clarify caching of exec auth tokens * Update the wording
2018-03-28 11:41:04 -07:00
parent 407518e5fd
commit e5dac76f5d
1 changed files with 2 additions and 1 deletions
@@ -828,7 +828,8 @@ Kubernetes API.

 Optionally, this output can include the expiry of the token formatted as a RFC3339 timestamp.
 If an expiry is omitted, the bearer token is cached until the server responds with a 401 HTTP
-status code.
+status code. Note that this caching is only for the duration of process and therefore the plugin 
+is triggered each time the tool using the plugin is invoked.

 ```json
 {