Skip to content

Conversation

@abetomo
Copy link
Contributor

Added class to set s3 events.
In the next PR add S3Events to main.js.

"test": "standard && standard bin/node-lambda && mocha"
"lint": "standard && standard bin/node-lambda",
"test": "npm run lint && npm run unit",
"unit": "mocha"
Copy link
ContributorAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It has nothing to do with subject matter, but cleaned the scripts.

Copy link
Collaborator

@DeviaVirDeviaVir left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some language feedback, looks good to me 👍

'use strict'

/**
* Do not create Bucket of S3
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do not create S3 bucket?

if(err){
if(err.code!=='ResourceConflictException')reject(err)
// If it exists it will result in an error but there is no problem.
resolve('Already exists permission')
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Permission already set

@abetomo
Copy link
ContributorAuthor

@DeviaVir Thank you!
Your advice was very helpful.

@DeviaVirDeviaVir merged commit 286e063 into motdotla:masterDec 7, 2017
@abetomoabetomo deleted the feature_s3_events branch December 7, 2017 14:33
@DeviaVirDeviaVir mentioned this pull request Dec 11, 2017
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@abetomo@DeviaVir