hashicorp / hashicorp/vault-helm
Create Secrets Engines and Auth Methods as part of installation process
- Dominant language
- Shell
- Stars
- 1.3k
- Forks
- 898
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 1
Description
**Is your feature request related to a problem? Please describe.**
Secrets Engines and Auth Methods as two step process once the installation is complete and has to be repeated every time a new install happens.
**Describe the solution you'd like**
I would like an option to specify oauth methods and secrets engine in helm chart values.yaml file that creates all resources as part of installation process.
**Describe alternatives you've considered**
Create a downstream TF project that runs after vault install creating all resources.
**Additional context**
NA
Contributor guide
Research direction
Start by reviewing the Helm chart and its values.yaml configuration, then trace how Vault installation completes before Secrets Engines and Auth Methods are created. Define the values needed for both resource types and verify that a fresh chart installation creates the requested resources without a downstream Terraform project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, yaml
- Domain
- devops, infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100