Merge pull request #1 from numtide/flokli-patch-1

Update README.md
main
Jörg Thalheim 2 years ago committed by GitHub
commit f41b20f763
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -2,7 +2,7 @@
systemd-vaultd is a proxy between systemd and [vault systemd-vaultd is a proxy between systemd and [vault
agent](https://vaultproject.io). It provides a unix socket that can be used in agent](https://vaultproject.io). It provides a unix socket that can be used in
systemd services in the `LoadCredential` option and than waits for vault agent systemd services in the `LoadCredential` option and then waits for vault agent
to write these secrets at `/run/systemd-vaultd/<service_name>-<secret_name>`. to write these secrets at `/run/systemd-vaultd/<service_name>-<secret_name>`.
## Systemd's `LoadCredential` option ## Systemd's `LoadCredential` option
@ -34,7 +34,7 @@ ExecStart=/usr/bin/myservice.sh
LoadCredential=foobar:/run/systemd-vaultd/sock LoadCredential=foobar:/run/systemd-vaultd/sock
``` ```
vault agent is than expected to write secrets to `/run/systemd-vaultd/` vault agent is then expected to write secrets to `/run/systemd-vaultd/`
``` ```
template { template {
@ -44,7 +44,7 @@ template {
``` ```
When `myservice` is started, systemd will open a connection to `systemd-vaultd`'s socket. When `myservice` is started, systemd will open a connection to `systemd-vaultd`'s socket.
`systemd-vaultd` than either serve the secrets from `/run/systemd-vaultd/secrets/myservice.service-foo` `systemd-vaultd` then either serve the secrets from `/run/systemd-vaultd/secrets/myservice.service-foo`
or it waits with inotify on secret directory for vault agent to write the secret. or it waits with inotify on secret directory for vault agent to write the secret.
## Installation ## Installation

Loading…
Cancel
Save