Setup example repo seems to not work with AWS bucket
dfdgsdfg opened this issue · 1 comments
dfdgsdfg commented
This is a Bug Report
Description
Setup example repo seems to not work.
- Cloned
https://github.com/graphcool/chromeless.git
- npm i from
chromeless/serverless
- Set and get permission The AWS Lambda function, API Gateway and IoT
Additional Data
t/chromeless/serverless ╍ npm run deploy (296ms)
> chromeless-remotechrome-service@1.3.0 deploy /tmp/chromeless/serverless
> serverless deploy
Serverless: Compiling with Typescript...
Serverless: Using local tsconfig.json
/tmp/chromeless/serverless/node_modules/@types/graphql/subscription/subscribe.d.ts (17,4): Cannot find name 'AsyncIterator'.
/tmp/chromeless/serverless/node_modules/@types/graphql/subscription/subscribe.d.ts (29,4): Cannot find name 'AsyncIterable'.
Serverless: Typescript compiled.
Serverless: Injecting Headless Chrome...
Serverless: Packaging service...
Serverless: Excluding development dependencies...
Serverless Error ---------------------------------------
Missing required key 'Bucket' in params
Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com
Your Environment Information -----------------------------
OS: darwin
Node Version: 8.11.3
Serverless Version: 1.27.3
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! chromeless-remotechrome-service@1.3.0 deploy: `serverless deploy`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the chromeless-remotechrome-service@1.3.0 deploy script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! /Users/user/.npm/_logs/2018-06-20T02_09_24_012Z-debug.log
dfdgsdfg commented
Need change service name to unique. Also it must be not too long.
service: MY-UNIQUE-CLESS-SLESS
And should document this for others.
https://github.com/prismagraphql/chromeless/tree/master/serverless#using-the-proxy
Check this out.
serverless/serverless#4457
Also if you delete bucket manually, you have to remove cloud formation and IAM role.
serverless/serverless#1877