Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Wrap provider-specific exceptions into CloudBridge ones #84
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.