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

Describe the solution you'd like

Current op command has a get item with --fields flag which makes it a lot simpler to extract values from details or section fields.

The output function can be used with this:

{{- output "op" "get" "item" "some-id" "--fields" "some-field" }}

But it might be nicer to have a built-in onepassworditemFields function (or something)

Great new metric last_state, thanks!

We now have a monitoring rule is in place to watch for failed sync. A sync was failing so I deleted the ExternalSecret. However, last_state does not forget and continues to report -1 on the ExternalSecret that no longer exists. It continues to report success on deleted objects as well.

Clearly this is bad and last_state should stop reporting ExternalSecre

Hi,
thank you for the library. It really improved the way I approach configuration files.
Finally I have types and proper sections.
What I am missing is schema: I would love to be able to enforce that some parameters are obligatory, their type and provide a description, also raise an exception if there is some unknown parameter is configured.
I think I could use something like marshmallow

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.