-
Notifications
You must be signed in to change notification settings - Fork 64
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
(Optionally) run _cluster_setup after installation #41
Comments
you might be able to do it with a post-install hook, but does this not happen as part of the |
I shuold ammend my suggestion to run all of the |
have a look at https://helm.sh/docs/topics/charts_hooks/ for automation |
Are you saying a PR to do this would be welcome on this project? Or you prefer to keep this up to the consumers of the helm chart to implement as they see fit? |
@flimzy PRs are always welcome 😃 |
Any chance of this PR being considered? Would love to have this feature in our couchdb setups. |
Would it be reasonable to create the
_users
database upon cluster initialization? If it doesn't make sense in all cases, would it be reasonable to do it optionally if a config value (createUsersDatabase = true
?) is set?If this is something we want, I'm happy to work on a PR.
I'm not sure of the best approach. One possibility would be to create a
Job
resource that effectively callscurl -X PUT http://.../_users
. There might be some cleaner way I haven't thought of. I'm eager to hear other suggestions, if this is deemed worth pursuing.The text was updated successfully, but these errors were encountered: