Skip to content
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

lambda.AssetCode() does not preserve file permissions #7749

Closed
pahud opened this issue May 2, 2020 · 5 comments
Closed

lambda.AssetCode() does not preserve file permissions #7749

pahud opened this issue May 2, 2020 · 5 comments
Assignees
Labels
@aws-cdk/aws-lambda Related to AWS Lambda bug This issue is a bug. closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.

Comments

@pahud
Copy link
Contributor

pahud commented May 2, 2020

I was trying to deploy my lambda code assets with custom runtime with my own bootstrap file which has to be executable(chmod +x).

However, it loos like when the folder was staged into cdk.out the executable permission will not be preserved.

圖片

According to the document, if we are implementing the custom runtime, the bootstrap file has to be exetable.
https://docs.aws.amazon.com/lambda/latest/dg/runtimes-custom.html

Looks like we have no property to enable the permission preservation in this scenario.

Not sure if it's related to nodejs/node#27241

Reproduction Steps

Error Log

Environment

  • CLI Version : 1.36.1
  • Framework Version:
  • OS : mac os x
  • Language : typescript

Other


This is 🐛 Bug Report

@pahud pahud added bug This issue is a bug. needs-triage This issue or PR still needs to be triaged. labels May 2, 2020
@SomayaB SomayaB added the @aws-cdk/aws-lambda Related to AWS Lambda label May 5, 2020
@nija-at
Copy link
Contributor

nija-at commented May 13, 2020

Hi @pahud -

Can you provide the code snippet you are using for this?

@nija-at nija-at added response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. and removed needs-triage This issue or PR still needs to be triaged. labels May 13, 2020
@netroy
Copy link
Contributor

netroy commented May 14, 2020

@pahud This is most likely due to the changes on copyFileSync for osx.
Can you try to test this on node 10.*?
if that fixes the issue, here is the ticket to follow.

@github-actions github-actions bot removed the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label May 14, 2020
@nija-at nija-at added the response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days. label May 15, 2020
@github-actions
Copy link

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.

@github-actions github-actions bot added the closing-soon This issue will automatically close in 4 days unless further comments are made. label May 22, 2020
@pahud
Copy link
Contributor Author

pahud commented May 25, 2020

Please don't close this issue. Will get back to it shortly.

@pahud
Copy link
Contributor Author

pahud commented May 26, 2020

this issue does not exist in my environment

tested with node v10.20.1 on Cloud9 and v13.10.1 in mac os x.

Closing this issue tentatively.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
@aws-cdk/aws-lambda Related to AWS Lambda bug This issue is a bug. closing-soon This issue will automatically close in 4 days unless further comments are made. response-requested Waiting on additional info and feedback. Will move to "closing-soon" in 7 days.
Projects
None yet
Development

No branches or pull requests

4 participants