-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Add Azure Blob Storage as a storage engine for attachments #255
Conversation
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
I have tested that the |
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.
Looks good 👍 Just couple of small details to staighten out
plugins/qeta-backend/src/service/upload/attachmentStorageEngine.ts
Outdated
Show resolved
Hide resolved
Also some lint issues that need fixing. And could you update the docs/config.md as well, thanks! |
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
@drodil I think the lint issues are fixed now and I've updated the docs with the new configuration values. |
Signed-off-by: Jonathan Mezach <[email protected]>
Signed-off-by: Jonathan Mezach <[email protected]>
Looking good, going to merge and publish a new version! |
This refactors the way the attachments endpoint interacts with storage engines by introducing an
AttachmentStorageEngine
interface. It then implements that interface for all existing storage engine types (database, filesystem, s3) and adds a new implementation for storing attachments in Azure Blob Storage.Fixes #136
Signed-off-by: Jonathan Mezach [email protected]