[aws-lambda]: Add support for Dockerfiles not named Dockerfile in DockerImageCode.fromImageAsset

[mainframenzo]

Describe the feature

Lambda.DockerImageCode.fromImageAsset expects Docker image instructions files to be named "Dockerfile", and they might not be. Please consider adding support for Docker image instruction files not named "Dockerfile".

Use Case

I have a number of Dockerfiles in a single folder that do not work with Lambda.DockerImageCode.fromImageAsset because it expects Docker image instructions files to be named "Dockerfile". For example, given the list of Docker files below, if I specify Lambda.DockerImageCode.fromImageAsset(path.resolve(process.cwd(), '../build-utils/docker/dockerfile.lambda.backend')), the CDK errors with Cannot find file at <root-path>/build-utils/docker/dockerfile.lambda.backend/Dockerfile.

Docker files e.g.:

build-utils/docker
├── dockerfile.base
├── dockerfile.lambda.backend
├── dockerfile.lambda.backend.dockerignore
├── dockerfile.lambda.backend.handler.sh
├── dockerfile.lambda.dataset-to-sqlite-db
├── dockerfile.lambda.dataset-to-sqlite-db.dockerignore
├── dockerfile.lambda.dataset-to-sqlite-db.handler.sh
├── dockerfile.run
├── dockerfile.run.dockerignore
├── dockerfile.run.entrypoint.sh
└── lambda-docker-bootstrap.sh

Proposed Solution

No response

Other Information

No response

Acknowledgements

• I may be able to implement this feature request
• This feature might incur a breaking change

CDK version used

2.89.0 (build 2ad6683)

Environment details (OS name and version, etc.)

Mac Ventura 13.5.2

[mainframenzo]

Looks like this exists :)

[pahud]

I believe it should exist, no?

aws-cdk/packages/aws-cdk-lib/aws-ecr-assets/lib/image-asset.ts

Line 256 in c445b8c

readonly file?: string;

[github-actions]

This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.