Generating all aws clients

[joepjoosten]

Solves #44

Generates all clients in ./generated folder for a particular version of aws (e.g. v3.535.0).

I'm reusing the previous codegen-client.ts, but using the smithy files a little bit different.

It's not done yet, some open points:

• I saw an implementation of presigned urls in the s3 client. Is it possible to make this more general? Can all commands be presigned?
• How to publish?

[joepjoosten]

I've some time later this evening to look at it again

[joepjoosten]

Also, what about versioning?
Probably better to keep it close to the AWS clients version, but how to indicate that we created a new version of the generated code?

[godu]

Hi,
I tested your PR for the mq & rds clients. The build miss the commonjs build. After fix this, my project is working well 👍

[godu]

Also, what about versioning? Probably better to keep it close to the AWS clients version, but how to indicate that we created a new version of the generated code?

This idea is very attractive, however I would prefer to keep the aws client as peerDep and sync the version of all @effect-aws/client-*. It can be more flexible if we make radical changes.

[joepjoosten]

Also, what about versioning? Probably better to keep it close to the AWS clients version, but how to indicate that we created a new version of the generated code?

This idea is very attractive, however I would prefer to keep the aws client as peerDep and sync the version of all @effect-aws/client-*. It can be more flexible if we make radical changes.

Ok, let's use the effect-aws version for the generated aws-client packages. Should we bump the release to 2.0? (and how to do this in this project, i don't really know).

Mayor version bump because it could be breaking, because the generated Effect tagged Errors/Exceptions changed name to be in line with the smithy models

[joepjoosten]

Who can help with the projen and github workflow, so it becomes publishable? I don't have any experience with projen...

[godu]

I think this PR is too huge. Let's ship it in smaller pieces.
I took some of your improvements of codegen script in my PR #48