mirror of
https://github.com/hashicorp/vault.git
synced 2025-08-16 19:47:02 +02:00
ac784f400d
When configuring DynamoDB, the read and write capacities configured only have any effect if the table does not exist. As per the comment in the code [1], the configuration of an existing table is never modified. This was not previously reflected in the documentation - this commit rectifies that. [1]: https://github.com/hashicorp/vault/blob/master/physical/dynamodb/dynamodb.go#L743-L745 |
||
|---|---|---|
| .. | ||
| alicloudoss.html.md | ||
| azure.html.md | ||
| cassandra.html.md | ||
| cockroachdb.html.md | ||
| consul.html.md | ||
| couchdb.html.md | ||
| dynamodb.html.md | ||
| etcd.html.md | ||
| filesystem.html.md | ||
| foundationdb.html.md | ||
| google-cloud-spanner.html.md | ||
| google-cloud-storage.html.md | ||
| in-memory.html.md | ||
| index.html.md | ||
| manta.html.md | ||
| mssql.html.md | ||
| mysql.html.md | ||
| postgresql.html.md | ||
| s3.html.md | ||
| swift.html.md | ||
| zookeeper.html.md | ||