From: the-maldridge <the-maldridge@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: vault: update to 1.6.1
Date: Thu, 14 Jan 2021 08:50:36 +0100 [thread overview]
Message-ID: <20210114075036.tprdK8vGIt_MWE0qe-Js_Mq6EekxiKYzDjKk1_6_k-Q@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27851@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 885 bytes --]
There's a merged pull request on the void-packages repository
vault: update to 1.6.1
https://github.com/void-linux/void-packages/pull/27851
Description:
@the-maldridge
* Here are [the minor-version changes](https://github.com/hashicorp/vault/blob/master/CHANGELOG.md#160).
* For consistency's sake I matched `_git_commit` to `v1.6.1`'s hash.
Sanity check:
```
$ ./xbps-src pkg vault
<...>
$ xi vault
<...>
$ vault version
Vault v1.6.1 (6d2db3f033e02e70202bef9ec896360062b88b03) (cgo)
$ vault server -dev &> /dev/null &
[1] 9125
$ export VAULT_ADDR='http://127.0.0.1:8200'
$ vault secrets enable -path=kv kv
Success! Enabled the kv secrets engine at: kv/
$ vault kv put kv/foo foo=bar
Success! Data written to: kv/foo
$ vault kv get kv/foo
=== Data ===
Key Value
--- -----
foo bar
```
Lemme know if there're any more tests you'd like me to run.
prev parent reply other threads:[~2021-01-14 7:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 7:47 [PR PATCH] " Goorzhel
2021-01-12 7:48 ` the-maldridge
2021-01-12 8:02 ` Goorzhel
2021-01-12 8:19 ` Goorzhel
2021-01-12 8:23 ` Goorzhel
2021-01-13 2:45 ` Goorzhel
2021-01-13 2:50 ` ericonr
2021-01-13 3:30 ` [PR PATCH] [Updated] " Goorzhel
2021-01-13 3:45 ` the-maldridge
2021-01-13 7:14 ` ericonr
2021-01-13 7:20 ` Goorzhel
2021-01-13 7:21 ` [PR PATCH] [Updated] " Goorzhel
2021-01-13 7:21 ` Goorzhel
2021-01-13 7:28 ` Goorzhel
2021-01-13 11:31 ` q66
2021-01-13 11:41 ` the-maldridge
2021-01-13 17:03 ` [PR PATCH] [Updated] " Goorzhel
2021-01-14 7:33 ` Goorzhel
2021-01-14 7:50 ` the-maldridge [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210114075036.tprdK8vGIt_MWE0qe-Js_Mq6EekxiKYzDjKk1_6_k-Q@z \
--to=the-maldridge@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).