https://pulumi.com logo
Docs
Join the conversationJoin Slack
Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
plugin-framework
pulumi-cdk
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumi-service
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Powered by Linen
general
  • m

    microscopic-florist-85263

    07/18/2018, 12:21 AM
    Hrm getting an error running
    pulumi update
    , anybody know what the problem could be?
  • m

    microscopic-florist-85263

    07/18/2018, 12:21 AM
    @microscopic-florist-85263 uploaded a file: Untitled
    -.txt
  • m

    microscopic-florist-85263

    07/18/2018, 12:37 AM
    Ahh disregard the above, i bootstrapped a new pulumi project and it worked
  • m

    microscopic-florist-85263

    07/18/2018, 12:37 AM
    I think the only difference i made was explicitly set a
    pulumi config set cloud:provider aws
    and for some reason it spit out an error
  • w

    white-balloon-205

    07/18/2018, 12:37 AM
    @microscopic-florist-85263 Definitely a bug - sorry about that. I've opened https://github.com/pulumi/pulumi-terraform/issues/211 so we can investigate. Curious if you can share the results of
    pulumi update --logtostderr -v 9
    in DM?
  • m

    microscopic-florist-85263

    07/18/2018, 12:37 AM
    Ah thanks!
  • m

    microscopic-florist-85263

    07/18/2018, 12:38 AM
    Ah crap, deleted the project folder
  • m

    microscopic-florist-85263

    07/18/2018, 12:38 AM
    Will do it the next time i encounter bugs though.
  • m

    microscopic-florist-85263

    07/18/2018, 12:38 AM
    Let me see if i can reproduce the bug
  • w

    white-balloon-205

    07/18/2018, 12:38 AM
    Okay - no worries. I'll leave the issue open so we can see if we can reproduce ourselves as well.
  • m

    microscopic-florist-85263

    07/18/2018, 12:38 AM
    cool thanks!
  • m

    microscopic-florist-85263

    07/18/2018, 12:39 AM
    Great product you folks have btw 🙂
  • m

    microscopic-florist-22719

    07/18/2018, 12:39 AM
    Thanks! 😄
  • m

    microscopic-florist-85263

    07/18/2018, 12:57 AM
    hrmmm can’t repro.. dont know what it could be 😮
  • m

    microscopic-florist-85263

    07/18/2018, 12:58 AM
    When it was broken, it did prompt me for a cloud:provider config though.
  • m

    microscopic-florist-85263

    07/18/2018, 12:59 AM
    These are all taken following the instructions for the tutorial deploying containers onto Fargate.
  • m

    microscopic-florist-85263

    07/18/2018, 12:59 AM
    Might have been a tiny little typo or something followign the entire flow.
  • e

    early-napkin-64960

    07/18/2018, 2:24 AM
    Is it possible to declare a javascript based lambda with it;s functionality inline? All the examples of this that I find seem to be creating HTTP/API based lambdas and I want to create one that doesn’t have a trigger that I can attach to a cloudfront lambda edge property.
  • i

    incalculable-sundown-82514

    07/18/2018, 2:32 AM
    @early-napkin-64960 you can! https://pulumi.io/reference/pkg/nodejs/@pulumi/aws/serverless/#Function
    e
    1 reply ¡ 2 participants
  • a

    adventurous-jordan-10043

    07/18/2018, 6:53 AM
    Hi, I've found something quite disturbing
  • a

    adventurous-jordan-10043

    07/18/2018, 6:53 AM
    I have this very simple serverless API deployed
  • a

    adventurous-jordan-10043

    07/18/2018, 6:55 AM
    @adventurous-jordan-10043 uploaded a file: Simple API
    Simple_API.ts
  • a

    adventurous-jordan-10043

    07/18/2018, 6:56 AM
    The deployment is working correctly but when I try to manually trigger the ressource on API Gateway console, it fails with the error
    Execution failed due to configuration error: Invalid permissions on Lambda function
  • a

    adventurous-jordan-10043

    07/18/2018, 6:58 AM
    I still can trigger the deployed endpoint btw
  • b

    big-piano-35669

    07/18/2018, 2:25 PM
    @adventurous-jordan-10043 This is indeed surprising, the serverless API abstraction is supposed to create the adequate IAM policies. @white-balloon-205 @lemon-spoon-91807 Any idea what might be happening here?
    w
    a
    2 replies ¡ 3 participants
  • a

    adventurous-jordan-10043

    07/18/2018, 2:46 PM
    To make things more clear I can hit this URL https://q8liyzmzn1.execute-api.eu-west-1.amazonaws.com/stage/a but manual testing from the console (see screenshot) is failing.
  • a

    adventurous-jordan-10043

    07/18/2018, 2:50 PM
    I'm trying to port an existing project using serverless to pulumi and I'm hitting a few walls
  • a

    adventurous-jordan-10043

    07/18/2018, 3:04 PM
    https://github.com/pulumi/pulumi/issues/463 is a very interesting and important issue I think. It helped me solved a few of my problems but I'm still stuck on something. In
    index.ts
    I declare a Dynamo table. I then export it's name
    export const slotsTableName = slotsTable.name
    . I have an
    aws/dynamo.ts
    file containing some functions to interact with my Table. I also have a
    lambda.ts
    file.
    lambda.ts
    is imported in
    index.ts
    as a Lambda handler for my API.
    const api = new serverless.apigateway.API('api', {
        routes: [
            {method: 'GET', path: '/events', handler: lambda} // imported from `lambda.ts`
        ]
    })
    Internally,
    lambda.ts
    references
    aws/dynamo.ts
    and
    aws/dynamo.ts
    references `index.ts to import the Dynamo table name. Pulumi can successfully deploy this infra but the dynamo table name import from 'index.ts' to
    aws/dynamo.ts
    is failing because index.ts is not serialized in the final Lambda. I realize that my architecture is a bit complex and I think that I will have to fallback to lambda env variables and use the lower level package for my Lambdas.
    s
    1 reply ¡ 2 participants
  • a

    adamant-restaurant-73893

    07/18/2018, 3:27 PM
    Morning/Evening/Afternoon all. @white-balloon-205 and @bitter-oil-46081 will be live streaming at 11am PDT this morning. Join us if you can.

    https://www.youtube.com/watch?v=OlyUnNXBqK8▾

  • a

    adamant-restaurant-73893

    07/18/2018, 3:27 PM
    They'll be discussing this blog post on GitHub automation http://blog.pulumi.com/managing-github-webhooks-with-pulumi
Powered by Linen
Title
a

adamant-restaurant-73893

07/18/2018, 3:27 PM
They'll be discussing this blog post on GitHub automation http://blog.pulumi.com/managing-github-webhooks-with-pulumi
View count: 1