mitocgroup / deep-framework Goto Github PK

Implement local lambda->lambda calls

Lambda with call method DELETE doesn't work properly through API Gateway. The lambda doesn't receive passed arguments. Direct lambda call works well.

Fix Lambda runtime context fail (currently it always succeed and generate unexpected behaviour on native fail called)

LambdaResponse._decodePayload fails when trying to parse invalid json string:

Refactoring unit tests for deep-kernel module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Implement a method to switch between user roles "on fly" to obtain AWS temp credentials for specific permissions.

I'm uing this code:

var deepSecurity = DeepFramework.Kernel.container.get('security');
deepSecurity.login('www.amazon.com', profile.identities[0].access_token, profile.user_id, (error, securityToken)=> {
]);

I'm getting this response:

Refactoring unit tests for deep-log module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Add "LogType" parameter into deep-resource when invoking lambda functions in order to receive lambda logs along with response body.

Ref. http://docs.aws.amazon.com/AWSJavaScriptSDK/latest/AWS/Lambda.html#invoke-property

IdentityId for local and aws environment are different cases. For local environment it IdentityId and for aws environmentidentityId.

Error stack trace:

LoadCredentialsException: Error on loading security credentials in deep-resource -> request. SynchronizeCognitoDatasetExceptio…
  at Request.emit(/js/lib/deep-framework.js:25:21898)
  at Request.emit(/js/lib/deep-framework.js:25:29882)
  at Request.callListeners(/js/lib/deep-framework.js:25:30423)
  at Request.<anonymous>(/js/lib/deep-framework.js:25:18895)
  at Response.AWS.CognitoSyncManager.RemoteStorage.CognitoSyncRemoteStorage.listUpdates.response(/js/lib/deep-framework.js:35:8600)
  at ? (/js/lib/deep-framework.js:34:16940)
  at Object.onFailure(/js/lib/deep-framework.js:33:11552)
  at ? (/js/lib/deep-framework.js:33:10303)
  at ? (/js/lib/deep-framework.js:34:5580)
  at ? (/js/lib/deep-framework.js:23:9821)

Load logged user using passed caller credentials from API Gateway (cognito identity pool and cognito identity id).

Please refer to the link bellow for more details
https://letsencrypt.org/2015/11/12/public-beta-timing.html

Remove all dependencies of deep-* services when booting a service (e.g. when booting deep-db it requires deep-cache service to be already booted)

Refactoring unit tests for deep-validation module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Refactoring unit tests for deep-cache module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

• Update roadmap priorities
• Add short description for each feature

Please refer to the link bellow for more details

https://github.com/showcases/web-application-frameworks

Refactoring unit tests for deep-core module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

When trying to make an async call to another lambda using invokeAsync() method i'm getting this error:

AccessDeniedException: User: arn:aws:sts::accountid:assumed-role/LambdaName/awslambda_959_20151123081502137 is not authorized to perform: lambda:InvokeFunction on resource: arn:aws:lambda:us-east-1:accountid:function:lambdaname]

var lambdaResource = resources.get('@microserviceIdentifie:resource:action');
lambdaResource.request(payload).invokeAsync().send((response) => {
      return callback(null, response);
    });

Improve unit tests for each library and assure most cases are covered (improve quality)

• Replace coverage badges from "Coveralls" to "Codacy" in Readme file

Please refer to attachment for more details

Refactoring unit tests for deep-db module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Refactoring unit tests for deep-fs module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Refactoring unit tests for deep-resource module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Manual benchmarking (10 runs each step, min/avg/max):

• Run with/out babel-polyfill
• Run different lambda sizes (with some unused garbages) [x5 sizes]
• Run different lambda sizes (use the included code) [x5 sizes]
• Run Dynamo+S3 write with/out deep-framework

1. Add kernel loading from file.
2. Loading all services by Kernel.get().
3. Fix mocks to have the same aproach

• Time of running the process should be optimized (actual result is more than 7 minutes)

Create void log driver

Adding functionality to pull local module version instead of npm repo version. Because this issue often blocks development process when module was modified in dev but didn't published it npm repo.

Implement lambda async calls

Find a way to append deployID using deep-asset by default

TypeError: Cannot read property 'body' of undefined
lib/deep-framework in new SuperagentResponse

Implement the functionality that will allow to call a lambda or an api gateway endpoint from another lambda.

• skip "Mocha" keywords : "test" , "suite" , "description" , "it" and etc.

Refactoring unit tests for deep-asset module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

When i'm trying to run s3fs.readdirp('/dir/') on local server i'm getting only /dir files and folders:

[ '1', '2', '3', '4']

but when i run this command on aws, i'm getting all files and folders recursively:

[
  "1/",
  "1/1.1/",
  "1/1.1/file1",
  "1/1.2/",
  "1/1.2/1.2.1/",
  "1/1.2/1.2.1/file2",
  "2/",
  "2/2.1/",
  "2/2.1/file3",
  "3/",
  "4/"
]

Refactoring unit tests for deep-security module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

Refactoring unit tests for deep-di module to have the same approach to create Kernel instance from config file.
Loading all services by Kernel.get(). Update/create mocks to have the same approach for all modules.

In Chrome it works without errors
[email protected]

when i run code on local server:

let fs = this.kernel.get('fs').system;
this.fs.readdirp('/').then((files) => {
      console.log(files);
      return this.createResponse(null).send();
    }, (reason) => {
      console.log(reason);
    });

i'm getting:

[ '/tmp/system.folder/microservice.identifier/1',
  '/tmp/system.folder/microservice.identifier/1/1.1',
  '/tmp/system.folder/microservice.identifier/1/1.1/123.txt',
  '/tmp/system.folder/microservice.identifier/2',
  '/tmp/system.folder/microservice.identifier/3',
  '/tmp/system.folder/microservice.identifier/4' ]

expected:

[ '/1',
  '/1/1.1',
  '/1/1.1/123.txt',
  '/2',
  '/3',
  '/4' ]

• Login to DEEP Marketplace
• Add 'ToDo application' to Cart
• Input valid data into 'Billing Management and AWS Credentials fields'
• Click on 'Checkout' button and deploy the application
• Go to 'Account' page after finishing the deploy
• Click on 'Account'
• Click on 'Billing Management'
• Click in 'Payment Receipts'

BUG :

Cannot read property 'hasOwnProperty' of null error while clicking on Payment Receipts

TypeError: Cannot read property 'hasOwnProperty' of null
  at ? (/js/lib/deep-framework.js:34:3149)
  at AcceptorStateMachine.runTo(/js/lib/deep-framework.js:34:2824)
  at Request.transition(/js/lib/deep-framework.js:32:27269)
  at Request.emit(/js/lib/deep-framework.js:33:121)
  at Request.emit(/js/lib/deep-framework.js:33:8100)
  at Request.callListeners(/js/lib/deep-framework.js:33:8641)
  at Request.<anonymous>(/js/lib/deep-framework.js:32:29120)
  at Response.<anonymous>(/js/lib/deep-framework.js:23:31572)
  at new LambdaResponse(/js/lib/deep-framework.js:23:17543)
  at LambdaResponse._decodePayload(/js/lib/deep-framework.js:23:18554)

Please refer to this PR: https://travis-ci.org/MitocGroup/deep-framework/builds/98650579

> [email protected] test /home/travis/build/MitocGroup/deep-framework/src/deep-security
> babel-node `which isparta` cover --include 'lib/**/*.js' _mocha -- 'test/**/*.js' --reporter spec --ui tdd
npm ERR! Linux 3.13.0-40-generic
npm ERR! argv "/home/travis/.nvm/versions/node/v0.12.9/bin/node" "/home/travis/.nvm/versions/node/v0.12.9/bin/npm" "run" "test"
npm ERR! node v0.12.9
npm ERR! npm  v2.14.9
npm ERR! code ELIFECYCLE
npm ERR! [email protected] test: `babel-node `which isparta` cover --include 'lib/**/*.js' _mocha -- 'test/**/*.js' --reporter spec --ui tdd`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the [email protected] test script 'babel-node `which isparta` cover --include 'lib/**/*.js' _mocha -- 'test/**/*.js' --reporter spec --ui tdd'.
npm ERR! This is most likely a problem with the deep-security package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     babel-node `which isparta` cover --include 'lib/**/*.js' _mocha -- 'test/**/*.js' --reporter spec --ui tdd
npm ERR! You can get their info via:
npm ERR!     npm owner ls deep-security
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR!     /home/travis/build/MitocGroup/deep-framework/src/deep-security/npm-debug.log
[FAILED] npm run test
npm ERR! Test failed.  See above for more details.

Add a method to check if logged user is allowed to invoke specific action (microservice:resource:action). It implies implementation of a deep policies static processor.