Datastore dynamic
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 228
- Avg merge
- 5m
- Merged PRs (30d)
- 1
Description
Initial checklist
- I understand this is a feature request and questions should be posted in the Community Forum
- I searched issues and couldn’t find anything (or linked relevant results below)
Problem
Hi,
Unfortunately, an endpoint is currently attached to ‘a single datastore’, which poses a problem, as we cannot have S3s for a single endpoint.
In our case, all clients have a private S3, and only one endpoint on our server.
I've tried to find a solution by tinkering, but it seems impossible.
Solution
The problem would be solved if we could allocate an s3Client dynamically during the upload request, for example, using the ‘onIncomingRequest’ or ‘namingFunction’ method.
Alternatives
No alternative solutions
Contributor guide
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 reviewing how an endpoint is attached to a single datastore, then inspect the onIncomingRequest and namingFunction entry points mentioned in the issue. Done means an upload request can select an S3 client dynamically rather than being limited to one datastore, with the supported behavior documented and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, node.js, typescript
- Domain
- api, backend, cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100