cfn-diagram VS aws-sdk-js-v3

What do you think, is it worth writing a patch for cfn-diagrams to create these links automatically?

{ "week": [ { "Id": "16", "AWS-Services": [ "AWS CloudFormation", "AWS CloudTrail", "AWS Config", "Amazon CloudFront", "AWS Cost Explorer", "AWS Lambda", "AWS Key Management Service", "Amazon Athena" ], "Languages": [ "Python", "nodejs", ], "Tools": [ { "name": "ORGTOOL", "github": "https://github.com/daknhh/aws-orgtool" }, { "name": "cfn-python-lint", "github": "https://github.com/aws-cloudformation/cfn-python-lint" }, { "name": "cfn-diagram", "github": "https://github.com/mhlabs/cfn-diagram" }, { "name": "Taskfile", "github": "https://github.com/Wildhoney/Taskfile" } ], } ] }

cfn-diagram how many times have you wished you could take your CloudFormation YAML or JSON and then visualise it? When this open source tool provides a CLI as well as integration into tools like VSCode that help visualise CloudFormation templates as draw.io diagrams. Very nice Lars Jacobsson and the MatHem tech team. There is also the experimental cfn-diagram-ci which you can have a look at as well.

From this GitHub issue and this one from 2021 it seems like AWS just doesn't care about this - so, asking here if anyone knows of a workaround (other than "just keep using v2"... that's not a long-term solution), or if any AWS devs can shed some light on the situation.

First class typescript support, but everything is possibly undefined?

I published "ts-dynamodb-attributes-transformer" that transforms the TypsScript object to Amazon DynamoDB attributes (precisely, this attributes type is Record that is defined at aws-sdk-js-v3).

Once we have verified the presence of the AWS_WEB_IDENTITY_TOKEN_FILE and AWS_ROLE_ARN environment variables, our pod is ready to connect to and read from S3. The following Typescript snippet illustrates a simple example which fetches the names of all the S3 buckets in our account. It uses the AWS SDK for JavaScript V3

If you'd like the Amazon JavaScript SDK to support Deno then make your support known on this thread:

https://github.com/aws/aws-sdk-js-v3/issues/1289

I really suggest checking out the repo and especially the Upgrading section for more details.

No CloudFront URL signing - how can v3 SDK be labeled as general release if it doesn't have feature parity with the v2 SDK?