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

Wrap provider-specific exceptions into CloudBridge ones #84

Open
afgane opened this Issue Sep 25, 2017 · 0 comments

Comments

Projects
None yet
2 participants
@afgane
Contributor

afgane commented Sep 25, 2017

While CloudBridge provides great abstraction from manipulating resources from multiple cloud providers through a single interface and shields the developer from discrepancies, this is not the case with exceptions. CloudBridge has minimal custom exceptions and when it raises an exception that originated on the provider side, it will just raise the original exception (e.g., https://github.com/gvlproject/cloudbridge/blob/master/cloudbridge/cloud/providers/aws/resources.py#L592). This requires the application to handle possibly different exceptions when deployed on different providers and hence breaks the goal of CloudBridge.

We should create a set of CloudBridge-specific exceptions and consistently raise those instead of the provider-specific ones.

@nuwang nuwang added this to the release 1.0.0 milestone Oct 1, 2017

@nuwang nuwang added the backlog label Oct 4, 2017

@afgane afgane modified the milestones: release 1.0.0, release 2.0.0 Feb 7, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment