-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(lambda): configure workdir for docker image based functions #16111
Conversation
Title does not follow the guidelines of Conventional Commits. Please adjust title before merge. |
PR Linter / validate-pr (pull_request):
Which? It seems the readme already doesn't cover the other properties like Would this qualify as a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for submitting this PR. Looks great!
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Pull request has been modified.
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
CloudFormation allows setting the
WorkingDirectory
property inAWS::Lambda::Function.ImageConfig
to override the docker container's working directory, but this isn't currently exposed through CDK. Not sure if that was intentional.This PR wires that up.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license