Parker Scanlon

### Describe the feature CodeBuild currently does not have methods to grant CodeBuild specific api commands to Iam roles. ### Use Case I am using lambdas in a custom resource...

Users still using v2 are facing problems relating to the Go.1.x runtime. Add wording in the readme to advise against using v2.

We currently give this repository as the "cdk recommended approach" for moving ECR assets. We should make it clear as to the level of maintenance and recommended use cases.

chore(lambda-nodejs): do not add unused environment variable by default for sdk v3 lambda runtimes

1

**Note:** for review before updating integ test snapshots. Will add updated snapshots after approval of approach. Closes #29497 Related to #29538 ### Reason for this change The `AWS_NODEJS_CONNECTION_REUSE_ENABLED` does not...

Feature Request: add support for external registries as sources and destinations

2

Depends on #7 and #8. #9 is an example. Other examples are ECR and Artifactory. - [ ] External ECR repositories - [ ] DockerHub - [ ] Aritfactory Add...

Feature Request: add support for credentials to be passed to the source and destination

2

The credentials would be used for the docker login so that external registries could be accessed by CodeBuild.

Feature Request: Reuse Infrastructure that Supports CodeBuild (lambdas, iam roles, provider, custom resource)

1

Each time the construct is instantiated, a custom resource, provider, 2 lambdas, and all of their roles are partitioned. Is there a way to reuse some of these resources? This...

Depends on #7 and #8.

This should be straightforward as it mirrors `Source.directory` other than `scope` is `_scope` in `bind()` since it is not needed.