Allow instances to configure their preferred storage service
Open
Nobody has claimed this yet.
- Dominant language
- Elixir
- Stars
- 296
- Forks
- 86
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 50
Description
We need to configure a storage service on lightning to enable every deployment to set up their preferred methods for storing exports. For this implementation, we will adopt Google Cloud Storage as default but eventually add AWS, Local Storage, and Azure.
- If the storage is not configured by providing the right API keys, the feature should be disabled
- Set up integration with Google Cloud Storage to allow reading and writing into storage buckets
- If storage bucket is not configured, the export feature is disabled
- Download URL should be a signed URL to ensure security
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating Lightning's export flow and deployment configuration, then identify where storage credentials, bucket access, and download URLs are handled. Done means Google Cloud Storage supports reading and writing exports, storage-dependent features are disabled when configuration is missing, and downloads use signed URLs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- elixir, google-cloud
- Domain
- backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100