vault

Consul Template version

v0.25.1

Expected behavior

Consul-template supports logging to file. Consul-template can be started as a service on Windows, and the resultant messages can be inspected. Consul offers -log-file via stdarg and Nomad offers log_file in the config.

Actual behavior

Consul-template only supports Syslog and stdout/stderr logging mechanisms. Windows d

I wanted to suggest this because I just started using this thing to document my own charts: https://github.com/norwoodj/helm-docs

Its trivial to use, just install the tool, use its comment syntax in your Chart.yaml and values.yaml and your done! You can customize it, but so far I haven't needed to use my own templating for it, just let it read the chart.yaml and values.yaml. It has examples in

A better logo?

what do I want on a logo:

• Few colors (max 2 or 3)
• Good to use as an icon
• Identity (connects with config, settings, adjustment)

logos live here: https://github.com/rochacbruno/dynaconf/tree/master/docs/img (used by documentation builds)

Full logo on top of the docs and readme (I personally don't like this one)

![](https://github.com/rochacbruno/dynaconf/raw/mas

Is your feature request related to a problem? Please describe.
Vault has backends for AWS like dynamo and s3. However to use them you should provide credentials. AWS support 2 solutions to eliminate this. IAM roles for Service Accounts and Instance profile roles.
Due to some unknown reason vault requires more time to start when using dynamic creds than explicit definition keys in s3 block o

So there is currently an hvac.v1.Client.sys.list_mounted_secrets_engines() method.

However, for obvious reasons this will fail as it will attempt to list all mounted secrets engines (as it calls /v1/sys/mounts).

The web UI, however, shows what mounts the current token has access to.

While poking around the live API documentation the other day (`VAULT_BASE_URI/ui/vault/api-explorer

Currently pressing ctrl+c while scans are going on we get a big traceback.
It would be nice if we can handle that traceback and print something nice like Canceled by the user or something similar.

Read this to understand how to do it properly.