Single Upload Source

Open
  • Is something wrong?
#46 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
javascript
Domain
api, backend, frontend

Research direction

Start by locating the obtain task and the UploadSources API, then trace the existing HTTP/S3 source-entry and source-selection flows. Implement the four listed actions: unified S3 and HTTP entries, a Selection-based source tab, and obtain support for Source IDs with automatic secret retrieval. Done means each checklist item works together for a single upload source.

Written by the indexing model from the issue text.

Description

Context

At the moment we have the ability to source a single upload from HTTP/S3 via the obtain task but it will only take raw values. We should also support selecting a source from the UploadSources API.

Actions
  • Unified component for S3 Source Entry
  • Unified component for HTTP Source Entry
  • Use Selection comonent for new Source selection tab
  • Support Source ID in obtain API and automatically retrieve secrets
Dominant language
JavaScript
Stars
7
Forks
1
No merged PRs in 30d

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from developmentseed/raster-uploader

All issues in developmentseed/raster-uploader

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.