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

Added support for Azure Storage #564

Merged
merged 36 commits into from
Mar 23, 2021

Conversation

kedarghule
Copy link
Collaborator

This PR provides initial support for Azure Storage resources. It populates resources like Azure Storage Account, Queue Service and Queues, Table Service and Tables, File Service and File Shares, and Blob Service and Blob Containers in the graph DB.

mpurusottamc and others added 30 commits December 5, 2020 07:47
# Please enter a commit message to explain why this merge is necessary,
# especially if it merges an updated upstream into a topic branch.
#
# Lines starting with '#' will be ignored, and an empty message aborts
# the commit.
storage_account['resourceGroup'], storage_account['name'],
).as_dict()['value']

except HttpResponseError as e:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just like in #563 , lets catch some specific errors.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ramonpetgrave64 Done! :)

Copy link
Contributor

@ramonpetgrave64 ramonpetgrave64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non blocking changes requested.

@kedarghule
Copy link
Collaborator Author

@ramonpetgrave64 Completed the requested changes and updated code in the branch! :)

except ResourceNotFoundError as e:
logger.warning(f"Storage Account not found error - {e}")
return []
except HttpResponseError as e:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I feel we should raise here. If you get the ClientAuthenticationError and ResourceNotFoundError exceptions upon not having proper permissions, then that's fine, we should continue the sync, otherwise, the other failure cases could indicate an incomplete sync.

Copy link
Contributor

@ramonpetgrave64 ramonpetgrave64 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One comment on the Exceptions, but it looks good. Do feel free to address it in a future CR!

@ramonpetgrave64 ramonpetgrave64 merged commit ce2ab53 into lyft:master Mar 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants