You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Quotes used in KINESIS_INITIALIZE_STREAMS will cause a parsing error. This is new behavior which perhaps was triggered by one of the underlying component upgrades.
To Reproduce
Steps to reproduce the behavior:
Set your variable using a quoted string like: KINESIS_INITIALIZE_STREAMS="audit-stream:1:us-east-1"
Start localstack
See error:
INFO:localstack.services.kinesis.kinesis_mock_server: kinesis.mock.InvalidArgumentException: Stream Name '"audit_stream' contains invalid characters
Expected behavior
The surrounding quote characters in environment variables should be ignored.
Additional context
This worked with a 3 month old localstack image, and only broke recently, potentially in conjunction with the requirement for the region to be included in the stream name (that was not required in the previous image either)
The text was updated successfully, but these errors were encountered:
Of course. It's just unexpected behavior for environment variables. Perhaps an oddity of docker-compose, since the shell would typically remove those quotes when parsing the set command.
I'm not entirely sure to be honest. Might also be something that changed in Localstack rather than here. I haven't pushed a release of kinesis-mock since April of this year.
Describe the bug
Quotes used in KINESIS_INITIALIZE_STREAMS will cause a parsing error. This is new behavior which perhaps was triggered by one of the underlying component upgrades.
To Reproduce
Steps to reproduce the behavior:
INFO:localstack.services.kinesis.kinesis_mock_server: kinesis.mock.InvalidArgumentException: Stream Name '"audit_stream' contains invalid characters
Expected behavior
The surrounding quote characters in environment variables should be ignored.
Additional context
This worked with a 3 month old localstack image, and only broke recently, potentially in conjunction with the requirement for the region to be included in the stream name (that was not required in the previous image either)
The text was updated successfully, but these errors were encountered: