Pass namespace to the Vault client (#1660)

The namespace was plumbed all the way through the API but isn't actually
set on the client when it is created.

Fixes #1597
This commit is contained in:
Jeff Mitchell authored and GitHub committed 2021-11-03 14:52:11 -04:00
1 parent 4df3b40def
commit 03de1c4b21
2 files changed
+7

No files matched your search

+3
View File
@@ -22,6 +22,9 @@ Canonical reference for changes, improvements, and bugfixes for Boundary.
a missing mandated cipher suite of the HTTP/2 (`h2`) specification that could
result in no shared cipher suites between the Boundary API listener and those
clients. ([PR](https://github.com/hashicorp/boundary/pull/1637))
* vault: Fix credential store support when using Vault namespaces
([Issue](https://github.com/hashicorp/boundary/issues/1597),
[PR](https://github.com/hashicorp/boundary/pull/1660))
## 0.6.2 (2021/09/27)
+4
View File
@@ -79,6 +79,10 @@ func newClient(c *clientConfig) (*client, error) {
}
vClient.SetToken(string(c.Token))
if c.Namespace != "" {
vClient.SetNamespace(c.Namespace)
}
return &client{
cl: vClient,
token: c.Token,