Skip to content

Allow for configurable backends for Bulkrax imports and exports #1203

Description

@maxkadel

Since import and export files can build up, which can have a significant financial impact, we should allow applications to choose which back end storage they want to use for these files.

Acceptance criteria

  • An application can configure where to store imports and exports (dealers choice on whether these should be configured together or separately)
  • An application could choose to store imports and exports to, for example, S3
  • Be non-breaking
    • Existing imports and exports continue to display correctly in the browser
    • Default storage behavior is current behavior

Implementation notes

Could use ActiveStorage or Valkyrie file uploaders, as well as tmp directories. @orangewolf recommends ActiveStorage

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions