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.

Sign up for GitHub

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

Jump to bottom

When instantiating a storage class using a bad endpoint, ghost should fail #75

Open
nir0s opened this issue Jan 19, 2017 · 2 comments
Open

When instantiating a storage class using a bad endpoint, ghost should fail #75

nir0s opened this issue Jan 19, 2017 · 2 comments
Labels
enhancement

Comments

@nir0s
Copy link
Owner

nir0s commented Jan 19, 2017

No description provided.

@nir0s
Copy link
Owner Author

nir0s commented Jan 20, 2017 •
edited
Loading

@EarthmanT, thinking about this again, I think failing on init (which also comes along #76), is smarter than failing on class instantiation.

WDYT?

@nir0s
Copy link
Owner Author

nir0s commented Mar 26, 2017

Currently, only the Consul and Vault backends need to be modified. Elasticsearch and any remote SQLAlchemy backend are already tested.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@nir0s