Jeff Mitchell

Not currently.

@mkozjak We have plans for an event system but it's orthogonal to your problem. Follow-up can happen there.

Not currently. We've been thinking through it conceptually. There is no hard roadmap commitment and no design docs.

Policy composition goes both ways. What you are thinking of as a solution to an inconvenient aspect of Vault's behavior is someone else's escalation of privilege.

My comment was regarding the CLI/API proposal discussed in the comments above.

> Even with Enterprise DR and replication, you wouldn't have a true backup as you can't back up the KMS keys. Enterprise DR can use a different key per cluster,...

The problem is that values for KVv2 live in a `data` map, not at a top-level. This is necessary for it to be able to provide extra functionality, as we...

So for what it's worth here's _one_ way to slice it, although there are other ways it can be done (or with other naming) https://github.com/jefferai/dns/commit/876d499e729fb7e1ca2eef7e438f4cf8ada09cec Basically I need access to...

For more explanation: some platforms (*cough*, Windows, *cough*) do not allow you to firewall anything on localhost so if you want to perform any introspection or security controls you have...

@talbright Another option would be to see if the upstream author will be willing to add collaborators onto the repo.