Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Jan 16 2019 18:39

    carlosandrebp on master

    upload email icon (compare)

  • Jan 15 2019 14:03

    carlosandrebp on master

    Icons update (compare)

  • Nov 13 2018 16:54
    hassankhan commented #3
  • Nov 02 2018 15:10
    hassankhan commented #3
  • Nov 02 2018 15:10
    hassankhan commented #3
  • Nov 01 2018 23:19
    hassankhan commented #3
  • Oct 29 2018 16:32
    hassankhan commented #3
  • Oct 24 2018 14:38
    hassankhan opened #3
  • Aug 14 2018 23:50

    carlosandrebp on master

    updates animations (compare)

  • Jul 19 2018 16:34
    brianneisler closed #1
  • Jul 19 2018 16:34
    brianneisler commented #1
  • Jul 18 2018 16:36

    andrepiresbp on master

    Updates (compare)

  • Jul 18 2018 15:50

    andrepiresbp on master

    Update (compare)

  • Jul 09 2018 19:25
    gornostal commented #59
  • Jul 09 2018 19:12
    maheshmasale commented #59
  • May 24 2018 23:39
    DavidWells removed as member
  • Feb 13 2018 19:40
    ivan-myob commented #54
  • Feb 08 2018 08:48
    julien2x opened #62
  • Dec 22 2017 16:14
    awcheng opened #61
  • Oct 23 2017 19:12
    dluu2015 closed #60
Himanshu Joshi
@himharsh1997
No, you need to have a different URL for all environments for better isolation and less confusion.
Omar Dulaimi
@omar-dulaimi
if so, then what's the point of /stage in the url?
since from aws console you would see a single stage for each project
note that I'm deploying these stages from different branches
master => production
staging => staging
Also, We're not considering using a custom domain like api.domain.com, since we're planning to use cloudfront origins later on
Himanshu Joshi
@himharsh1997
So, how single url able to decide which DB, and backend it should hit if we have single URL. We can have single URL of one stage deployed in different region using route53 but not for this case.
yes but how your testers get to know if they testing in staging/qa
Omar Dulaimi
@omar-dulaimi
I get your point, but I dont see why we have to have a different deployment for each stage. it would make it a lot simpler to just hardcode the same base url, and then just change the stage value according to one's needs
I mean api gw already support that
So why not expose it to us
Himanshu Joshi
@himharsh1997
or just set keys in aws ssm and create pipeline file which do that for you. Like /project/<sstage>/<variable>
just button work
you can put other checked in pipeline so no manual work.
Omar Dulaimi
@omar-dulaimi
I honestly don't get what you mean by that. Is it documented somewhere so I could read more about it?
Himanshu Joshi
@himharsh1997

Error --------------------------------------------------

Error: EIO: i/o error, chmod '/folder/demo-api/.webpack/getFunction1/node_modules/aws-appsync/node_modules/graphql/module/type/definition.js'

 For debugging logs, run again after setting the "SLS_DEBUG=*" environment variable.

Get Support --------------------------------------------
Docs: docs.serverless.com
Bugs: github.com/serverless/serverless/issues
Issues: forum.serverless.com

Your Environment Information ---------------------------
Operating System: linux
Node Version: 12.20.1
Framework Version: 2.17.0 (local)
Plugin Version: 4.5.2
SDK Version: n/a
Components Version: 3.7.7

I trying to deploy our project in aws-appsync and our bitbucket pipeline breaking due to this.
Can anyone help use. It's urgent.
It's coming from serverless.
Simi
@kaurthing_twitter
#
tenant-mgmt-service: # 84134: 25 of 26 promises have settled
tenant-mgmt-service: # 84134: 1 are taking longer than expected:
tenant-mgmt-service: # 84134: cf:vlncc-resources-lambda-sandbox.TokenAuthorizerLambdaArn waited on by: ${cf:vlncc-resources-lambda-sandbox.TokenAuthorizerLambdaArn} ${cf:vlncc-resources-lambda-sandbox.TokenAuthorizerLambdaArn}
tenant-mgmt-service: # This can result from latent connections but may represent a cyclic variable dependency
tenant-mgmt-service:
how can this be dealt with?
da club has asbestos
@jukebapes_twitter
Anyway to use this plugin with an existing AppSync service that was not bootstrapped using the serverless ecosystem https://github.com/bboure/serverless-appsync-simulator
Dror Weiss
@Dror__Weiss_twitter

Deployment 1: success
Deployment 2 (immediately after) with --force flag: ServerlessError: ValidationError: No updates are to be performed

Is there a particular reason for this error despite using the --force flag?

Roberto Wesley Overdijk
@RWOverdijk
This message was deleted
Cyber Peach
@peachwaravich
ภาพ.png
Sorry, If I want to run serverless in local , What Should I do ? and Now I got a problem .
Amit Goldberg
@amitizle
Hey, I'm moving to creating my λ functions with a Docker image, but I can't seem to make it work with serverless-offline. In AWS it works fine of course. Anyone have any idea how to make functions + API GW work with serverless-offline, when using image (=> docker)?
Charles Lanahan
@daidoji
hi, I have a serverless python code that works when I invoke local however when I deploy to AWS lambda python3.8 runtime a binary (that I have to use) links against libX11 which the runtime doesn't seem to support. How can I go about fixing this?
Charles Lanahan
@daidoji
nevermind, I guess just sticking em all in a lib folder near the binary seems to work
Alessandro Baccanelli
@alebacca89
Hi guys! There is a way to get documentation about serverless object that serverless framework pass to js function in File(.path.js) ? I want read stage passed when invoke command and check if serverless framework invoked local. thanks
jugglingjsons
@jugglingjsons
Hello! Do you guys know if there is a way to define the OAI for clodfront as a resource in serverless.yml?
I am trying to reference it in an s3accesspolicy resource that I have. created.
The use case is serving private s3 buckets content through a public cloudfront distribution.
Pedro Gomes
@Lusitaniae
I want to create resources only for prod
if i do
  Conditions:
      IsProd:
        Fn::Equals:
          - ${self:provider.stage}
          - prod
this doesn't work
    Type: AWS::RDS::DBInstance
    Condition: IsProd
this doesn't work
    Type: AWS::RDS::DBInstance
    Condition: !If [IsProd, true, false]
Any ideas?
it always complains mixed up types (it expect string, or all values must have same type)
Pedro Gomes
@Lusitaniae
Using https://github.com/anantab/serverless-plugin-ifelse seems to do it, but if no need for plugin all the better
Zerebokep
@Zerebokep
Hey everyone, is serverless-cloudflare-workers still being worked on or is the focus more on other cloudproviders like aws and gcp?
looks like the last commit was early 2019 :/
Arkoprabho Chakraborti
@Arkoprabho

Been struggling with a specific issue.
While deploying a function, we want to retain the log group. This can be easily done by specifying the DeletionPolicy as Retain.

At the same time, we want to be able to re-use existing log groups. How can we achieve this?
Use-case: On running sls remove, the log group isn't deleted due to retention policy (yay), but while trying to re-deploy, it throws an error saying the log group already exists.

Juan Carlos del Valle
@jc-delvalle
Hey guys, quick question, under org settings / access keys there is this option: 'Access Keys allow your CLI to authenticate with the Serverless Framework API' do you know how I tell the sls cli to use that secret?
Gareth McCumskey
@garethmcc
@jc-delvalle That access key only needs to be used on headless systems like a CI/CD server. Otherwise, you can just run serverless login to setup credentials for the CLI locally
Juan Carlos del Valle
@jc-delvalle
@garethmcc I am actually setting up a CD pipeline that's why I asked, should I manually create the .serverlessrc with that key there? or is there a way to pass it as an argument or something to the cli?
Maksymilian Babarowski
@k0mmsussert0d

I'm struggling to import my resources from one serverless.yml to another.
In the first yaml, I declare:

provider:
  name: aws
  environment:
    DOMAIN_PREFIX: ${self:service}-${opt:stage, self:provider.stage, 'dev'}
    POSTS_TABLE: ${self:provider.environment.DOMAIN_PREFIX}-posts-table
resources:
  Resources:
    PostsTable:
      Type: 'AWS::DynamoDB::Table'
      Properties:
        TableName: ${self:provider.environment.POSTS_TABLE}
  Outputs:
    PostsTableName:
      Value:
        Ref: PostsTable
      Export:
        Name: ${self:provider.environment.DOMAIN_PREFIX}-PostsTableName

This stack is getting created without problems. In another stack, I'm trying to import the table name:

provider:
  name: aws
  environment:
    DOMAIN_PREFIX: ${self:service}-${opt:stage, self:provider.stage, 'dev'}
    POSTS_TABLE:
      'Fn::ImportValue': '${self:provider.environment.DOMAIN_PREFIX}-PostsTableName'

but I'm getting an error:
Trying to populate non string value into a string for variable ${self:provider.environment.POSTS_TABLE}. Please make sure the value of the property is a string.

I checked the first stack in the AWS console and it has outputs with correct names. My guess is that there's something wacky going on with variables interpolation.

Maksymilian Babarowski
@k0mmsussert0d

Checked where the exception is being thrown in sls and found out that Variables.populateVariable function is being called with these args:

arn:aws:dynamodb:us-east-1:*:table/${self:provider.environment.POSTS_TABLE}
${self:provider.environment.POSTS_TABLE}
{ 'Fn::ImportValue': 'sf-microblog-dev-PostsTableName' }

This is for resolving the resource I put under one of my IAM roles in iamRoleStatements. Apparently, Fn::ImportValue is not resolved before variable interpolation with the resource name in the IAM role. Should I report this as a bug?