Open z3d1k opened 3 months ago
Welcome to LocalStack! Thanks for reporting your first issue and our team will be working towards fixing the issue for you or reach out for more background information. We recommend joining our Slack Community for real-time help and drop a message to LocalStack Pro Support if you are a Pro user! If you are willing to contribute towards fixing this issue, please have a look at our contributing guidelines and our contributing guide.
Is there an existing issue for this?
Current Behavior
When listing shards for Kinesis stream and specifying shard filter type as
AT_TRIM_HORIZON
, the response is the same as when shard filter type is set toFROM_TRIM_HORIZON
- contains all currently available shards, existing or created afterTRIM_HORIZON
.Expected Behavior
Request with shard filter type set to
AT_TRIM_HORIZON
should return only shards that were open atTRIM_HORIZON
as per documentation:Same sequence of commands when calling AWS produces the desired result:
How are you starting LocalStack?
With the
localstack
scriptSteps To Reproduce
How are you starting localstack (e.g.,
bin/localstack
command, arguments, ordocker-compose.yml
)Client commands (e.g., AWS SDK code snippet, or sequence of "awslocal" commands)
Environment
Anything else?
No response