Skip to content
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

Provide a per-storage init command #35

Open
nir0s opened this issue Oct 10, 2016 · 0 comments
Open

Provide a per-storage init command #35

nir0s opened this issue Oct 10, 2016 · 0 comments
Assignees
Milestone

Comments

@nir0s
Copy link
Owner

nir0s commented Oct 10, 2016

Both the Consul and Vault (and later Elasticsearch, etc..) storage backends can receive additional configuration options currently not exposed via the CLI. The API comfortably exposes those options.

Creating a command which will allow to initialize each specific storage will make configuring the storage easier:

ghost init consul --stash http://localhost:8500 --directory 'my_dir' --verify --client-cert 'my_cert' --auth user:password

An alternative could be to allow the user to pass any set of kwargs to the init command like so:

ghost init http://localhost:8500 --backend consul --storage-args directory=mydir;verify=true;client_cert=my_cert;auth=user:password
@nir0s nir0s self-assigned this Oct 25, 2016
@nir0s nir0s added this to the v0.8.0 milestone Mar 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant