You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
🪲 bug report
🚀 feature request
📚 construct library gap
☎️ security issue or vulnerability => Please see policy
❓ support request => Please see note at the top of this template.
What is the current behavior? If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
I'm migrating from 0.31.0 to 1.0.0. I have a stack to create ApiGateway and Lambdas
This is part of the code:
constDEFAULT_RUNTIME=lambda.Runtime.NODEJS_8_10;constAPI_LAMBDAS_BASE_PATH=path.join(__dirname,'../../rest/dist');exportclassApiStackextendscdk.Stack{privatesharedLayer: lambda.LayerVersion;constructor(scope: cdk.Construct,id: string,props: ApiStackProps){super(scope,id,props);this.createCodeAsset();this.createSharedLayer();
...
}privatecreateCodeAsset(): void{this.codeAsset=lambda.Code.asset(path.join(API_LAMBDAS_BASE_PATH,'code'));}privatecreateSharedLayer(): void{constlayerName=StackUtils.getEnvName('api-layer',this.envName);this.sharedLayer=newlambda.LayerVersion(this,layerName,{code: lambda.Code.asset(path.join(API_LAMBDAS_BASE_PATH,'layer')),compatibleRuntimes: [DEFAULT_RUNTIME],description: 'Shared dependencies layer for API Lambdas',});}
...
}
The deployment simply ends without any errors rights after the start. The verbose logs:
api-stackcdk1test
api-stackcdk1test: deploying...
Waiting for stack CDKToolkit to finish creating or updating...
Preparing asset apistackcdk1testapilayercdk1testCode5ED1E954: {"path":"asset.904bbef99d02b2b8c95d96e2a1621f358c424427f3d15b0c0256838afe31b98f","id":"apistackcdk1testapilayercdk1testCode5ED1E954","packaging":"zip","sourceHash":"904bbef99d02b2b8c95d96e2a1621f358c424427f3d15b0c0256838afe31b98f","s3BucketParameter":"apilayercdk1testCodeS3Bucket2C4C037A","s3KeyParameter":"apilayercdk1testCodeS3VersionKeyDFEF168D","artifactHashParameter":"apilayercdk1testCodeArtifactHash3A74B244"}
Preparing zip asset from directory: cdk.out/asset.904bbef99d02b2b8c95d96e2a1621f358c424427f3d15b0c0256838afe31b98f
What is the expected behavior (or behavior of feature suggested)?
Code should create resources properly
What is the motivation / use case for changing the behavior or adding this feature?
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
Seems like either assets are stealthily fails or the LayerVersion code
The text was updated successfully, but these errors were encountered:
To preserve file order using `archiver` files must be appended serially either using stream or
buffer (appending by file path does not preserve order even when done serially).
Appending using buffer seems to be the only way to solve `EMFILE` errors.
Call `fs.stat` before appending to preserve mode.
Closesaws#3145, Closesaws#3344, Closesaws#3413
To preserve file order using `archiver` files must be appended serially either using stream or
buffer (appending by file path does not preserve order even when done serially).
Appending using buffer seems to be the only way to solve `EMFILE` errors.
Call `fs.stat` before appending to preserve mode.
Closes#3145, Closes#3344, Closes#3413
Note: for support questions, please first reference our documentation, then use Stackoverflow. This repository's issues are intended for feature requests and bug reports.
I'm submitting a ...
What is the current behavior?
If the current behavior is a 🪲bug🪲: Please provide the steps to reproduce
I'm migrating from
0.31.0
to1.0.0
. I have a stack to create ApiGateway and LambdasThis is part of the code:
The deployment simply ends without any errors rights after the start. The verbose logs:
Code should create resources properly
What is the motivation / use case for changing the behavior or adding this feature?
Please tell us about your environment:
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. associated pull-request, stackoverflow, gitter, etc)
Seems like either assets are stealthily fails or the
LayerVersion
codeThe text was updated successfully, but these errors were encountered: