vault/website/source/docs/secrets
Jeff Mitchell 7479621705 Don't check parsability of a ttl key on write.
On read we already ignore bad values, so we shouldn't be restricting
this on write; doing so alters expected data-in-data-out behavior. In
addition, don't issue a warning if a given `ttl` value can't be parsed,
as this can quickly get annoying if it's on purpose.

The documentation has been updated/clarified to make it clear that this
is optional behavior that doesn't affect the status of the key as POD
and the `lease_duration` returned will otherwise default to the
system/mount defaults.

Fixes #1505
2016-06-08 20:14:36 -04:00
..
aws Adds sts:AssumeRole support to the AWS secret backend 2016-05-05 23:32:41 -04:00
cassandra Cassandra: 2016-02-01 10:27:26 -05:00
consul Minor documentation change 2016-03-09 14:50:23 +00:00
cubbyhole Add cubbyhole wrapping documentation 2016-05-19 13:33:51 -04:00
generic Don't check parsability of a ttl key on write. 2016-06-08 20:14:36 -04:00
mssql Docs updates 2016-03-10 21:15:25 -05:00
mysql Revert "Change mysql connection to match new" 2016-03-23 15:18:09 -04:00
pki url fix 2016-06-08 14:53:33 -04:00
postgresql postgres: connection_url fix 2016-02-22 11:22:49 -05:00
rabbitmq Update rabbitmq lease docs 2016-05-20 23:28:41 -07:00
ssh Provide option to disable host key checking 2016-06-01 11:08:24 -04:00
transit Merge pull request #1293 from gliptak/patch-2 2016-04-05 09:38:00 -04:00
custom.html.md website: add a couple more secret backend sections 2015-04-13 20:42:07 -07:00
index.html.md Use HTTPS + www where appropriate 2016-01-14 13:42:47 -05:00