Skip to content

API Address Configuration #34

@micchickenburger

Description

@micchickenburger
May 15 21:51:01 RHSSRV01 vault[1417]: ==> Vault server configuration:
May 15 21:51:01 RHSSRV01 vault[1417]:                      Cgo: disabled
May 15 21:51:01 RHSSRV01 vault[1417]:               Listener 1: tcp (addr: "127.0.0.1:8200", cluster address: "127.0.0.1:8201", max_request_duration: "1m30s", max_request_size: "33554432", tls: "disabled")
May 15 21:51:01 RHSSRV01 vault[1417]:                Log Level: info
May 15 21:51:01 RHSSRV01 vault[1417]:                    Mlock: supported: true, enabled: true
May 15 21:51:01 RHSSRV01 vault[1417]:            Recovery Mode: false
May 15 21:51:01 RHSSRV01 vault[1417]:                  Storage: file
May 15 21:51:01 RHSSRV01 vault[1417]:                  Version: Vault v1.4.1
May 15 21:51:01 RHSSRV01 vault[1417]: ==> Vault server started! Log data will stream in below:
May 15 21:51:01 RHSSRV01 vault[1417]: 2020-05-15T21:50:59.505Z [INFO]  proxy environment: http_proxy= https_proxy= no_proxy=
May 15 21:51:01 RHSSRV01 vault[1417]: 2020-05-15T21:50:59.520Z [WARN]  no `api_addr` value specified in config or in VAULT_API_ADDR; falling back to detection if possible, but this value should be manually set

Setting api_addr seems to be best practice and could help cleanup the ansible vault configuration, which uses an environment variable before each command; that approach could be unnecessary with this simple change.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions