-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
FilesAdapter for Azure Blob Storage #545
Conversation
// If you had provided storage account name, then also provide storage access key | ||
// Host is optional, Azure will default to the default host | ||
// directAccess defaults to false. If set to true, the file URL will be the actual blob URL | ||
constructor( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would be more consistent with other adapters to only have one parameter options
@aneeshd16 that looks great, unit tests would be nice too, even if they fail as you don't want to provide your keys there :) we were also talking with @drew-gross about the future of those adapters and we both are in favour to remove them from the core repository, and reference them through dependencies. Moving to a dependency would also help for the testing as you'll be able to put encrypted keys in travis for the unit tests to run and check for failures. I'm working on a PR (#549) that will enable a simpler and more flexible adapter architecture. |
Thanks for the review! Yes, I'll add unit tests soon. Looking forward to the new design. |
@aneeshd16 updated the pull request. |
please rebase and add the according tests into https://github.com/ParsePlatform/parse-server/blob/master/spec/FilesController.spec.js |
Okay will do! |
Thx! |
Oh man, we just saw the pull request - @aneeshd16, this is awesome! We at Microsoft made felixrieseberg/parse-server-azure-storage, but it'd certainly be great to have some tests (and for this to be more integrated with the Parse-Server development). |
This is great! Tests are on the way. < 24hrs |
@aneeshd16 updated the pull request. |
Current coverage is
|
@flovilmart Added the |
@aneeshd16 updated the pull request. |
# The first commit's message is: Added FilesAdapter for Azure Blob Storage # This is the 2nd commit message: Updated Azure Blob Adapter to return Buffer instead of text # This is the 3rd commit message: Added tests for Azure Blob Storage Added an extra "mount" parameter in FilesControllerTestFactory
@aneeshd16 updated the pull request. |
@aneeshd16 updated the pull request. |
Is this getting merged into a new version soon? With this merged, I'm ready to go with a full Azure deployment :) Just curious what the status is.....thanks |
Yep, me too. Just tell me what needs to be done so that this can be merged! |
@aneeshd16 updated the pull request. |
@onsol: In the meantime, we at Microsoft made an adapter you can use today.
|
@felixrieseberg |
Like #971 I'd really like to see this become its own module on npm, instead of being included in the core server. It's easier to test and maintain that way. For example: https://www.npmjs.com/package/parse-server-sendgrid-adapter |
...and @aneeshd16, we at Microsoft would love contributions over at https://www.npmjs.com/package/parse-server-azure ❤️! |
Closing as we pimped the adapter tests and moved all adapters to external packaged |
This is a FilesAdapter for uploading, accessing and deleting files on Azure Blob Storage.
It is very similar to how the S3 adapter works.
Use the
AzureBlobStorageAdapter
as thefilesAdapter
when initializing parse-server.or with more options:
IMO, this addition is needed since parse-server already supports direct deployment to Azure.
This is my first PR at a major repo, I am open to feedback and suggestions! Thanks!