Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Bernd Strehl
    @Strernd
    Sorry, I meant how did you invoke it?
    Wisen Tanasa
    @ceilfors
    wscat -c wss://...url
    Bernd Strehl
    @Strernd
    I will try to test it on friday on my machine
    Bernd Strehl
    @Strernd
    I just learned that the connect handler should receive a http event
    Wisen Tanasa
    @ceilfors
    @Strernd Just filed a PR here, can you help review? laconiajs/laconia#68
    Bernd Strehl
    @Strernd
    will do tomorrow
    Bernd Strehl
    @Strernd
    @ceilfors do you know if I can use the laconia http adapter for a function that is triggered by a cloudwatch cron?
    Wisen Tanasa
    @ceilfors
    @Strernd That sounds like a new adapter, rather than using the existing http adapter. What kind of data are you trying to adapt? It seems like most of the functions I've written that are triggered by cron has no input at all, or is taking the input from somewhere else
    Bernd Strehl
    @Strernd
    Yes, there's no real input I would say
    Wisen Tanasa
    @ceilfors
    @Strernd Are you actually talking about a Lambda that is re-used for two trigger types?
    Bernd Strehl
    @Strernd
    No, it shouldn't be triggered by HTTP just by cloudwatch
    Wisen Tanasa
    @ceilfors
    @Strernd Raised an issue here: laconiajs/laconia#119. Thanks!
    Bernd Strehl
    @Strernd
    Have you seen load balancer events? That would be nice also, they're a little different from http
    Wisen Tanasa
    @ceilfors
    @Strernd I have not used them! Why would one want to use that instead of API Gateway? Would be great if you can help file that issue too :)
    Bernd Strehl
    @Strernd
    https://serverless.com/blog/framework-release-v145/ It's explained quite good here why one would want to use it
    Hugo Sena Ribeiro
    @hugosenari
    Hi, anyone have some luck with https://localstack.cloud/ ?
    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