localstack / localstack/localstack-extensions
Confusion on which services/requests should be proxied to real AWS and which should not
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 47
- Forks
- 19
- Avg merge
- 2h 2m
- Merged PRs (30d)
- 1
Description
- If I have
read_onlyset to true fordynamodb, and I have specified resources that I want proxied - what happens to a read request that comes in for a resource I haven't specified? Should it not get proxied out? Currently the behavior is that it does. - If I haven't configured any specific services to be proxied, will all requests then be proxied?
- How can I proxy just requests for specific dynamo tables? The following config proxies all requests regardless of which table. If I make a read request for
Table3it will succeed. It's not until I completely remove the dynamo configuration that it fails.
services:
dynamodb:
resources:
- .*TableOne
- .*TableTwo
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
Reproduce the behavior using the shown services.dynamodb.resources configuration and compare requests for TableOne, TableTwo, and Table3. Start by tracing how configured services and resource patterns determine whether DynamoDB requests are proxied; done means the behavior for unspecified resources, empty service configuration, and table-specific matching is documented or corrected and covered by verification.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100