by

Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Wisen Tanasa
    @ceilfors
    @hugosenari Good question. We tried it once in our team and we didn't manage to make it work. We actually moved to a pattern where we test more in the cloud, than locally.
    Hugo Sena Ribeiro
    @hugosenari
    I would suggest this for laconiajs/laconia#104 but can make it work for serverless-vanilla example :(
    Wisen Tanasa
    @ceilfors
    @hugosenari Did you mean you "can't"?.. What problem are you facing? Is the problem with serverless framework, laconia, or localstack?
    Hugo Sena Ribeiro
    @hugosenari
    localstack
    *I can't
    Wisen Tanasa
    @ceilfors
    Yeah we struggled to make it work too..
    Steffen Leistner
    @sleistner
    @Strernd
    What is the roadmap for adapter-api in regards to additional http verbs next to GET and POST?
    https://laconiajs.io/docs/guides/creating-api-endpoints#using-built-in-adapter
    Wisen Tanasa
    @ceilfors
    Hey @sleistner. We are tracing the discussion here, do chime in: laconiajs/laconia#124
    Hugo Sena Ribeiro
    @hugosenari
    Yesterday I had one idea related with laconiajs/laconia#141 if custom node runtime with similar api of actual but that accept streams at body could perform better for some edge cases like binary/jsonl responses. 🤔
    Sakthivel Viswanathan
    @sakthivel-tw

    Hello all,
    I did an initial analysis on the failed PR: laconiajs/laconia#323

    Release notes for npm-package-json-lintstates: Array type rules now ensure at least one item is passed.

    This is contradicting to the rule prefer-property-order which can allow empty array

    https://npmpackagejsonlint.org/docs/en/rules/package-json-properties/prefer-property-order

    Charles Szilagyi
    @thekarel
    I have an env var LACONIA_CONFIG_FB_TOKEN. I use laconia(adapter(app)).register(envVarInstances()) - I was assuming I'll end up with a dependency fbToken but it seems undefined. Am I missing something?
    Wisen Tanasa
    @ceilfors
    @sakthivel-tw Oops. Would you be interested to raise an issue to npm-package-json-lint? I think it's a non urgent dependabot PR for us. If the author is not interested to fix it, I guess we can take the default and put it to laconia.
    Hey @thekarel. The error message should be giving you a list of dependencies that are available. The message starts with These are the dependencies available in LaconiaContext. Is your token somewhere to be found in that list?
    Hugo Sena Ribeiro
    @hugosenari
    @ceilfors I can't deploy laconia-acceptance, serverless fail it says that restaurantBucket already is exists, is something with sync plugin, any tip?
    Wisen Tanasa
    @ceilfors
    hey @hugosenari. That's weird, I've never hit such error. Are you running it with npm run test:acceptance ?
    Hugo Sena Ribeiro
    @hugosenari
    ~/C/laconia> npm run test:acceptance

    yes, from work and home and same problem:

    An error occurred: S3Tracker - laconia-acceptance-node8-tracker already exists.

    Wisen Tanasa
    @ceilfors
    @hugosenari Oh!! The S3 name must be unique per region, I guess you are conflicting with my bucket, haha. I guess we need to make sure that it's unique for everyone, if you're playing around with it, I guess you can change the service name on top of the serverless.yml for now.
    Hugo Sena Ribeiro
    @hugosenari
    would be very strange if my bucket conflict with ours :-P
    but it works, almost works, now when I run tests they fail, with 500 :(
    Hugo Sena Ribeiro
    @hugosenari
    is something with :
    {
    "errorMessage": "Invalid parameters: /laconia-acceptrance-node8/apikey",
    "errorType": "Error",
    "stackTrace": [
    "validateSsmData (/var/task/node_modules/@laconia/config/src/SsmConfigConverter.js:3:11)",
    "SsmConfigConverter._getParameterMap (/var/task/node_modules/@laconia/config/src/SsmConfigConverter.js:19:5)",
    "<anonymous>",
    "process._tickDomainCallback [as _tickCallback] (internal/process/next_tick.js:228:7)"
    ]
    }
    Wisen Tanasa
    @ceilfors
    @hugosenari Ah! Yes. This is due to it not automated -- the test is expecting you to create a SSM parameter manually in AWS. Sorry for the poor documentation.
    Hugo Sena Ribeiro
    @hugosenari
    :-)
    Wisen Tanasa
    @ceilfors
    @hugosenari Created laconiajs/laconia#389
    Hugo Sena Ribeiro
    @hugosenari

    AWS add support to Node 12: https://aws.amazon.com/about-aws/whats-new/2019/11/aws-lambda-supports-node-js-12/

    And scheduled Node 8 Deprecation: 2019 January 6 (Create), 2020 February 3 (Update)

    Hugo Sena Ribeiro
    @hugosenari
    @ceilfors deploy creates any apikey or we need create it manually also?
    Wisen Tanasa
    @ceilfors
    @hugosenari If you're referring to the apikey that the acceptance test is trying to find in SSM, yes, it has to be manual
    @hugosenari Ok! I just saw your PR, I will continue the conversation there!
    Hugo Sena Ribeiro
    @hugosenari
    @ceilfors should we remove aws-sdk from core, to be more vendor agnostic?
    Wisen Tanasa
    @ceilfors
    @hugosenari Yes, that's the vision. Unfortunately, I don't have experience in other cloud providers though.
    Hugo Sena Ribeiro
    @hugosenari
    Me either, but require aws-sdk at core may keep away azure (and other) users or contributors 🤔
    Hugo Sena Ribeiro
    @hugosenari
    image.png
    image.png
    Hugo Sena Ribeiro
    @hugosenari
    core.svg
    config.svg
    Hugo Sena Ribeiro
    @hugosenari
    invoker.svg
    adapter-api.svg
    Wisen Tanasa
    @ceilfors
    @hugosenari That looks pretty cool! Good to see that there's no cyclic dependency too!
    Hugo Sena Ribeiro
    @hugosenari
    @ceilfors there are any place where we list changes for next major release?
    Wisen Tanasa
    @ceilfors
    Hey @hugosenari, we don't. I don't actually know where this kind of list normally is being maintained. Maybe we could create a milestone in GitHub?
    Hugo Sena Ribeiro
    @hugosenari
    Hugo Sena Ribeiro
    @hugosenari
    to honest did not expect theses features to v2, but would be strange set things to v3, without milestone to v2
    Franco Meriles
    @FrancoMeriles

    Hi all !!
    Hi have a problem when i wanna create a middleware.

    TypeError: next is not a function

    Im using laconia/core 1.9 and the example in the docs

    const laconia = require("@laconia/core");
    
    // Define a new middleware
    const myMiddleware = next => (event, context, callback) => {
      console.log("Logging all events in my middleware", event);
      return next(event, context, callback);
    };
    
    const app = (event, laconiaContext) => {};
    const handler = laconia(app);
    
    exports.handler = myMiddleware(handler); // Wrap your handler with a middleware
    Hugo Sena Ribeiro
    @hugosenari
    Hello
    here is working as expected
    image.png
    Hugo Sena Ribeiro
    @hugosenari
    try change your log to console.log('Loggin all events in my middleare', next);
    Franco Meriles
    @FrancoMeriles

    my bad, i was exporting te handler like this

    module.export.getContent = laconia(app)

    then on the next object I had to do something like this

    next.getContent(event, context, callback)

    Thanks