Better visibility into vault integration status for clients
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 17k
- Forks
- 2.1k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 105
Description
Proposal
When a client attempts to configure vault, if the vault endpoint is unreachable, the request to vault will eventually time out. There is no logging around any potential miss configuration or any indication that the specified vault endpoint cannot be reached.
Use-cases
- Provide visibility into the clients vault status
- Easily determine if a client is configured to use vault
Attempted Solutions
Currently the only option is to see if nomad node status -verbose <node id> includes vault configuration options such as
vault.accessible = true
vault.cluster_id = 5eaffb28-e2aa-5b26-fadc-c4ed728cf223
vault.cluster_name = vault-cluster-f8bdef26
vault.version = 1.6.3
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the client Vault configuration and status path exposed by nomad node status -verbose <node id>, including the existing vault.accessible fields. Done means clients provide clear Vault configuration and reachability visibility, including useful indication when the configured endpoint cannot be reached.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100