-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename unsealer.image to bankVaults.image #29
Comments
This should be backwards compatible like: bank-vaults/vault-operator@203082c |
Yes, it should. |
I can help with this. 👍 |
Appreciate it, thank you! |
@sagikazarmark Should this be implemented only for https://github.com/bank-vaults/vault-helm-chart/blob/main/vault/values.yaml#L250-L254 or for the entire |
Good question... I'd say it would be ideal if we could have a common block for everything that's shared between the unsealer and the configurer, but I can see why that could prove challenging. Maybe we could use templating to filter the relevant keys from the unsealer section and recursively merge it with a new bankVaults section. I think that should be possible using template functions. |
Having an issue with creating a template for |
Hi @tanmay-pnaik, thanks for the interest, do you still need help with this? I can assist you and help out with setting everything up. |
@ramizpolic That would be helpful. I'll raise a PR with my current changes and maybe we could then take it forward? |
Sounds good, whenever you are ready @tanmay-pnaik |
Thank you for your contribution! This issue has been automatically marked as |
Currently both the configurer and unsealer use the unsealer image config.
Rename it to bankVaults so that naming makes more sense.
The text was updated successfully, but these errors were encountered: