github DaviReisVieira/stackport v0.4.9
v0.4.9: fixes found testing against AWS Emulator

31 minutes ago

Bug fixes found by running StackPort end to end against AWS Emulator. Almost all of them affected every emulator and real AWS too.

IAM

  • Policy documents show again. Trust policies, inline policies and managed policy documents were always empty. (#198)
  • The dashboard counts your own IAM policies, like the IAM view, instead of every AWS managed one.

S3

  • Large uploads work on AWS Emulator. Files of 8 MiB or more go up in 8 MiB parts, under AWS Emulator's 16 MiB request limit. Tested on AWS Emulator, MiniStack, Floci, LocalStack and Moto. (#202)
  • Downloads are about 14 times faster, and files with any name download (names outside Latin-1 used to fail). (#203)
  • The object list no longer labels every object application/octet-stream: the Type column shows the extension, and the object detail shows the real content type. (#203)

DynamoDB

  • Decimals save exactly in Plain JSON, including numbers with more digits than a float holds. (#197)
  • A missing table shows a clear "not found" error instead of an empty table. (#207)
  • Item count and size are labelled as approximate, and "Get live item count" counts the items with a scan. On real AWS it asks before scanning, since the scan is billed. (#208)

SQS

  • Editing a queue's settings keeps its long polling wait time instead of resetting it to 0. (#205)
  • Invalid message attributes get a clear error instead of a 500. (#206)

CloudWatch Logs and tags

  • Log streams show their last event time, and every time is shown in your own time zone. (#200)
  • Tags can be read and edited on log groups and SQS queues from the resource table. (#201)

Resource table

  • EC2 instances are listed and counted as instances, not reservations. Load balancers, CloudFormation stacks and EventBridge rules on custom buses open their details, and the SQS detail is no longer empty. (#199)
  • Every resource type is now tested end to end, from the listing to its detail. Thanks @amjadjibon for the idea. (#175)
  • Errors from the endpoint come back with its own status and message instead of a 500.

Changes in behaviour

Change If it affects you
The SQS API answers 422 for fields it doesn't know Scripts calling /api/sqs/... should send only documented fields
Unknown /api/... paths answer a JSON 404 instead of the UI page Nothing to do
content_type is null in the S3 object list Read it from the object detail
Requires boto3 1.36 or newer pip install -U stackport upgrades it

For contributors

The test suite no longer sends requests to an emulator running on its default port (4566 or 9297) on your machine. (#215)

Full changelog: v0.4.8...v0.4.9

Don't miss a new stackport release

NewReleases is sending notifications on new releases.