Ross Coundon
12/09/2021, 8:50 PMapp.setDefaultFunctionProps({
logRetention: logs.RetentionDays.ONE_WEEK,
..
})
Since then we haven't tried setting the log retention but I just tried it again on v0.53.4 and I still see an error:
The following resource(s) failed to create: [omwGetAllResourceConfigsLogRetention87CC9E7D, (and many others)].
Received response status [FAILED] from custom resource. Message returned: A conflicting operation is currently in progress against this resource. Please try again
Is this a known issue and is there a way around it?Ryan
12/10/2021, 5:32 AMChris Visser
12/10/2021, 2:39 PMOmi Chowdhury
12/10/2021, 4:27 PMRoss Coundon
12/10/2021, 7:47 PMAdriƔn Mouly
12/10/2021, 8:11 PMenvironment
, should it read it from the .env
file defined in SST?AdriƔn Mouly
12/10/2021, 8:47 PMregisterSiteEnvironment
are defined AFTER building the app with npm run build
ā¦ why is that?Mike McCall
12/11/2021, 3:30 PMaccessLog
to false. I might have missed something, but accessLogs were not being created by default before. This is an easy work around because I was already managing the access log for the Api outside of the SST's construct.Tharshan
12/11/2021, 7:43 PMthdxr
12/12/2021, 12:28 AMbundle.esm
flag to be turned on to true and from there I need to package aws-lambda-ric in 2 different modes both for esm and cjs. The rest of SST can be left as is for now.
Anyone else looking for ESM support?Robert Morgan
12/13/2021, 6:01 PMDerek Kershner
12/13/2021, 6:04 PMAdam Elmore
12/13/2021, 7:49 PMNextjsSite
? Would sst.json
live at the repo root?Gabriel AraĆŗjo
12/13/2021, 9:41 PMJack Fraser
12/14/2021, 2:36 PMKujtim Hoxha
12/14/2021, 6:45 PMJack Fraser
12/15/2021, 5:30 PMSeth Geoghegan
12/15/2021, 6:51 PMthis.addOutputs({
"ApiEndpoint": "https://"+ api.restApi.restApiId + "-" + process.env.VPC_ENDPOINT + ".execute-api." + this.region + ".<http://amazonaws.com/|amazonaws.com/>" + this.stage
});
resulting in more than 1 output?
Outputs:
apiApiEndpoint71625CD3: https://<rest-api-id>.<http://execute-api.us-east-1.amazonaws.com/stage/|execute-api.us-east-1.amazonaws.com/stage/>
ApiEndpoint: https://<rest-api-id>-<my-vpc-endpoint>.<http://execute-api.us-east-1.amazonaws.com/stage|execute-api.us-east-1.amazonaws.com/stage>
I don't know what is creating apiApiEndpoint71625CD3
AdriƔn Mouly
12/16/2021, 1:08 AMDockerImageFunction
from CDK.
How can I give it permissions to write into Dynamo table?
This is really easy with SST Function construct, but not sure how to do it with CDK constructs.jamlen
12/16/2021, 1:02 PMWarning: Ignoring extra certs from `/etc/pki/tls/certs/ca-bundle.crt`, load failed: error:02001002:system library:fopen:No such file or directory
Seth Geoghegan
12/16/2021, 9:35 PMDerek Kershner
12/16/2021, 10:38 PMDerek Kershner
12/17/2021, 12:10 AMApi
today, wondering if I am alone...
https://github.com/serverless-stack/serverless-stack/issues/1163Branko Gvoka
12/17/2021, 8:41 AMpdfkit
library and esbuild - has anyone had similar problems and solution for this? Thanks!
`Error: ENOENT: no such file or directory, open '/Users/.../pms-integrations-v2/services/hsk/.build/src/cron/data.trie'
https://github.com/foliojs/pdfkit/issues/990
https://stackoverflow.com/questions/67234055/pdfkit-on-js-ts-lambda-with-cdk-error-enoent-no-such-file-or-directory-openMischa Spiegelmock
12/19/2021, 9:54 AMAdriƔn Mouly
12/20/2021, 11:34 PMRoss Coundon
12/22/2021, 10:06 AMAdriƔn Mouly
12/22/2021, 8:05 PMDockerImageFunction
construct from CDK into my SST stack.
How can I test this locally? Can I run the docker image locally? and how I can connect to Dynamo and others? is that possible from LOCAL?Ross Coundon
12/23/2021, 12:44 PMsst deploy
and the process hangs at the point where it bundles the first function in the stack.
Setting up sst deploy
within a debug launch config I can see that it gets to this point in Functions.js:
else {
const bundled = core_2.Runtime.Handler.bundle({
id: logicalId,
root: root.appPath,
handler: handler,
runtime: runtime.toString(),
srcPath: srcPath,
bundle: props.bundle,
});
We've tried this on a couple of different machines, one Windows and one Mac with the same result.
I can run sst start
successfully so it seems like a bundling problem, which the point of hanging would imply too.
sst-debug.log looks like this when running deploy from a debugger - output is pratically identical doing a straight sst deploy
(last line is a console log in the stack)
[2021-12-23T12:40:17.939] [DEBUG] default - SST: 0.54.4
[2021-12-23T12:40:17.942] [DEBUG] default - CDK: 1.132.0
[2021-12-23T12:40:17.945] [INFO] default - Using stage: pjn-dev
[2021-12-23T12:40:17.948] [INFO] default - [90mPreparing your SST app[39m
[2021-12-23T12:40:18.181] [DEBUG] core - synth {
output: '.build/cdk.out',
app: 'node .build/run.js',
rollback: true,
roleArn: undefined,
verbose: 0,
noColor: false
}
[2021-12-23T12:40:18.392] [TRACE] cdk - Debugger attached.
[2021-12-23T12:40:20.742] [TRACE] cdk - Debugger attached.
[2021-12-23T12:40:42.010] [TRACE] cdk - Running locally? false
We're running sst v0.54.4. Any thoughts?Carter Himmel
12/24/2021, 1:19 AMhttp://tugboat.dev/utit9r.pngā¾