support custom AWS.Config() instead of requiring parameters be manually mapped
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 79
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
The Dyno factory only supports a small subset of the available AWS configuration options because it plucks certain properties from the options hash and passes them into the AWS.DynamoDB constructor.
This is problematic for consumers wishing to have fine-grain control over the behavior of the AWS SDK.
Dyno should support using a custom AWS.Config instance to configure the AWS SDK.
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 in index.js at the Dyno factory around lines 35, 66, and 77, then review how options are currently selected for AWS.DynamoDB. Define how a supplied AWS.Config instance should be accepted while preserving the existing configuration path, and verify that Dyno passes the custom configuration to the AWS SDK.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, javascript
- Domain
- backend, database
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100