Releases: cloudydeno/deno-aws_api
Releases · cloudydeno/deno-aws_api
v0.7.0: ECS Credentials, Backblaze compatibility
- Add by-default support for task-specific IAM credentials inside Amazon ECS. See also IAM roles for tasks.
Fixes #33 - thanks for the report! - Properly sign S3 request headers, fixing compatibility with Backblaze B2 (#32) - thanks for the report!
- Add dual-stack (IPv6-ready) endpoints for RDS and App Mesh.
- Fix API endpoint for Amazon Chime.
No codegen changes, v0.3
is still the latest codegen revision.
v0.6.0: Codegen v0.3 with numerous fixes
This is mostly a bug fixes & maintenance upgrade. Numerous services had specific fixes applied for them.
Breaking Change
Some response types now have nullable lists and maps from #21.
This brings the aws_api types closer to the official aws-sdk. Thanks @bacek for reporting in #16
Workarounds
- Add a nullcheck around any broken fields if you just want to get going again.
- If you aren't already, add an
?actions=...
filter to your import to produce more-concise types.
Notable Changes
- Test on Deno 1.11 up to 1.17 (the current latest)
- Use Deno's
/[email protected]
, and AWS SDKv2.1060.0
- Fix specific issues with
Glacier
,ApiGateway
,S3
, andEC2
- Fix 404 when requesting several APIs incluiding Lex and DynamoDBStreams
- Set
docs=short
as the default. For the least bytes, please specifydocs=none
. - Use Lambda's new IPv6-enabled API endpoints
Additional Changes
- Rewrite of response error parsing
- Add experimental request hooks to
ApiFactory
, helps with debugging - Allow selecting IPv6 endpoints for IMDSv2
- Block APIs needing AWS's "eventstream" protocol (so,
S3.SelectObjectContent
) - Fix incorrect logic reuse between
rest-json
andjson
clients - Adjust which headers are used for request signatures
Full Changelog: v0.5.0...v0.6.0
v0.5.0: Big Endpoint Rewrite
Versions
- Pairs with codegen generation
v0.2
. - Requires Deno 1.11 or later.
- Uses definitions from
[email protected]
.
Breaking Changes
- EC2's API isn't available from /x/ anymore, so import https://aws-api.deno.dev/v0.2/services/ec2.ts instead.
- Hopefully nothing else but the URL building was rewritten so if you find a regression please report!
All Changes
- Formalize
.makeNew(constructor)
method onApiFactory
- Complete rewrite of the endpoint selection logic
- Automatically selects GovCloud or AWS China domains
- Uses the S3 and EC2 dualstack endpoints when offered.
- Add
fixedEndpoint
option toApiFactory
for localstack, minio, etc. - Remove pre-generated EC2 API because of how large it is on disk.
- Implement request cancellation via
AbortSignal
pass-thru - Remove
/std/uuid
import in favor ofcrypto.randomUUID()
v0.4.0: Deno 1.9, Relocate service modules
- Deno 1.9 compatibility
- Remove most less-common AWS services.
- To use a service that is no longer bundled, use the Web Service.
- API Version has been removed from module filenames.
- The primary export of each service module is no longer
export default
.
⚠️ BREAKING CHANGES ⚠️
- This release stops including every service's API in the published module. Instead, the code-generation process is running on Deno Deploy and allows importing extremely precise modules, generated on the fly based on multiple configuration options. Check out this Web Service wiki page for more details on this new URL endpoint.
This is a bit experimental! Please report any issues or concerns with this new approach. - For services that are still bundled (SQS, S3, SNS, etc), the import URL no longer includes an API version (the
@year-month-date
part). Only the most recent API version gets bundled. - The primary class export on each service module is no longer 'default'.
So instead ofimport SQS from ...
, you'll doimport { SQS } from ....
. - Removed
AbortSignal
inputs which were allowed everywhere previously. These never did anything, and I'll add them back once Deno itself supports request cancellation.
The last version of this library to include every then-current API client on /x/
is v0.3.1.
v0.3.0: Module renaming & internal cleanup
Using definitions from [email protected]
- Service module names now match the folder names from AWS-SDK
- New names are in the README of course!
- Refactored the codegen a bit for cleaner output
- Bumped /std dependencies
- Removed /x/base64 dep in favor of /etc/encoding
v0.2.1: EC2 Instance Metadata / IAM Instance Roles
Using definitions from [email protected]
- Added basic client for AWS IMDSv2 (EC2 instance metadata server v2).
- All instances support v2, so I didn't implement v1. They both expose the same data. You may opt to disable v1.
- Added EC2 Instance IAM Role credential support, and enabled in the default credential loading chain.
- Regenerated all APIs, including 24 new API services.