StackPort 0.4.4
Two fixes, both reported or picked up by the community.
DynamoDB tables with binary data open again (#176, #177)
A table holding binary (B or BS) data that is not valid UTF-8 returned 500 as soon as you opened it. Binary now travels as base64, which is how AWS writes B in DynamoDB JSON, and it works end to end: scanning, paginating on a binary key, querying by a binary key, editing an item, and deleting it.
This also fixes a quieter bug. Saving an item with a binary attribute used to store the base64 text itself as the bytes. It now stores the real bytes. Items written from the StackPort editor before this release may hold that base64 text, so check and rewrite any binary attributes you edited there. Thanks to @mspiller for the report.
Correct ids for five more resource types (#170, #174)
IAM policies, EC2 subnets and security groups, EFS file systems, and RDS clusters listed a field that was not their real identifier, so the detail view returned 500. They now list the identifier the describe call expects, in the web UI and in stackport list. The test reads each list and describe shape from botocore, so a new collision like this would fail CI. Thanks to @amjadjibon, his second fix in a week.
Upgrade
pip install -U stackport
# or
docker pull davireis/stackport:0.4.4
Full Changelog: v0.4.3...v0.4.4